For AEM 6.3 , the fix is part of AEM 6.3SP1 CFP1 release in November

It's a bug in AEM 6.2. The fix is scheduled to go live in CFP-8 next month.

In AEM 6.1 we didn't have the concept of folders, so the projects had a name. But with 6.2 and above, the folders are one level above the project nodes and the API doesn't read that. Since the TMS/GMS vendors didn't bother for the folder name we didn't build support in the API. We will look into add...

Hi,Below are the steps confirmed by the Engineering team to manage Asset metadata translation without impacting Repository size.Setup File Data Store / Amazon S3 Data Store by following the instructions from https://docs.adobe.com/docs/en/aem/6-2/deploy/platform/data-store-config.html and/or https:/...

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 a...

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 t...