Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM filling in metadata on upload

LazyLibrarian1992
Level 1
Level 1

Hi, 

 

I am having an issue where when new assets are uploaded to a project, AEM seems to be automatically filling in tags, IPTC data, and titles of assets which in turn are giving incorrect asset previews. Is there a behavior that if an asset has already been in AEM, uploaded to a project again with a different name AEM with autofill tags based on some sort of signature in the jpeg? 

AEM Experience Manager metadata projects upload
1 Accepted Solution
markus_bulla_adobe
Correct answer by
Employee
Employee

Hi @LazyLibrarian1992!

There is no out-of-the-box matching mechanism that synchronizes data between an already existing asset in AEM and a newly uploaded one.

A somewhat related feature is duplicate detection [1]. Once activated it works as follows:

"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."

If a user tries to upload an asset that is already present in AEM, he will be presented with an according warning message:

chlimage_1-8_c5

(See [2])

 

For your use case you would need to build a custom solution.

You may want to check the blog post [3] linked on the above mentioned documentation page that provides some guidance on the implementation around duplicate detection.

 

[1] https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/duplicate-detection.ht...

[2] https://experienceleague.adobe.com/docs/experience-manager-64/assets/managing/managing-assets-touch-...

[3] https://experience-aem.blogspot.com/2019/06/aem-65-find-duplicate-assets-binaries-in-existing-reposi...

 

Hope that helps!

View solution in original post

2 Replies
markus_bulla_adobe
Correct answer by
Employee
Employee

Hi @LazyLibrarian1992!

There is no out-of-the-box matching mechanism that synchronizes data between an already existing asset in AEM and a newly uploaded one.

A somewhat related feature is duplicate detection [1]. Once activated it works as follows:

"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."

If a user tries to upload an asset that is already present in AEM, he will be presented with an according warning message:

chlimage_1-8_c5

(See [2])

 

For your use case you would need to build a custom solution.

You may want to check the blog post [3] linked on the above mentioned documentation page that provides some guidance on the implementation around duplicate detection.

 

[1] https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/duplicate-detection.ht...

[2] https://experienceleague.adobe.com/docs/experience-manager-64/assets/managing/managing-assets-touch-...

[3] https://experience-aem.blogspot.com/2019/06/aem-65-find-duplicate-assets-binaries-in-existing-reposi...

 

Hope that helps!

View solution in original post

LazyLibrarian1992
Level 1
Level 1
Hi Markus, Thank you for the such detailed response! We found that the user was using assets that had XMP and EXIF data on the jpeg that matched existing data on other assets in the DAM (it was an ad that used an AEM asset as a source file) we believed the behavior came from AEM reading that data and auto assigning tags and IPTC data which is an expected behavior.