Home Portal

Skip to end of metadata
Go to start of metadata
 

Target audience: XTRF Platform's users

 

 


 

 

 

 

 

 


 

XTRF Platform offers integration with Memsource Cloud Ultimate, a popular web-based CAT tool.

Translation Memories

The TMs are stored on the Memsource's side and are updated on-the-fly after each segment confirmation.

Job Statuses

When XTRF creates a project in Memsource, all job statuses in Memsource are set to "New".

When in XTRF a job's status is changed to "Ready", in Memsource it's changed to "Completed by Linguist".

Reverting a job's status in XTRF to "Started", sets it back to "New" in Memsource, too.

When in XTRF a job's status is changed to "Cancelled" or the job is deleted, in Memsource the status is changed to "Delivered" (earlier named "Locked").

Memsource Project Templates

It is possible to attach a Memsource project template to an XTRF workflow.

In XTRF v2014 Autumn (3.4) in such case the XTRF workflow must have the same workflow steps as defined in the template, and it can have more steps - these will be added in Memsource project.
From XTRF v2015 Winter (3.5) the workflow jobs configuration from XTRF will entirely override the settings defined in the Memsource template.

Languages configuration from Memsource project template will be overridden by the language combination selected in XTRF.

Cached Settings

XTRF caches the following Memsource settings: Clients, Domains, Machine Translation Engines, Workflow Steps. From XTRF v2014 Autumn (3.4) also Project Templates are cached.

Cache is updated automatically every hour and can also be updated at any time by a user in external system settings.

CAT Analyses

If "Create CAT Receivable" and/or "Create CAT Payables" options are turned on, during the project creation a CAT analysis file will be downloaded from Memsource and stored in the Log File folder.

In case there are different payables (providers will work on different sets of files), there will be more than one CAT analysis file.

The analysis will be created in LOG format and the filename will be: Analysis#1.log by default. The analysis name can be changed in the integration settings.

From XTRF v2015 Winter (3.5), the analyses can be created in CSV format, too. The filename will then be: Analysis#1.csv by default. The analysis name and format can be changed in the integration settings.

For the list of supported formats of CAT analyses generated by Memsource that can be imported into XTRF regardless of the integration, see CAT Analysis Import.

Supported Document Formats

For the complete list of supported document formats, please see Memsource's website.

Supported Languages

For the complete list of supported languages, please see Memsource's website.

Memsource Documentation

See: http://wiki.memsource.com/

Memsource Configuration

No changes are required.

XTRF Platform Configuration

  1. Expand the Integration section and click External Systems.
  2. On the External Systems screen click Add to create a new entry.
  3. Set the Type of the system to Memsource using the drop-down menu.
  4. Set the name of the system and click the Save button to be re-directed to next step of configuration.
  5. Provide the Webservice URL under which Memsource is available (standard address is https://cloud1.memsource.com/web).
  6. Provide the User ID and Password. These are the same credentials that you use to log in to Memsource.
  7. You can access Memsource configuration directly by clicking Open in Pop-up in External Configuration section.
  8. You can specify the way the project names in Memsource will be generated by entering the Project Name Expression. The default expression is:
    ${this.name} [${this.languageCombination.sourceLanguage.symbol}]-[${this.languageCombination.targetLanguage.symbol}] ${this.idNumber} 
    which includes the XTRF task name, two-letter symbols (plus country code, if applicable) of the source and target languages, and the XTRF task ID, e.g.:
    Translation of documents [EN_UK]-[DE] 2014/123
  9. You can specify the way the analysis names are generated by entering the Analysis Name Expression.
    If the field is left empty, the default Memsource analysis names will be used, i.e. "Analysis#1".
    Note that starting from XTRF version 2014 Autumn (3.4) analysis files in LOG format (and from XTRF version 2015 Winter (3.5), optionally, alternatively in CSV format) are created during project creation step and are stored in the Log File folder in Task Input.
  10. You can specify the Analysis Format by choosing CSV or LOG.
    This option is available starting from XTRF version 2015 Winter (3.5).
  11. You can select a default machine translation engine if one was configured in Memsource.
    (The default MT engine can be changed for each workflow and for each XTRF task, if necessary.)
  12. Click the Save button. Now the connection between Memsource and XTRF is established.

XTRF accesses the following elements of Memsource configuration: clients, domains, machine translation engines, project templates and workflow steps. They are automatically updated every hour. If you changed the Memsource configuration and wish to update the cached elements, you can do it any time by clicking the Update button in the external system configuration.

Workflow Configuration

To automate the integration you should establish special workflows which will manage the communication between XTRF and Memsource. You can create as many workflows as you wish. To do that, go to Settings, expand the Workflows section, click Workflow Definitions and click Add to create a workflow.

Workflow Graph Tab

Here you can configure the steps that will be included in the workflow. The workflow should contain the jobs listed below, in this order:

  1. External Project Preparation (set the Default Provider as Automated Activity Action: External Project Preparation).
  2. The proper jobs you wish to be performed in this workflow, e.g. Translation, Proofreading, etc.
  3. External Project Finalisation (set the Default Provider as Automated Activity Action: External Project Finalisation).

Examples:

For information on the possibilities of more advanced workflow configuration with the use of the Prepare Packages action, see: Prepare Packages Action in memoQ, Memsource and XTM Integrations.

To add new step click the plus icon.

External Systems Tab

  1. In the External System field select your Memsource.
  2. You can choose if a Memsource project template should be attached to this workflow. For more information on project templates see the relevant section in Memsource Integration.
  3. The project creation step in a workflow will automatically create a CAT receivable. However, it is also possible to create a CAT receivable using an external system manually. If you don't want your workflow to start automatically after receivable creation, untick the checkbox labeled Start Workflow after Completing CAT Receivable Using External System.
Job Mapping

To ensure correct integration and information exchange you need to match the job in XTRF with corresponding workflow step in external system. Select from the list what kind of action should be performed by Memsource.
Users can define their own workflow steps in Memsource. When workflow steps are configured in Memsource, their order must be set up. The steps can be added to a project only in the preselected order. Thefefore when you set up job mapping, the drop-down selection list contains only those jobs which can be added after the previous job and before the next job.

For more information on Memsource workflow step order please refer to Memsource documentation.

Advanced Settings
  1. You can select a Machine Translation Engine to be used.

  2. Select whether a CAT Receivable should be created during project creation.

  3. Select whether CAT Payables for each job should be created during project creation.

  4. If a package preparation job is included in your workflow, in the File Type for Package Preparation field you can select what type of bilingual file should be created by this job.

Bundles Tab

Create as many bundles as you require here.

Assignment of bundles to particular jobs can be configured in the Workflow Graph tab.

  • No labels