Asset Update | Community
Skip to main content
br68931391
br68931391
March 6, 2019
Solved

Asset Update

  • March 6, 2019
  • 1 reply
  • 867 views

Hello,

Currently, I am using 6.3 version. To activate last modified date for any asset I have enabled the OOTB workflow( DAM Metadata Writeback) and updated an asset. So, after updating I could see last modified date but I observed there were large number of tar files being generated in the segmentstore of repository. Tar file size of 200MB-250MB kept on generating till I disable the OOTB workflow.

It would be great if anyone can suggest me how to get rid of this issue.

Thank You

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 Gaurav-Behl

If your requirement is just to update last modified date, then you could use 'DAM SET LAST MODIFIED DATE'  (http://localhost:4502/editor.html/libs/settings/workflow/models/dam/dam_set_last_modified.html​) with appropriate launcher configuration(s).

DAM Metadata Writeback would create versions of each asset whenever it gets modified and that could be the reason you're able to see large number of tar files. If you want to continue using it, then you may have to schedule periodic TAR maintenance/cleanup tasks.

1 reply

Gaurav-Behl
Gaurav-BehlAccepted solution
March 6, 2019

If your requirement is just to update last modified date, then you could use 'DAM SET LAST MODIFIED DATE'  (http://localhost:4502/editor.html/libs/settings/workflow/models/dam/dam_set_last_modified.html​) with appropriate launcher configuration(s).

DAM Metadata Writeback would create versions of each asset whenever it gets modified and that could be the reason you're able to see large number of tar files. If you want to continue using it, then you may have to schedule periodic TAR maintenance/cleanup tasks.

Terms & ConditionsAccessibility statement

Loading footer...