dam:size is not added to metadata of Asset | Community
Skip to main content
selvaganesh
selvaganesh
Level 5
June 25, 2018
Solved

dam:size is not added to metadata of Asset

  • June 25, 2018
  • 6 replies
  • 5236 views

dam:size is not added to metadata of Asset in AEM 6.2. We have the Metadata Processor step enabled in workflow

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by shroti

I am not able to reproduce this in AEM 6.2 (latest SP + CFP), I can see dam:sha1, dam:size and dam:extracted are getting saved on metadata node for all type of files including mp3/mp4.  Is there any customization around asset processing/handling done in your case? Can you please check if there is any error in logs (error.log) logged during asset processing (dam_update_asset) workflow? Share the same to understand the issue better.

Thanks,
Ashutosh

6 replies

C
Adobe Employee
castanedAdobe Employee
Adobe Employee
June 25, 2018

selvaganesh you could run the Add asset size workflow [1] to get the property for all the existing assets.

[1]host:port/libs/cq/workflow/admin/console/content/models.html/etc/workflow/models

selvaganesh
selvaganeshAuthor
Level 5
June 26, 2018

dam:extracted and dam:sha1 is also missing

smacdonald2008
smacdonald2008
Level 10
June 26, 2018

Did you try the workflow that Yanira Castaneda suggests.

selvaganesh
selvaganeshAuthor
Level 5
June 26, 2018

the add size workflow adds the size but not dam:sha1.

Metadata processor workflow step fails to add the property for mp3,mp4 (but works fine for ai/eps files). Just wondering if there is any configuration which disables adding dam:size,dam:sha1

smacdonald2008
smacdonald2008
Level 10
June 26, 2018

I asked the asset team to look here to answer questions about those specific file types.

S
Adobe Employee
shrotiAdobe EmployeeAccepted solution
Adobe Employee
June 27, 2018

I am not able to reproduce this in AEM 6.2 (latest SP + CFP), I can see dam:sha1, dam:size and dam:extracted are getting saved on metadata node for all type of files including mp3/mp4.  Is there any customization around asset processing/handling done in your case? Can you please check if there is any error in logs (error.log) logged during asset processing (dam_update_asset) workflow? Share the same to understand the issue better.

Thanks,
Ashutosh

Terms & ConditionsAccessibility statement

Loading footer...