Abstract
Custom Asset Compute workers can produce XMP (XML) data that is sent back to AEM and stored as metadata on an asset.
Common use cases include:
Integrations with 3rd party systems, such as a PIM (Product Information Management system), where additional metadata must be retrieved and stored on the asset
Integrations with Adobe services, such as Content and Commerce AI to augment asset metadata with additional machine learning attributes
Deriving metadata about the asset from its binary and storing it as asset metadata in AEM as a Cloud Service
In this tutorial we’ll create an Asset Compute metadata worker that derives the most commonly used colors in an image asset, and writes the names of the colors back to the asset’s metadata in AEM. While the worker itself is basic, this tutorial uses it to explore how Asset Compute workers can be used to write back metadata to assets in AEM as a Cloud Service.
Logical flow of a Asset Compute metadata worker invocation
The invocation of Asset Compute metadata workers is nearly identical to that of binary rendition generating workers, with the primary difference being the return type is an XMP (XML) rendition whose values are also written to the asset’s metadata.
Asset Compute workers implement the Asset Compute SDK worker API contract, in the renditionCallback(...) function, which is conceptually:
Input: An AEM asset’s original binary and Processing Profile parameters
Output: An XMP (XML) rendition persisted to the AEM asset as a rendition and to the asset’s metadata
Read Full Blog
Q&A
Please use this thread to ask the related questions.
Kautuk Sahni