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 adding this in future if there is a strong use case. In
the meantime you can use the workaround mentioned by @diptinarang.
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
DAM MetaData Writeback workflowAs the name says, DAM Metadata Writeback
workflow writes the metadata back in the binary file. As the metadata
Silican wrote... samery56615784 wrote... it creating the laguage
specific folder (syntax: -) 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 usu...