Set up your Service Account for Google
According to Google's documentation, existing Cloud Translation - Basic (v2) users who want to use the latest Translation features, such as glossaries and AutoML models, must migrate their applications to use Cloud Translation - Advanced (v3). For a comparison, see Compare Basic and Advanced.
Migrating to the Advanced edition includes using Identity and Access Management (IAM) and the Advanced edition client libraries. The following sections outline migration tasks and the key differences between the two editions.
Once you have chosen the version of Google Translation API, you can proceed with creating a Service Account (or selecting the existing one).
-
Go to https://console.cloud.google.com/projectselector2/iam-admin/serviceaccounts
-
Choose a particular Google user (if required):
-
Select a project:
-
If you already have service accounts for this project, then you will see them here. To create a new Service Account, click on "Create Service Account":
-
Fill in the form and click "Create and continue" to add roles:
What roles can be chosen?
If you plan to create glossaries you need the following roles:
- AutoML Viewer (list custom models)
- AutoML Predictor (translate with custom models)
- Cloud Translation API Editor (use and create glossaries)
- Storage Object Viewer (use glossaries)
- Storage Object Creator (create glossaries)
If you need full control over the glossaries you'd need the following roles:
- AutoML Viewer (view custom models)
- AutoML Predictor (translate with custom models)
- Cloud Translation API Editor (use, create, update and delete glossaries)
- Storage Object Admin (use, create, update and delete glossaries)
To train custom models you need the following roles:
- AutoML Editor
- Cloud Translation API Admin
- Editor
- Storage Admin
-
Click "Continue" after picking the needed roles
-
Finish filling service account details by pressing Done:
- Create a service account key:
NB:In Google, there is no way to view your previously generated key. If you lost the key or it became insecure, you need to replace it by generating a new key.
Select the new service account and select the KEYS tab on the top panel. Here in this section press the ADD KEY option and select "Create new key" option from the drop-down list: - In the new window select JSON from the key type options and press create:
This will save your JSON file on your local computer. You will need this file further to activate the Connected Account in the Console
Add Service Account Key to the Intento Connected Accounts
-
Choose Google Cloud Advanced Translation API or Google Cloud AutoML Translation API
-
Click "Connect your own account"
-
Enter your own credential id and copy Service Account Key and click "Check and connect":
Create a Cloud Storage bucket to store files
Go to Google Cloud Storage and select Create bucket.
Enter a name for your bucket.
In Choose where to store your data, select any option convenient for you.
In Choose a default storage class for your data, choose any storage class for your bucket.
In Choose how to control access to objects, please select the Uniform option.
In Choose how to protect object data, please select None by default. For details about bucket encryption, please go to the Google Cloud Storage documentation page on Cloud Storage encryption.
Select Create.
Enable Cloud Resource Manager API to use your models
Until you enable the Cloud Resource Manager API, you will not be able to see your models and glossaries in your plugin.
Go to https://console.cloud.google.com/apis/library/cloudresourcemanager.googleapis.com?q=Resource%20manager and enable Cloud Resource Manager API
Using glossaries
If you want to use your project glossary while translating via Google Cloud Advanced Translation API:
- Upload a glossary file (csv, tmx, tsv) to your Google Storage and compile a new glossary resource, please see the detailed instruction from Google here https://cloud.google.com/translate/docs/glossary
- Add Cloud Translation API Editor role to your project
- If all steps were taken properly, you would see a list of glossaries in the plugin.