Some metadata not extracted by DAM update asset workflow

[aanchal-sikka]

Hello,

We have encountered a few images where agencies have added metadata like clipping paths, and the name of the clipping path is visible in the metadata when accessed using ExifTool. However, this information is not being extracted by the DAM Update Asset workflow and added to the metadata node.

• Are there specific rules that determine which types of metadata can be extracted?
• For metadata that does not meet these rules, what is the recommended approach to extract and include such metadata?

[SreenivasBr]

What type of images are being uploaded? I mean mime-type

How is the metadata stored in the binary? 

Is the metadata having custom namespace?

[aanchal-sikka · Accepted solution]

AEM has been designed to extract XMP metadata and unable to extract Photoshop metadatata. Thus, if one needs to extarct "Clipping Path Name", they will need to implement as custom solution using APIs like

<dependency>
    <groupId>com.drewnoakes</groupId>
    <artifactId>metadata-extractor</artifactId>
    <version>2.19.0</version>
</dependency>

[aanchal-sikka]

Clipping paths aren’t extracted out-of-the-box in AEM DAM since they’re stored in Photoshop metadata, not XMP headers. But with a custom workflow, you can extract and store them for seamless use in Dynamic Media.  For details, refer to:

• Clipping Path Extraction in AEM DAM: A Custom Workflow Approach
• Understanding Clipping Path: Importance and related metadata extraction