Solved! Go to Solution.
Views
Replies
Total Likes
Your usecase might not be achieved with Bulk Metadata Export.
- jcr:created property resides below Asset Node and not the Metadata Node.
-dam:created property is not a mandatory property which is not going to be populated everytime
There is another OOTB feature - Asset Reports, which exports Asset Data and not particularly Metadata, into CSV format. This encompasses all Asset Properties and gives you a provision to add custom properties as well. Find the link below
https://experienceleague.adobe.com/docs/experience-manager-learn/assets/advanced/asset-reports.html?...
Views
Replies
Total Likes
Your usecase might not be achieved with Bulk Metadata Export.
- jcr:created property resides below Asset Node and not the Metadata Node.
-dam:created property is not a mandatory property which is not going to be populated everytime
There is another OOTB feature - Asset Reports, which exports Asset Data and not particularly Metadata, into CSV format. This encompasses all Asset Properties and gives you a provision to add custom properties as well. Find the link below
https://experienceleague.adobe.com/docs/experience-manager-learn/assets/advanced/asset-reports.html?...
Views
Replies
Total Likes
Awesome idea @krati_garg !
1. I can get the upload report which has the jcr:created property, sort it with path column.
2. Then sort the export sheet with path. Both sheets will now be in same sequence.
3. From here I can copy thejcr:created column from the report sheet to the export sheet and use it for filtering for specific dates for updating metadata in the export sheet.
4. Finally, when all metadata updates are done, I'll remove the jcr:created column from the export sheet before uploading it back again to update metadata.
I gave this a quick try as well just now and seems reliable.
Thank you!
Views
Replies
Total Likes