SOLVED
AEM filling in metadata on upload
1 Accepted Solution
Correct answer by
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:
(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.
Hope that helps!
Correct answer by
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:
(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.
Hope that helps!
