Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED

AEM 6.5.4 duplicate assets upload in content dam using create version is overriding the updated metadata dc:title and dc:description

Avatar

Level 1

Hi, 

Using AEM 6.5.4
Upload a pdf in content dam and edit asset properties, we can see the metadata title and description is picked up from the pdf metadata. 

Manually change the asset properties metadata title and description and save. 
Now Uploading the same pdf again, we get a popup for duplicate asset upload, chose create version to continue.

Once the asset is uploaded, we notice the asset title and description is overridden with duplicate upload.(from the pdf metadata) and the changed title and description is not retained.
 

How can we reset the metadata title and description in this scenario to retain the updated title and description.

 

Tried adding com.adobe.acs.commons.workflow.process.impl.DamMetadataPropertyResetProcess process step before workflow complete step in DAM Update Asset Workflow. with below process args

akashdeepm_0-1624020115046.png

 

But still the metadata title and description is overridden with the pdf values and does not retain the manual title and description change.
 https://adobe-consulting-services.github.io/acs-aem-commons/features/workflow-processes/dam-metadata-property-reset/index.html
 
Am I missing something with ACS Commons solutions or there is any other recommendation to achieve this.  

cc @kautuk_sahni   @arunpatidar 
@Jörg_Hoh @BrianKasingli 


Thanks

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

In your opinion, how should the system behave when you upload with a name, which is already used? Do you expect some properties to get merged in the background, so you have relicts of the old version still being present? Or should rather the new version always take precendence?

 

From what I understand from your description, the product philosophy is to override all settings with the data from the new asset. I can totally relate to this design decision, because in this case the behaviour and the resulting properties are much more predictive than in the case you want to achieve.

 

Can you share the business requirement behind it?

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

In your opinion, how should the system behave when you upload with a name, which is already used? Do you expect some properties to get merged in the background, so you have relicts of the old version still being present? Or should rather the new version always take precendence?

 

From what I understand from your description, the product philosophy is to override all settings with the data from the new asset. I can totally relate to this design decision, because in this case the behaviour and the resulting properties are much more predictive than in the case you want to achieve.

 

Can you share the business requirement behind it?

Avatar

Level 1

Looking at the sourcecode of the plugin it doesn't quite address this issue (we are having the same issue and hoped it would help):

https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/ad...

 

The business usecase is that a lot of PDFs are generated by automated processes that don't necessarily give good 'titles' built in (not titles you would ever want a customer seeing). AEM then becomes a good place to store the real title, but uploading a new version of the PDF erases that work and requires a ton of extra work for authors (and it is confusing because certain metadata fields are preserved, seems to be dc:title and dc:description only are overwritten).