Validation for TD terms and entries

In WorldServer, you can use the Workflow Editor to create validation workflows for the terms and the entries in a term database (TD). Validating terms and entries involves deciding on an appropriate action for every proposed change or addition.

Appropriate actions might include the following:
  • Editing the proposal before accepting it.
  • Approving the proposal as it is.
  • Rejecting the proposal.
Rejecting the proposal can have one of two consequences, depending on whether you are rejecting a change or a new term:
  • If you reject a change, the proposal is deleted. WorldServer does not keep a record of rejected change proposals.
  • If you reject a new term, it receives the Rejected status. WorldServer will remember it as a rejected term and will prevent future proposals of the same term.
To carry out these actions in WorldServer, go to Tools > Term Databases > Term Database: <name> and either search for the appropriate terms or entries or create a validation project. You can create validation projects in two ways:
  • By selecting Validate TD. In this case, WorldServer creates a project and includes in it all the terms or entries with the Proposed status.
  • By selecting Create Project from Result Set after having searched for terms with proposed changes. In this case, WorldServer creates a project and includes in it all the terms or entries from the current result set.

When you create a term validation project, the terms that require approval are sent through your validation workflow, which creates a project group with a project for each language and a task for each term. When a term that requires approval is approved during the process, its status becomes Approved.

When you create an entry validation project, the entries that require approval are sent through your validation workflow, which creates a project with a task for each entry. Each entry can contain multiple terms.

A simple validation workflow might be as follows:A screen shot that shows a simple validation workflow, with the asset-based workflow type being highlighted.

Make sure that the user type of the users who will perform the Review step has the Can modify TD and Can modify term statuses permissions. When an assigned user with these permissions selects a task in the task list and selects Edit, that user can approve the term (Activate > As Approved or Activate > As Preferred), reject it, or deactivate it as deprecated.