XMP writeback to renditions

Last update: May 3, 2023

Topics:
Metadata

CREATED FOR:

User
Admin

CAUTION

AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.

This XMP writeback feature in Adobe Experience Manager Assets replicates the metadata changes to the renditions of the original asset. When you change the metadata for an asset from within Assets or while uploading the asset, the changes are initially stored in the metadata node in the asset hierarchy.

The XMP writeback feature lets you propagate the metadata changes to all or specific renditions of the asset. The feature writes back only those metadata properties that use jcr namespace, that is, a property named dc:title is written back but a property named mytitle is not.

Consider a scenario where you modify the Title property of the asset titled Classic Leather to Nylon.

metadata

In this case, the Experience Manager Assets saves the changes to the Title property in the dc:title parameter for the asset metadata stored in the asset hierarchy.

metadata_stored

However, Experience Manager Assets does not automatically propagate any metadata changes to the renditions of an asset. See how to enable XMP writeback.

Enable XMP writeback

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.

Open Configuration Manager from https://[aem_server]:[port]/system/console/configMgr.
Open the Adobe CQ DAM Rendition Maker configuration.
Select the Propagate XMP option, and then save the changes.

Enable XMP writeback for specific renditions

To let the XMP Writeback feature propagate metadata changes to select renditions, specify these renditions to the XMP Writeback Process workflow step of DAM Metadata WriteBack workflow. By default, this step is configured with the original rendition.

For the XMP Writeback feature to propagate metadata to the rendition thumbnails 140.100.png and 319.319.png, perform these steps.

In Experience Manager, navigate to Tools > Workflow > Models.
From the Models page, open the DAM Metadata Writeback workflow model.
In the DAM Metadata Writeback properties page, open the XMP Writeback Process step.
In the Step Properties dialog box, tap/click the Process tab.
In the Arguments box, add rendition:cq5dam.thumbnail.140.100.png,rendition:cq5dam.thumbnail.319.319.png. Tap/click OK.
To regenerate the pyramid TIFF renditions for Dynamic Media images with the new attributes, add the Dynamic Media Process Image Assets step to the DAM Metadata Writeback workflow.
PTIFF renditions are only created and stored locally in a Dynamic Media Hybrid mode. Save the workflow.

The metadata changes are propagated to the renditions thumbnail.140.100.png and thumbnail.319.319.png of the asset, and not the others.

NOTE

For XMP writeback issues in 64 bit Linux, see How to enable XMP write-back on 64-bit RedHat Linux.

For more information about supported platforms, see XMP metadata write-back prerequisites.

Filter XMP metadata

Experience Manager Assets supports both blocked list and allowed list filtering of properties/nodes for XMP metadata that is read from asset binaries and stored in JCR when assets are ingested.

Filtering using a blocked list lets you import all XMP metadata properties except the properties that are specified for exclusion. However, for asset types such as INDD files that have huge amounts of XMP metadata (for example 1000 nodes with 10,000 properties), the names of nodes to be filtered are not always known in advance. If filtering using a blocked list allows a large number of assets with numerous XMP metadata to be imported, the Experience Manager instance or cluster can encounter stability issues, for example clogged observation queues.

Filtering of XMP metadata via allowed list resolves this issue by letting you define the XMP properties to be imported. This way, any other or unknown XMP properties are ignored. For backward compatibility, you can add some of these properties to the filter that uses a blocked list.

NOTE

Filtering works only for the properties derived from XMP sources in asset binaries. For the properties derived from non-XMP sources, such as EXIF and IPTC formats, the filtering does not work. For example, the date of asset creation is stored in property named CreateDate in EXIF TIFF. Experience Manager stores this value in the metadata field named exif:DateTimeOriginal. As the source is a non-XMP source, filtering does not work on this property.

Open Configuration Manager from https://[aem_server]:[port]/system/console/configMgr.
Open the Adobe CQ DAM XmpFilter configuration.
To apply filtering via an allowed list, select Apply Allowlist to XMP Properties, and specify the properties to be imported in the Allowed XML Names for XMP filtering box.
To filter out blocked XMP properties after applying filtering via allowed list, specify those in the Blocked XML Names for XMP filtering box. Save the changes.

NOTE
The Apply Blocklist to XMP Properties option is selected by default. In other words, filtering using a blocked list is enabled by default. To disable such filtering, deselect the Apply Blocklist to XMP Properties option.

recommendation-more-help