Adobe Experience Manager (AEM) Assets lets you identify assets that share common attributes and mark them as related using the new Related Assets feature. It also lets users define a source/derived relationship between assets, making it easy for users to identify the origin of an asset. Running translation workflow on a derived asset fetches any asset that the source file references and includes it for translation, thereby reducing the efforts to maintain multi-site.
In this video, we are going to be discussing about some of the Asset management enhancements introduced in AEM 6.3. You can efficiently create content for multi-national and multi-lingual sites, through the combined use of multi-site manager and the translation workflow. Content authors often need to manage a multi-site asset. Let’s navigate to AEM Assets, create a master asset folder in one language, for a specific country. Then use that content as a basis for the other asset, using translation.
Let’s open the English folder and upload two files from your local machine. Click create and then upload your files. We have uploaded an InDesign file and an image file. Cycling images used in the InDesign file and is related. With the new asset management enhancements, we can easily associate assets that are related. Let’s select the cycling image and click on the relate option, from the options displayed. We would like to relate that cycling image to our InDesign file, as related by source. So let’s select the source option and navigate through the assets selected dialogue box to find our InDesign file and select it.
Now, we have successfully related assets. Let’s explore how asset translation enhancement in AEM 6.3 work. Let’s open the cycling image, and then select the references option from the left dropdown. Under references, select Language Copies, and you should be able to see the asset referenced, under the route English language copy. Let’s initiate a translation workflow, by clicking on the Create & Translate option.
Select your target language from the dropdown. Under the Project dropdown, select Create a new translation project option, and provide a project title to continue to the next step.
Let’s navigate to the project console, to start the translation workflow that we created in the previous step. Open the translation job folder and check out the list of assets that are being prepared for translation.
Under assets and cycling image, we can also notice the InDesign file, which is related to the cycling image as a source. With the asset management enhancements introduced in AEM 6.3. With the asset management enhancements introduced in AEM 6.3, invoking a translation workflow for an AEM asset, also identifies the related assets and is sent for translation. Select the translation project, and click on Start translation job.
Give it a couple of seconds for the translation job to complete.
Let’s navigate to the assets console and open the We.Retail Spanish folder. You should be able to notice the cycling image created under We.Retail Spanish folder. You can also notice the image title and description that has been translated.
The key point to note here, is that translation workflow was initiated only for the cycling image, but we also see the InDesign file created and translated under the Spanish language copy. Content authors are given more ability to author and manage assets by automatically invoking the related files, for an asset file. This would work for asset reference by sites and content fragments as well.
Related Assets helps users to manage better, cross-link assets with shared traits, properties and streamline workflows: