Uploading New Versions of an Asset in AEM Assets

Question

Hi team,

We are currently testing the capabilities of AEM Assets and we have been able to find videos that walk us through how to upload new versions of assets in AEM Assets. We have been unable to find any that help us fully understand how the naming convention of the new asset needs to be the same as the existing asset in AEM Assets to be added as a new version. I've recently uploaded a new asset with the same name as the existing asset into AEM Assets and it uploaded as a new separate asset in the system. Is there a reason why this would happen? Would metadata have anything to do with it? Has anyone else had this experience or know of any documentation that covers the naming convention and versioning relationship in depth?

Best,

E

krati_garg · Accepted Answer

Hi @erika_antkowiak

Please find answers inline:

We have been unable to find any that help us fully understand how the naming convention of the new asset needs to be the same as the existing asset in AEM Assets to be added as a new version.

[KG]: To get a prompt for new version while uploading another asset, there are following rules:

1. New asset should be uploaded in the same folder as the older one for creating a new version

2. File Extension should be same

3. File Name should be same

Not meeting any of the above rules would make AEM believe that its a new asset and it will not prompt you for a new version.

I've recently uploaded a new asset with the same name as the existing asset into AEM Assets and it uploaded as a new separate asset in the system.

[KG]: Please check out above response

Is there a reason why this would happen? Would metadata have anything to do with it? Has anyone else had this experience or know of any documentation that covers the naming convention and versioning relationship in depth?

[KG]: As per OOTB functionality, as far as same filename+extension matches, it would detect the new asset upload as a candidate for new version. However, if you want to customize this behavior based upon binaries, you might need to enable duplicate detection config "Day CQ DAM Create Asset" OSGI config. This config depends upon dam:sha1 value(by default - can be changed to any other metadata asset property).

dam:sha1 is SHA 1 checksum value of the binary and if this is same for any two assets, it would not even check for Filenames and would take both assets as same and shall prompt you for new version.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/detect-duplicate-assets

Hope this helps

Kamal_Kishor · Answer

@erika_antkowiak :

For asset versioning, it seems to work with same name only (I have tested on 6.5).

However, there is a way to identify if the same Asset already exists in entire Assets irrespective of its name or assets path. This would help to know if same asset already exists and at which path it is present.

Please refer: for AEMaaCS: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/admin/detect-duplicate-assets
For AEM 6.5: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/managing/duplicate-detection

The detect duplicate feature is now enabled in Assets. When a user attempts to upload an asset that exists in Experience Manager, 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.

I am not sure if this helps with your use-case but let me know if it does.
thanks.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded