Amazon S3 translation strategies

There are multiple ways in which you can configure the integration with Amazon S3, depending on your specific business needs and on your preferred way of working.

1. Multilingual

You select a source and a target repository configuration with details such as:
  • Access key ID
  • Secret access key
  • Bucket ID
  • Source folder name
  • Success folder name
For the success folder name, you have two options:A diagram that illustrates the status and structure of the source folder before translation.
  1. Enter the name of the Source folder. In this case, after the translation is complete, the connector creates target folders and moves the translated files to these folders:A diagram that illustrates the Copy to Language Folder strategy.
  2. You specify a different Success folder. In this case, after the translation is complete, the connector creates a subfolder for each target language under the Success folder and adds the translated files to those subfolders. A diagram that illustrates the Copy to In/Out Folder strategy.
Then, the translation process begins:
  • New or changed files are retrieved from the repository and sent to Trados for translation. Translation projects are created.
  • Medatada related to folders and name files is persisted to reconstruct the translations in the Out folder (the metadata tree is persisted).
  • No files are moved from the Source folder during the translation process.
You can select your strategy on the Strategy tab when creating a new automation configuration. The translation workflow corresponding to the Multilingual strategy is displayed:
  • Preprocessing
    • Retrieve source directory content
    • Verify if content was already translated
    • Assign unique ID for translatable content
    • Save directory structure
  • Translation
    • Create Translation project with all the files
  • Finalization
    • Retrieve translated content
    • Upload translated files to Translated directory under the Target language folder
    • Complete Translation project
    • Send success email notification
  • Error
    • Send error email notification

2. COTI

Use this strategy if your content respects the COTI Level 2 standard.

The COTI translation package is an archive file that contains one or more translation projects. The name of the translation package consists of three parts:
  • The time stamp
  • The name of the actual package (the individual name of the content management system)
  • The .coti file extension
For example: 2009-11-13T103935Z_translation-COTI-specification.coti
The name of each translation project also consists of three parts:
  • The project ID
  • The source language
  • The target language
For example: 4711_de-DE_en-GB. The languages are set according to RFC 1766 and ISO 639.

Whereas COTI Level 1 defines an interchange format between a content management system (CMS) and a translation management system (TMS), COTI Level 2 extends that format slightly and defines the process of exchanging COTI packages.

The exchange process as relevant to this specification includes the following:
  1. The generation of a COTI package from the CMS.
  2. The transfer of the package to the TMS.
  3. The transfer of the result back to the CMS.
  4. Error handling and logging during the process.
Level 2 extends the format defined in Level 1 as follows:
  • archive=yes|no on the COTI element to signal that processed translation packages should be moved to an archive subfolder instead of being deleted.
Mandatory prerequisites for setting up the connector:
  • Source Folder = untranslated
  • Processing Folder = archived\untranslated
  • Success Folder = translated
  • Exception Folder = error\untranslated
You can select your strategy on the Strategy tab when creating a new automation configuration. If you select the COTI strategy, the translation workflow corresponding to this strategy is displayed:
  • Preprocessing
    • Retrieve content from untranslated directory
    • Identify .coti files
    • Download .coti files
    • Extract & Process archives on server
    • Assign unique ID for translatable content
    • Save archive structure
  • Translation
    • Create individual Translation project for each COTI project from each archive
    • Move files to archive/untranslated directory or remove files
  • Finalization
    • Retrieve translated content
    • Recreate .coti based on the saved structure
    • Upload files to translated directory
    • Complete Translation project
    • Send success email notification
  • Error
    • Move files to errors/untranslated directory
    • Send error email notification