How to apply the multilanguage on Metadata fields and value in AEM

[sameryadav]

Hi,

We have uploaded the assets in to AEM DAM with matadata values. The few metadata fields are globally common for other GEO in different language . 

Our requirement is to show the metadata fileds and values (both) as per GEO specific language. How We can achieve it in AEM?

Thanks

~S

[kautuk_sahni]

Hi

I have asked internally to answer this question.

Thanks and Regards

Kautuk Sahni

[sameryadav]

Hi Kautuk,

Did you get any response on it?

Thanks

~S

[smacdonald2008]

this solution will require interacting with the AEM translation service and a lot of customization. 

https://docs.adobe.com/docs/en/aem/6-0/administer/integration/third-party-services/machine-translati...

Lets see what Kautuk finds. 

[kautuk_sahni]

samery56615784 wrote...

Hi Kautuk,

Did you get any response on it?

Thanks

~S

Hi

I am waiting for their reply. i will notify you asap.

Thanks and Regards

Kautuk Sahni

[sameryadav]

Hi Kautuk,

Any chance to get the response from team?

Thanks

~S

[Sridhar1]

Hi samery56615784,

You can send the Assets AND/OR the Asset and Tag metadata for translation through one of the several Translation Connectors that work with AEM. When the metadata is translated, it is stored in the JCR along with the original metadata as properties. The Asset metadata is stored at the Asset level,but the Tag metadata is stored under /etc/tags and is globally available for different GEOs. The translations are stored with a .<language> suffix like jcr:title.de, jcr:description.fr etc. 

Will this work for your usecase ?

[kautuk_sahni]

Hi

Apart from the Silican's reply,

Internally team also recommend to refer : https://docs.adobe.com/docs/en/aem/6-1/author/projects/language-copy.html

Thanks and Regards

Kautuk Sahni

[sameryadav]

Hi Kautuk, Silican

We followed the steps as per document and able to display the metadata values in different languages for different countries.But not the metadata labels like "Title" and "Description" etc.

it creating the laguage specific folder (syntax: <folder name>-<language name>) but it is not creating the metadata labels with language specific like "jcr:title.de"

Q1: Are any ways to convert the metadata labels also?

Q2: Do content author always need to execute the translation job upon new asset upload or it is configurable automatically?

Thanks

~Samer

[Jitendra_S_Toma · Accepted solution]

Hi,

There isn't a way to change level of this form. You have to go metadata form for assets and change label there.

For more information, go through this document

https://docs.adobe.com/docs/en/aem/6-1/administer/content/assets/metadata-schemas.html

---Jitendra

[Sridhar1]

samery56615784 wrote...

it creating the laguage specific folder (syntax: <folder name>-<language name>) but it is not creating the metadata labels with language specific like "jcr:title.de"

Q2: Do content author always need to execute the translation job upon new asset upload or it is configurable automatically?

1) The asset metadata is different from the Tag metadata. The tag metadata is the global list of tags available for assets, pages, etc and is stored under /etc/tags. The Asset specific metadata usually have a "dam:" prefix and are specific to the asset. 

2) The 'WCM: Sync Translation Job"  workflow is invoked when you send a job for translation. So if you want to automatically start this workflow upon asset upload, you can very well integrate the workflow with the Assets workflow or just the "com.adobe.cq.wcm.translation.impl.process.SyncTranslationProcess" process into your Assets Workflow

[sameryadav]

Silican wrote...

samery56615784 wrote...

it creating the laguage specific folder (syntax: <folder name>-<language name>) but it is not creating the metadata labels with language specific like "jcr:title.de"

Q2: Do content author always need to execute the translation job upon new asset upload or it is configurable automatically?

1) The asset metadata is different from the Tag metadata. The tag metadata is the global list of tags available for assets, pages, etc and is stored under /etc/tags. The Asset specific metadata usually have a "dam:" prefix and are specific to the asset. 

2) The 'WCM: Sync Translation Job"  workflow is invoked when you send a job for translation. So if you want to automatically start this workflow upon asset upload, you can very well integrate the workflow with the Assets workflow or just the "com.adobe.cq.wcm.translation.impl.process.SyncTranslationProcess" process into your Assets Workflow

Yes. Than you all for your quick response.

Thanks

~S