Manage translation integration

• Manual — use this method if there is no integration with external applications. You need to manually export a zip file of the translation job components and then send the zip file yourself to the translation vendor. When the vendor delivers a zip file with the translated content, you must import it back into Inspire.
• GlobalLink Portal — use this method if you want to integrate with GlobalLink Enterprise using a transmission tool built for this purpose. You must configure Inspire to use GlobalLink Portal to submit and retrieve translations from GlobalLink Enterprise. To learn more about GlobalLink Portal, go to GobalLink's site for Modules.

  GlobalLink Portal was formerly known as GlobalLink Transport.

  An advantage to using GlobalLink Portal is that if a vendor finds errors in a file, you can log in and Resend corrected files using GlobalLink Portal. This allows you to correct files and resend them without having to create a new translation project.

• GlobalLink Rest APIs — use this method if you want to integrate with GlobalLink Enterprise using the REST (Representational State Transfer) API. This integration method allows Inspire to communicate with GlobalLink Enterprise using a web service over HTTP.
• SFTP — use this method to securely automate the transfer of a translation job as a ZIP file to and from an ftp site. After you create the translation job, Inspire uploads the job as a ZIP file to a specified site securely by encrypting all data and commands. When the vendor completes the job, Inspire downloads and imports the updated ZIP file for you. Inspire also updates the status of the translation job to Complete.

In Translation Projects.

As an administrator, when you create or update a translation project, you can identify if you need to work with an external application.

• If Inspire communicates with an external application, you can include additional details such as a project code and attributes.
• Each translation project can have only one Integration Method.
• You can give a Translation Project any name. If the integration method is important for a translation coordinator to know, include it in the title.

As a translation coordinator, when you create a translation job, you must select a Translation Project.

• This setting tells Inspire how to package the files that need to be translated, and where to send them.
• Translation Projects can be named anything and the title may not include the integration method. For example, an Translation Project may be named after a vendor or a language set.

In this scenario:

1. You send source files to GlobalLink Enterprise for translation.
2. The translator starts work on the files in GlobalLink Enterprise.
3. The translator finds an error in one of the files that they can't fix.
4. The translator uses GlobalLink Enterprise to send the files back to you. The files without errors have been translated and the files with errors haven't been translated yet.
5. After correcting the files with errors, you can either resend them to GlobalLink Enterprise or create a new translation job.

An advantage to using GlobalLink Portal is that if a vendor finds errors in a file, you can log in and Resend corrected files using GlobalLink Portal. This allows you to correct files and resend them without having to create a new translation project. If you do want to create a new translation project you can do that in Inspire.

• If you're sending them manually, for example in email, then you can correct the files and resend them again manually.
• If you're using GlobalLink Connect API to send the files, you'll need to create a new translation project in Inspire and resend only the corrected files.

If an administrator chooses to Configure an integration project to accept cancellations, the external application is notified that the translation job has been canceled.