| Term | Explanation |
|---|---|
| Business Unit (BU) | A department or team. For Cochrane, we use the BU to differentiate the projects of different translation teams. We have one Business Unit per language. |
| Client | We do not use this for Cochrane. This can be used if a translation company works on projects for different clients. |
| Cost Center | We do not use this for Cochrane. This can be used if projects are paid via different budgets. |
| Domain | Projects and users can be categorised with a domain, e.g. medicine, or law. We do not use this for Cochrane. |
| Due | A project and each workflow step of a job can have a due date by when it should be completed if you indicate one. |
| Job | A job usually corresponds to one file that needs to be translated. Each project contains one or more jobs. |
| Linguist | The user role for translators and editors. |
| Owner | The owner of a project can receive project notifications, for example, when a linguist completes a job. The owner of a project is usually one of the translation project managers for each language. |
| Project Manager | The user role for project managers of a translation team. |
| Project | A project can include one or more jobs that need to be translated into one or more languages. In Cochrane, we use a separate project for each Review and language. |
| Project owner | The project owner can receive project notifications, for example, when a linguist completes a job. The owner of a project is usually one of the translation project managers for each language. |
| Segment | Phrase splits text for translation into smaller segments. A segment can be a single sentence, phrase or heading of a text. This allows for storing translations efficiently in the translation memory and finding matches from the translation memory. |
| Source | The original language of a project or job that should be translated. For Cochrane, that is usually English. |
| Subdomain | Projects and users can be categorised with a subdomain, e.g. internal medicine, or oral health. We do not use this information for Cochrane at the moment. |
| Status | A project and each workflow step of a job can have different statuses: New, Emailed, Accepted, Declined, Completed, Delivered, or Cancelled. The status can be edited manually by project managers, and in some cases by Linguists, when they work on a job. |
| Target Languages | The language(s) into which a project or job will be translated. |
| Term Base (TB) | The glossary. You can store English terms and their translations in the TB, which often appear in Cochrane content. This helps make your translations consistent. The terms that you have stored in the TB, will be highlighted to translators and editors when they work on a text that includes the terms. |
| Translation Memory (TM) | All translations that you complete on Phrase will be stored in a TM as bilingual sentences. The sentences that are stored in the TM, will be suggested to translators and editors when they work on a text that includes the same or similar sentences to those stored in the TM. This can make translation quicker and more consistent. |
Overview
Content Tools
Apps