This Adobe Experience Manager (AEM) Assets feature replicates any changes you make to the asset metadata to the renditions of the asset.
When you change the metadata for an asset within AEM Assets or while uploading it, the changes are stored within the folder hierarchy defined for the asset.
For example, using the Asset editor, you can modify the Title property of the asset titled "Target" to "Target_1."
In this case, the AEM Assets saves the changes to the Title property in the dc:title parameter for the asset metadata stored in the asset hierarchy.
However, AEM Assets does not automatically propagate any metadata changes to the renditions of an asset.
The XMP writeback to renditions feature helps propagate the metadata changes to all or specific renditions of the asset. However, the changes are not stored under the metadata node in the asset hierarchy. Instead, this feature embeds the changes in the binary files for the renditions.
To enable the metadata changes to be propagated to the renditions of the asset when uploading it, modify the Adobe CQ DAM Rendition Maker configuration in Configuration Manager.
If you want the feature to propagate metadata changes to specific renditions of the asset, add the name of the renditions to the XMP Writeback Process workflow step of DAM Metadata WriteBack workflow. By default, this step is configured with the original rendition.
For example, if you want the metadata changes to propagate to the renditions thumbnail.140.100.png and thumbnail.319.319.png, perform these steps:
The metadata changes are propagated to the renditions renditions thumbnail.140.100.png and thumbnail.319.319.png of the asset, and not the others.
To troubleshoot issues around XMP metadata extraction and writeback on 64 bit Linux, see How to enable XMP metadata extraction and write-back on 64-bit RedHat Linux.
For more information about supported platforms, see XMP metadata write-back prerequisites.