Adding Project Types

General Settings

Client managers can associate one or more project types with their clients. Keep in mind the following client requirements when creating or associating project types:

AssociateFor those Clients requiring localization ofAdvantagesDisadvantages
A single project type Projects that use the same settings, such as workgroup, workflow, or source locale.Contains the same source locale, workgroup, workflow, cost model, file type, and linguistic tools.

TransPort users do not need to select a Project Type. TransPort automatically selects the Project Type behind the scenes.

The Project Type does not display for TransPort users.
Multiple project typesProjects that use different workgroups, workflows or source locales. For example, a client may want to:
  • Localize marketing collateral and technical design content from several source locales.
  • Review translations using multiple workgroups or workflows for light and in-depth (in-country) editing.
  • Localize a Web content using different vendors and cost models.
Provides for different types of projects that use different file type configurations or workflows.TransPort users must be able to select the correct project types from a list when creating a project.

To create a project type, click Add in the Management > Business Rule Linkage > Project Types page. You can also access this page when you are creating a client (in the Management > User Setup > Client: New page) by clicking Create New in the Project Types section.

The project type definition page has three tabs: General, Processing, and Linguistic Tools.

SettingDescription
NameAn available column in the Project List page. The name and description should provide enough information so a user can decide if this project type is appropriate for them to use, since this is what they will see when trying to create a new project.
DescriptionAn optional description that can be displayed as a column in the Project Types page.

To view a list of project types, go to Management > Business Rule Linkage > Project Types.

Due DateYou can specify that a due date and time be required. The default is that a due date and time is not required.
Source LocaleThe source language of the project.
Restrict Target LocalesSelect this check box if you want the projects created with this project type to be restricted to a number of target locales.
Target LocalesAny locales created in Management > Business Rule Linkage > Locales. This option becomes available only if you select the Restrict Target Locales check box. Use the arrows to add locales to the Selected Target Locales box or to remove them. The locales you add to the Selected Target Locales box will be the ones available to users when they create projects using that project type.
Project AttributesAny custom attributes created in Management > Administration > Customization with the Custom Component Type Attributes selected will be displayed here. You can select which ones you want included in the Project Type. The available project attributes appear in the Available Project Attributes selector box, and you can move them to the Selected Project Attributes box.
AIS PropertiesAny custom AIS properties created in Management > Administration > Customization with the Custom Component Type AIS Properties selected are displayed here. You can select which ones you want included in the Project Type. The available AIS properties appear in the AIS Properties selector box, and you can move them to the Selected AIS Properties box.
In the Processing tab, you select the workgroup, workflow, file type configuration, and cost model for the project type. Since clients may have different sets of content with different translation needs, keep in mind the following:
SettingDescription
WorkgroupIdentifies the users who work on the project, such as translators, reviewers, and client managers. (Required)

Each workflow step specifies the assigned users individually or by workflow role. However, the users must be members of this workgroup to be eligible assignees.

To create or modify a workgroup, go to Management > User Setup > Workgroups.

WorkflowAssociates the project with a workflow, which defines each human and automatic step required to process the translation project. (Required)

Use the Advanced options to override this default workflow for individual locales.

Tip: Click for a quick preview of the workflow.

To create or modify a workflow, go to Management > Workflow > Workflows.

File TypesDetermines how the translatable assets for the project are processed. If you accept the system defaults, WorldServer uses the MIME type associated with the file extensions of each asset to locate an appropriate file type.

Use the Advanced options to override this default file type configuration for individual locales.

To create or modify a file type configuration, go to Management > Linguistic Tool Setup > File Types.

Cost ModelsSpecifies the translation cost per word for a given vendor for each target locale. For example, you can set prices for different types of translations based on the required effort level to complete them.

Use the Advanced options to override this default cost model for individual locales.

To create or modify a cost model or cost model rules, go to Management > Linguistic Tool Setup > Cost Model Setup.

These settings will be used if you select this project type when you create the project or quote.

The Project Type definition page has a Linguistic Tools tab that is similar to the TDs & TMs tab in the Client definition page, with important differences. You can choose to use the TM (or TD) specified in the Client definition page or you can choose a default TM (or TD) to use for all locales. Note that each setting has an Advanced options check box that allows you to override the default for individual locales.
SettingDescription
Translation MemorySelect one of the following:
  • Use client-specific TM. Clients may want to use their TMs to leverage their translation projects. In this case, define the TM in the Client and then select this option.
  • Choose default TM for all locales. You may want to select a global TM as the default for all clients.

Use the Advanced options to override this default TM for individual locales.

Terminology DatabaseSelect one of the following:
  • Use client-specific TD. Clients may want to use their TDs to leverage their translation projects. In this case, define the TD in the Client and then select this option.
  • Choose default TD for all locales. You may want to select a global TD as the default for all clients.

Use the Advanced options to override this default TD for individual locales.

Machine Translation ConfigurationYou can add adapters for third-party machine translation engines to supplement the translation memory leveraging process.

Use the Advanced options to override this default MT configuration for individual locales.

When the leverage process is run, WorldServer uses both TMs and MTs to produce fuzzy matches. In the absence of 100% or better matches, WorldServer uses the score for the best fuzzy match from the TM or MT for scoping purposes.

Quality ModelsA quality model enables you to categorize translation error types and severities to create quantifiable measures and statistics based on the quality of a translation.

You can select a Quality Model, which will be applied to all locales.

Use the Advanced options to override this default quality model for individual locales.

Studio QA Checker ProfileA profile for settings to be used in SDL Trados Studio 2014 and later for verifications. You can select a specific profile, if a customized version has been uploaded into WorldServer. If so, this will be used to automatically configure Studio's verification settings, upon downloading a translation kit.

To use a Studio QA Checker profile in WorldServer, first you need to upload it from the location where SDL Trados Studio exported it. To do so, go to Management > Administration > Customization, and then choose Studio QA Checker Profile from the Custom component type list. Select Add, and then, in the Add Custom Studio QA Checker Profile Component dialog, enter a meaningful name for your QA Checker profile and select Browse. Then, in the File Upload dialog box, browse for the Studio QA Checker profile, select it, and then select Open.

These Project Type settings will take precedence over the Client definition settings at the time of project creation unless you select a client-specific setting.