5 Steps for Efficiently Translating Metadata for AEM Assets
If you plan to translate your digital assets, for example to use in multilingual product catalogs, you can rely on Adobe Experience Manager to handle your multi-language content in a professional and organized way. Experience Manager’s multilingual workflows enable you to translate binaries, metadata, and tags for digital assets into multiple locales and to manage the translated assets. For details, see Multilingual Assets.
For efficient asset management and to ensure that translated versions stay synchronized, it is a good idea to create language copies of assets before you run translation workflows.
A language copy of an asset or a group of assets is a language sibling (or a version of the asset(s) in a cognate language) with a similar content hierarchy.
However, a language copy, like an asset, exists independently in the repository. Therefore, translating assets into multiple locales creates multiple language copies, which can drastically increase the size of the CRX repository. For example, translating assets with a combined size of 10 GB into two languages can increase the repository size by approximately 20 GB (10 GB for each language).
To translate assets efficiently, you can set up an optimal storage infrastructure and improvise the translation workflows.
Asset binaries occupy much larger storage space compared to metadata and tags. Therefore, if translating metadata and tags only serves your purpose, omit to translate the binaries. You can retain the original copy of the binaries in the repository for association with metadata and tags translated to different locales. Maintaining a single copy of binaries, instead of multiple translated versions, minimizes the impact on repository size.
File Data Store and Amazon S3 Data Store provide a storage infrastructure that is best suited for these scenarios. These storage repositories store a single copy of asset binaries (including renditions) that can be shared by metadata and tags in multiple locales. Therefore, creating asset language copies and translating metadata and tags does not affect repository size.
Perform these steps to set up your data store and configure your translation workflows for efficient translation:
- Do one of the following:
- Disable the DAM MetaData Writeback workflow.
As the name suggests, the DAM Metadata Writeback workflow rewrites the metadata to the binary file. Because the metadata changes after translation, writing it back to the binary file generates a different binary for a language copy.
Note: Disabling the DAM MetaData Writeback workflow turns off XMP metadata write-back on asset binaries. Consequently, future metadata changes are no longer be saved within the assets. Please evaluate the consequences before disabling this workflow.
- Enable the Set last modified date
The DAM MetaData Writeback workflow configures the last modified date for an asset. Because you disable this workflow in step 2, AEM Assets is no longer able to keep the last modified date of assets up-to-date. Therefore, enable the Set last modified date workflow to ensure that last modified dates of assets are up-to-date. Assets with outdated last modified dates can cause errors.
- Configure the translation integration framework to stop translating asset binaries. Unselect the “Translate Assets option” under the Assets tab to stop the translation of Asset binaries.
- Translate asset metadata/tags using Multilingual Asset workflows.