1. Integrating and Extending Oracle Content Management
  2. Developing Oracle Content Management Extensions
  3. Develop Translation Connectors for Language Service Providers
  4. Translation Jobs Validation

Translation Jobs Validation

The custom translation connector, which is part of the Oracle Content Management (OCM) Toolkit, can return validation data of a translation job. The validation data indicates whether the documents in the translation job are translatable. The validation data is returned after the connector processes and uploads the documents to the Language Service Provider. The documents can include page content, fields or attributes of content items and digital assets, and native files of digital assets.

Behind the scenes, the custom connector implementation returns the validation data in the form of a JSON object through the notificationData property of the TranslationJobInfo. The same validation data is also presented in the OCM web UI on the translation jobs details page through the GET_CONNECTOR_JOB_INFO server API. Note that the Lingotek translation connector now also has the same feature.

The steps to enable this feature consists of the following:

Create and Start the Custom Translation Connector

  1. Install the OCM toolkit

    Note:

    The custom translation connector toolkit commands.
    cec | grep translation-connector
  2. Create a translation connector

    cec create-translation-connector <name>

  3. Start a translation connector

    cec start-translation-connector <name>

    Note:

    Take note of your IP address of the desktop or Linux box running the toolkit. You will need it for later.

Configure the Custom Translation Connector

  1. Configure the custom translation connector in the OCM web UI.

    Note:

    The translation connector must be started before you can configure the custom translation connector in the OCM web UI.

    To configure a custom translation connector, access the Integration page and select Translation Connectors in the top dropdown menu. Select Create > Custom Connector. Enter the required fields: Name {name of your translation connector}, and Connector service URL http://{IP address:port}/connector/rest/api.

    Click Next to fill in the Additional Fields section as shown below.

    • Bear Token: Bearer token1
    • WorkflowId: machine-workflow-id
    • Additional Date: []

    Once finished, Save and Enable.

  2. Use the custom translation connector by associating it with a repository.

    Access the Content page, select a repository. Click Edit to add the translation connector you’ve created and configured.

Create a Translation Job to See the Validation Data

  1. On the Assets page, select an Asset Type. Under Languages > Translate, create a translation job. Enter a Name. Select a Target Language and Translation Project, which is the connector that’s created in the previous steps. Finish with Create.

  2. Go to the Translation Jobs page and select your translation job, expand the Details section to see the validation data.

    This screen capture shows the page that lists the information about your particular translation job. In the Details section, you're able to see the validation data which indicates whether your documents are translatable.


    The page that lists the information about your particular translation job. In the Details section, you're able to see the validation data which indicates whether your documents are translatable.

    This screen capture below shows the validation data retrieved by the translation connector.


    Translation Jobs Details