This article will guide you through the process of configuring your own Machine Translation (MT) provider on Bureau Works, and the credentials required for their utilization.

1. Certified providers

2. Configuring your MT

3. Setting up the configuration at both the Organization and Organizational Unit levels

4. Credential details

1. Certified providers

Currently, it is possible to link credentials for the following Machine Translation providers to Bureau Works:

1. Amazon Translate
2. Google Cloud Translation API
3. Microsoft Azure Cognitive Services Translation API
4. DeepL API
5. Google AutoML API
6. ODIN

These providers offer powerful machine translation services that can be integrated with Bureau Works to enhance translation capabilities.

Bureau Works utilizes Microsoft Azure as its standard Machine Translation (MT) service, accessible to all users who activate the MT features in their individual accounts.

It is possible to link a personal or business credential from another provider to Bureau Works. This can be set at the Account level, making it available for your entire account, as well as at the Organization (Org) and Organizational Unit (Org Unit) level, making it available only for the projects associated with it.

2. Configuring your MT

In the left menu, go to Settings and then click on Translation Settings. This will expand the menu and you will be able to find the Machine Translation (MT) tab.

On the MT settings tab, you must then enter the fields in order to associate your credentials with Bureau Works.

The new MT provider can be defined as the default provider (being used in all your account projects) or you can define specific language pairs for it. 

1. Define a name for this configuration;
2. Select the provider;
3. Set as default;
4. Define a specific language pair for this MT configuration;
5. Insert the credentials;
6. You may also upload the credentials in JSON format.

3. Setting up the configuration at both the Organization and Organizational Unit levels

Once the new credential has been added to your account, you can choose to apply it at either the Organization or Organizational Unit level.

Within the MT settings, you will find the option to select and customize the preferred credential for a specific Organization or Organizational Unit. This selection enables you to utilize the designated credential for projects associated with the corresponding Organization or Organizational Unit.

• Organization: Open the desired organization and go to the MT settings tab:

• Organizational Unit: Access the specific Organizational Unit in Bureau Works and navigate to the MT settings tab:

In both screens, you have the same features:

1. 1. 1. Sets the default MT configuration for the Organization or Organizatinal Unit. This setting is used when there's no language pair formally defined.
      2. Set the specific language pair for available MT's. Manually defined language pairs will be used first in order of priority.
      3. Manually add a MT associated with a language pair.

When there's no default MT setting or no language pair formally defined, the system will use the default settings for the account.

The configuration by language pair can be done for as many pairs as needed. You can also set up multiple MT providers for different language pairs. For example, you can use Google to translate from en-US to pt-BR and use AWS to translate from en-US to ES (Spanish). You just need to have the necessary providers registered in your account beforehand.

By having multiple MT providers linked to your Bureau Works account, you gain the flexibility to choose the most suitable provider for each language pair based on their strengths and capabilities. This allows you to leverage different translation engines for different language combinations, optimizing the translation quality and results.

To configure the language pairs, click on the Add Language Pair button:

You must then fill in the information:

1. Choose the MT provider;
2. Select the source language;
3. And the target language;
4. You may set this configuration as active, or inactivate an existing one.

⚠️ Remember to click on "Save".

4. Credential details

It is important to remember that the processes for obtaining credentials and keys may vary for each translation service provider. It is recommended to consult the specific provider's documentation or contact their support for precise instructions on how to obtain the correct credentials to use their translation services.

These credentials, or keys, need to be obtained directly from each provider and are not offered by Bureau Works.

• For Amazon AWS Translate, you can access it via regular AWS Services. To do this, you'll need to provide your client AWS credentials, which consist of the Access Key ID and Secret Access Key. The expected information is in the format:

  {
  "access_key_id": "YOUR_ACCESS_KEY",
  "secret_access_key": "YOUR_SECRETE_KEY"
  }

• For Google, although Google provides two ways to access its translating resources in the cloud, we currently only support the Service Account approach, the recommended method by Google as it ensures better security, with an OAuth2 format. To utilize this method, you'll need a Service Account Key, which is a more complex JSON file generated in the Google Cloud Console.
  Fill out the credentials in the format shown below, replacing the fields marked with xxx with your information.
  

  {
  "type": "service_account",
  "project_id": "xxxxxx",
  "private_key_id": "xxxxxx",
  "private_key": "xxxxxxx",
  "client_email": "xxxxxx",
  "client_id": "xxxxxx",
  "auth_uri": "xxxxxxxx",
  "token_uri": "xxxxxxx",
  "auth_provider_x509_cert_url": "xxxxxxx",
  "client_x509_cert_url": "xxxxxx"
  }

• For Microsoft Translate, the translation process takes place through their REST API. To use this service, you must provide a JSON file containing their subscription information to Microsoft/Azure. The expected information is in the format:

  {
    "endpoint": YOUR_ENDPOINT, 
    "subscription_key": YOUR_SUBSCRIPTION_KEY, 
    "location": LOCATION
  }

• For DeepL, the translation process takes place through their REST API. Currently our Machine Translation services offer compatibility with DeepL API - both the Pro¹ and Free versions.
  
  This MT service also comes with a particular configuration: the formality setting. The translation's tendency toward formal or informal language is determined by this parameter. Only the target languages DE (German), FR (French), IT (Italian), ES (Spanish), NL (Dutch), PL (Polish), PT-BR and PT-PT (Portuguese), JA (Japanese), and RU (Russian) are currently supported by this feature.
  
  Possible Options are:
• • default (default)
  • more - for a more formal language
  • less - for a more informal language
  • prefer_more - for a more formal language if available, otherwise fallback to default formality
  • prefer_less - for a more informal language if available, otherwise fallback to default formality
•  The integration process requires a JSON file containing the client key or it can be inserted typing the key in the format:
  

  { 
  "key": "YOUR_KEY_HERE"
  
  "formality": "more" 
  }     

• For ODIN, the communication goes through their REST API. In order to insert an ODIN credential into Bureau Works, you must provide your credentials with the following information: Project-id, X-API-KEY and X-API-SECRET. The expected information is in the format:

  { 
  "project-id": "YOUR_PROJECT_ID", 
  
  "X-API-KEY": "YOUR_API_KEY", 
  
  "X-API-SECRET": "YOUR_API_SECRET" 
  }

Regardless of the engine used, we ensure that sensible data, such as client credentials, is stored in a secure and encrypted database. It is not directly accessed by our system, but through a unique MT config ID generated at the moment the credentials are entered into the system. This ID can also be used to remove the credentials at any time you feel the need to so.

We are continually working on expanding our support for various Machine Translation engines and methods to enhance the overall translation experience for our users. Stay tuned for updates on new integrations and features in the future!

¹ Please note that DeepL API Pro is distinct from the DeepI Pro which is not supported and requires a different partnership with DeepL.

If you have any inquiries or require assistance with this configuration, feel free to reach out directly to our support team at help@bureauworks.com.