translation data multiplication

Avatar

Avatar
Validate 10
Level 3
何塞
Level 3

Likes

12 likes

Total Posts

48 posts

Correct reply

1 solution
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 10
View profile

Avatar
Validate 10
Level 3
何塞
Level 3

Likes

12 likes

Total Posts

48 posts

Correct reply

1 solution
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 10
View profile
何塞
Level 3

01-06-2016

Hi guys,

I noticed the translation framework will create a new copy of the original content under the target language folder. So my data size increases by whatever size the original content was every time I use the translation framework to add a new language. Even though all languages use the same binary file and it's only the metadata that gets translated, the translation framework makes a new copy of the binary for each of the translated languages.

This is not a problem when the size of the original content is small, but when you are dealing with petabytes, adding a few more petabytes every time a new language is added is expensive.

I know in some other systems, when dealing with multilingual asset metadata, the binary is unique and it's only the metadata that gets translated.

My question to you guys is, what are the reasons why AEM needs/wants to create a copy of the asset binaries every time a new language is added?

Thanks in advance for all your help.

View Entire Topic

Avatar

Avatar
Give Back
Level 1
Sridhar1
Level 1

Likes

0 likes

Total Posts

8 posts

Correct reply

3 solutions
Top badges earned
Give Back
Affirm 3
Affirm 1
View profile

Avatar
Give Back
Level 1
Sridhar1
Level 1

Likes

0 likes

Total Posts

8 posts

Correct reply

3 solutions
Top badges earned
Give Back
Affirm 3
Affirm 1
View profile
Sridhar1
Level 1

06-06-2016

Hi,

Below are the steps confirmed by the Engineering team to manage Asset metadata translation without impacting Repository size.

  1. 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://jackrabbit.apache.org/oak/docs/osgi_config.html
  2. Disable DAM MetaData Writeback workflow
    As the name says, DAM Metadata Writeback workflow writes the metadata back in the binary file. As the metadata will change after translation, writing it back to binary will lead to different binaries for the language copies. Therefore, to use this optimization, one has to Disable DAM MetaData Writeback workflow using “Disable the workflow launchers” option documented at https://docs.adobe.com/docs/en/aem/6-2/administer/content/workflow-offloader.html
    NOTE – The above procedure will turn off XMP metadata write back on asset binaries. Therefore, future metadata changes will no longer be saved into assets. Please evaluate the consequences before disabling the workflow.
  3. Enable Set last modified date workflow
    DAM MetaData Writeback workflow sets asset’s last modified date. As this was disabled in above step, Set last modified date workflow should be enabled to keep last modified date up to date. This is because, Asset workflows and UI expect last modified date to be accurate. Keeping stale date could result in unexpected behavior.
  4. Configure Translation Integration Framework to stop translating asset binaries
    Use “Creating translation integration framework configurations” documented at https://docs.adobe.com/docs/en/aem/6-2/author/assets/managing-assets-touch-ui/multilingual-assets.ht... and uncheck “Translate Assets option” under Assets tab to stop translation of Asset binaries.

 

Sridhar