Projects can be created to manage translations, track progress, and make estimates for groups of related documents. Typically, a project consists of group documents with similar deadlines, content, and translation settings; however, a project can be used in any manner that makes sense to your organization.
Once you have created a workflow, you can use it to manage translation projects. Simply create a Project, upload your documents, and make assignments.
Create a New Project
To create a new project,
Go to the Projects menu from the sidebar, select Projects, and click New Project.
You must provide your project with a name and a workflow.
- The workflow you choose for the project will determine the workflow for all content manually uploaded using the Add Documents page. Any content uploaded to your project via the API will use this workflow unless a specific workflow is specified.
| Note | ||
|---|---|---|
| ||
Glossaries and TM vaults must be uploaded to Lingotek before they can be added to a project. If no TM vaults, glossaries, or MT engines display on these tabs, check to ensure these resources were added to Lingotek. |
| Live Search | ||||||
|---|---|---|---|---|---|---|
|
Visit the Lingotek Support Center.
| Style |
|---|
#children-section { display:none !important; }
#comments-section { display:none !important; }
#likes-and-labels-container { display:none !important; }
.page-metadata {display:none;} |
Overview of Projects
Inside the Enterprise TMS, Projects have three primary purposes. Projects:
Organize content.
Control how content interacts with the system (and connectors).
Control how users interact with the project and content.
Organizing content
Organizations can create as many projects as necessary. You can create projects for every marketing campaign, for every PO, or your different content sources (e.g., an AEM project and a Marketoproject).
Content interacting with the TMS
Project Settingscontrol how content interacts with the TMS as well as other integrations by determining:
How different file types are imported into the TMS.
The default Workflow to use to translate source content into various targets.
Which project resources are used in the translation process.
Which third-party tools are communicated with, and when.
Users interacting with the project and content
Project Settings also control how users interact with content by:
Determining the permissions project managers and vendor project managers have in the project.
How users upload new documents to the system.
What linguists can and cannot do when working on tasks in the project.
Documents and Targets
Inside the project itself, there are documents (source files that have been uploaded to the TMS for translation) and targets (the locales your source file is being translated into). Inside the Projects menu, project managers and community admins can monitor and take action on documents, targets, and phases on an individual and bulk level. We have provided an enormous set of tools and actions that can be used to make managing content simple in our system.
On this page:
| Table of Contents |
|---|
Projects menu documentation
| Child pages (Children Display) |
|---|
Related Pages
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|