A project is the central elements of Memsource Cloud where its main components (translation jobs, translation memories and term bases) are combined together.
For instance, to translate a file through Memsource Cloud, a project needs to first be created, only then the file for translation can be added.
Creating a Project
When creating or editing a project, the following fields are available:
- Project Template (on Create page only)
- Owner (on Edit page only)
- Subdomain (displayed only if at least one subdomain record exists)
- Cost Centers (displayed only if at least one Cost Centers record exists)
- Business Unit
- Source language
- Target languages (one or more)
- Completed (changes by linguist users are blocked on the server)
Memsource Cloud currently supports over 300 languages.
Select one of the available machine translation engines or set this option to Disabled for your project.
To add more machine translation engines, go to Setup - Machine Translation (only available to administrator users). Consult the Machine Translation section, if needed.
Set the default analysis for your project. This setting is connected to the Job Analysis window with 2-way interaction. Any changes made in Job Analysis settings will be saved in Project settings and vice versa. See Analysis for more details.
Set default Pre-translation for your project. This setting is connected to the Job Pre-translation window with 2-way interaction. Any changes made in Job Pre-translation settings will be saved in Project settings and vice versa. See Pre-translate for more details.
Project Status Automation
Project Status Automation rules enable users to configure when a project‘s status should be automatically changed. Project Status Automation rules can be saved in a Project Template and therefore used together with Automation Widget or Automated Project Creation to achieve a completely automated process without Project Manager’s involvement.
All options are deselected by default and can be modified on account level in Setup, and on project level in Project Settings. The options are as follows:
- Set project to Assigned once all jobs are Emailed
- Set project to Assigned once all jobs are Accepted
- Set project to Completed once all jobs are Completed
- Set project to Completed once all jobs are Delivered
- Set project to Cancelled once all jobs are Cancelled
- Set project to Completed once project is Completed by Vendor
Select what checks should be performed when the quality assurance is launched for any of the project's translation jobs. See the Quality Assurance article for more details.
Access & Security
- Email notifications
- Notify job owner when job status is changed
- Linguists may download their translation jobs as TMX
- User metadata displayed to linguists in Memsource Editor
- Web Editor enabled for linguists
- Use vendors (only available to users that can act as buyers)
- Linguists may start a workflow step only if the preceding step has been completed
- Linguists may edit locked segments
- Linguists may edit source
- Linguists may turn on/off auto-propagation of repetitions
- Spellcheck words in ALL CAPS
- Spellcheck words with first capital letter if identical term is used in the source
File Renaming in Project
File renaming can be set in general Setup (effecting newly created projects) or for individual projects.
Please see chapter File Renaming for details
- Net Rate Scheme
- Price list
The workflow feature is only available to users of the Team and Ultimate editions. Workflow makes it possible to maintain multiple versions of a translation job in a project. For instance, a typical workflow could be translation -> editing -> proofreading. These are called workflow steps and they can be customized in the Workflow Steps section of the Setup. Please see detailed explanation in our Workflow article.
To start using workflow in an existing project, click on the Edit button at the top right of a project page to edit the project settings. Then click on Workflow at the bottom of the Settings section and select the workflow steps you want to activate for the project. For new projects, the workflow can be activated immediately during project creation.
The maximum limit is 15 workflow steps in a project.
The project filter is activated by clicking on the filter icon at the top right of a project list, selecting desired items and clicking on the Magnifying glass icon. Projects can be filtered by:
- Created date
- Due date
- Source language
- Target language
- Purchase Order #
Save a Project Filter
Once projects have been filtered, the filter can be saved through the Save filter as submenu.
Project Column Customization
Project Dashboard provides statistics for a specific project divided into two sections:
- Overall progress - overview of job statuses and issues across all workflow steps
- Individual progress - overview of job statuses and issues in individual workflow steps and language combinations.
Each of these sections contains color-coded status bars that reflect the progress of the project in real time based on the number of characters. You can hover over the bar to display a tooltip with the more detailed breakdown for the given section. The following color coding has been used for the Project Dashboard:
- Green - Progress
- Yellow - Issue (Warning)
- Red - Issue (Critical)
- Gray - All other information
The Project Dashboard also tracks the job creation date and the due date as well as the status of individual jobs. If a warning is present in the project, a box will appear in the respective section of Individual progress. Click on the box to receive a breakdown of the issues. Click on the warning itself to filter jobs based on the content of the warning (e.g. overdue jobs) The following warnings are displayed in the Project Dashboard:
- Issues for accepted jobs
- Due in 24 hours (Warning)
- Overdue (Critical)
- Issues for not accepted jobs
- Not accepted (Warning) - displayed for the first workflow step 12 hours after the job was created.
- Overdue (Critical)
- Declined (Critical)
The job filter is very useful to filter jobs by:
- File name
- Job Status
- Target language
- Due date
Job details are displayed when a mouse hovers over individual icons:
- Job number displays ID of the downloaded mxliff
- Job's Confirmed percentage displays details about the segments and Quality Assurance.
- File type icon displays the job import settings. Clicking on the "Create a new job" link will show import details and will also allow you to import a new file with exactly the same settings.
- Job's Status shows when and by whom was the job Created, Emailed, Completed etc.
Selecting Translation Memories for Projects
There are two ways of selecting a translation memory for a project:
- Click on the Create New button to create a new TM and select it for your project at the same time.
- Click on the Select button to select an existing TM for your project. Select the Read and Write checkboxes in the new window next to the desired TM and click on the Save button (do not click on the TM name).
The sections below explain the available options when selecting a TM for a project.
Translation Memory Read Mode and Write Mode
One or more TMs can be selected for a project. As many as 10 TMs can be selected in the Read mode. Only two TMs can be selected in the Write mode.
The read and write mode explained:
- Write: New translations are saved in the TM with the Write mode (for instance when segments are confirmed in Memsource Editor)
- Read: Memsource will connect to these translation memories to retrieve TM matches
Relevant Translation Memories
This feature makes it easier for project managers to select the right translation memories by offering them Relevant translation memories automatically. Translation memories are offered as relevant during the selection process when the TM and the project share one of these:
Reverse Translation Memory
Memsource Cloud allows for selecting TMs which have a reverse source-target language as opposed to the project's languages. E.g. a TM en->de can be selected for a de->en project.
Reverse TMs can only be selected in the read mode for a project.
Selecting Translation Memories with different locales
Memsource allows for adding TM to a project with the same language but a different locale. For example, project DE - EN_US can have assigned TM DE - EN_GB. Generally, all languages with the same prefix can be added (en, en_gb, en_uk...).
For certain languages, however, the code has a different prefix - for example, Norwegian has the code "no" and Norwegian (Bokmål) has the code "nb-NO” - these two languages cannot be mixed.
Selecting Translation Memories for Projects with Multiple Target Languages
When selecting TMs for projects with multiple target languages, the user can decide whether to select a TM that matches all the project's target languages or whether to select TMs for just specific target languages.
Selecting Translation Memories for Projects with Workflow
When selecting TMs for projects with workflow, the user can decide whether the same translation memories should be selected for all of the project's workflow steps, or whether each workflow step should have its own TM setup.
Setting Penalties for Translation Memories
Any translation memory can be penalized by setting the appropriate penalty for it. The penalty can be set when selecting a TM for a project. After a penalty has been set, TM matches originating from that translation memory will be impacted by the penalty in Memsource analysis, pre-translation, in Memsource Editor, etc. Memsource Editor will display an arrow pointing downwards for all penalized TM matches in the CAT panel.
Selecting Term Bases for Projects
- You can select up to 10 TBs for one project.
- Only one is set as writable.
- In the Editor the TBs are searched and matches are displayed in the same order as they are set in the project.
There are two ways of selecting a term base for a project:
- Click on the Create New button to create a new TB and select it for your project at the same time
- Click on the Select button to select an existing TB for your project. Select the Read and Write check boxes in the new window next to the desired TB and click on the Save button (do not click on the TB name).
The sections below explain the available options when selecting a TB for a project.
Term Base Read and Write Mode
One or more TBs can be selected for a project. Only one TB can be selected in the Write mode. As many as 10 TBs can be selected in the Read mode.
The read and write mode explained:
- Write: When new terms are created in Memsource Editor, they are saved in the TB with the Write mode
- Read: Memsource will connect to these term bases to retrieve terminology matches
Relevant Term Bases
This feature makes it easier for project managers to select the right term bases by offering them Relevant TBs automatically. Term bases are offered as relevant during the selection process when the TB and the project share any of these:
Selecting Term Bases with different locales
Memsource allows for adding TB to a project with the same language but a different locale. For example, project DE - EN_US can have assigned TB DE - EN_GB. Generally, all languages with the same prefix can be added (en, en_gb, en_uk...).
However, for certain languages the code has a different prefix - for example, Norwegian has a code "no" and Norwegian (Bokmål) has code "nb-NO” - these two languages cannot be mixed.
Selecting whether Quality Assurance Is Applied
A term base will be included into the quality assurance check if the checkbox under the QA column is checked.
Selecting Term Bases for Projects with Multiple Target Languages
When selecting TBs for projects with multiple target languages, the user can decide whether to select a TB that matches all the project's target languages or whether to select TBs for just specific target languages.
One or more reference files can be attached to a project.
Reference files do not appear in Memsource Desktop Editor or Web Editor. Linguists users can download the files in the linguist portal.
Project templates make it possible to speed up project creation of repetitive projects and also reduce the risk of human error. Any project can be saved as a template through the Save as a button located on the project detail page. See the Project template article for more details.
Any project can be cloned through the Save as button located in the project detail page. Cloned projects inherit project settings from the original project (e.g. attached Translation memories and Termbases, Workflow, Pre-translation and Machine translation settings, source and target languages, Client, Domain, etc.).