Duplicate Asset Detection in AEM

 Enabling Duplicate Detection

If you attempt to upload an asset that exists in Adobe Experience Manager (AEM) Assets, the duplicate detection feature identifies it as duplicate. Duplicate detection is disabled by default. To enable the feature, do the following steps:

  1. Open the Adobe Experience Manager Web Console Configuration page at https://[server]:[port]/system/console/configMgr.
  2. Edit the configuration for the servlet Day CQ DAM Create Asset.
  3. Select the detect duplicate option, and click/tap Save.


The detect duplicate feature is now enabled in AEM Assets. When a user attempts to upload an asset that exists in AEM, the system checks for conflict and indicates it. The assets are identified using SHA-1 hash stored at jcr:content/metadata/dam:sha1, which means duplicate assets are detected irrespective of the filenames.

By duplicate in this context means, exact copy of the asset. For example if you are trying to upload xyz image and the same image already exist in the dam may be with different name or in different location, Then this feature gets you the list of such duplicate images in the dam. This is possible because each asset is associated with unique SHA1-hash, this is correspondent to dam:sha1 property as shown below. If two assets are same, then they both share same dam:sha1 value.


Below is the Dialog you see if there are any duplicate assets. As you can see I already have abc.jpg in "/content/dam/test" location and I am trying upload same image with different name in the same folder.


As I said earlier, this feature even helps you to detect duplicate assets present in different location. As shown in below picture, here I am again trying to upload same image with different name but in different folder.


Work around for you guys:

Try modifying the content of the asset. Crop it for image or change data for text or similar type.

Comments

Post a Comment

Popular posts from this blog

Customizing Detect Duplicate Result

Image
Customizing Detect Duplicate Result We have seen in the previous blog how we can detect any duplicate asset and the result contains a list of all the duplicate assets. Now if you have noticed when you click on the items in the list, it is not redirecting to the respective assets. So, if you want to know how you can achieve that follow this blog. The duplicate detect dialog is as shown below. To summarize, here I am trying to upload def.jpg, but it’s duplicates already present in the dam so I am getting those assets list in the result. As you can see the result is non-clickable and cannot redirect to the corresponding images. In order to achieve clickable result or if you want it to redirect you to those assets follow below steps. First step is to find the script that is responsible to render this response. After debugging, I found that " /libs/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js "  is responsible for rendering this dialog. ...
Read more

Customizing Asset Upload Dialog

Image
  Customizing Asset Upload Dialog We have seen in the previous blogs that how we can detect duplicate assets, but once this feature is enabled it will be applied to each and every asset you are uploading. So, if you don’t want it to be applied for some assets or you want to have control over whether or not you want to get duplicates of an asset, then you can customize asset dialog then have a control over this feature. Let’s find out how to do this. Asset Upload Dialog looks something like as shown in below screenshot. Now I want to toggle between applying duplicate asset feature or not. So, I am adding one checkbox to the above dialog when this is checked it will call duplicate asset feature, else it won’t call. In order to achieve this, follow below steps. First step is to find the script that is responsible to render this dialog. After debugging, I found that " /libs/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js "  ...
Read more