Defining Release States and User Groups for Localization

Before creating localizations, give consideration to the release states and user groups you will need. By creating the release states in your Source library, they are automatically included in each Target Library. You can then use the release states to manage your workflow and effectively create a handover of an object from one group to another.

We suggest the following release states as a guideline:

Draft (Source)
Review (Source)
Released (Source)
Sent for Translation
Translation Review
Released (Translated)

Of course, these are only examples and you can create your own customized release states to show where, in the localization cycle, a particular component is. For more information on setting up release states, refer to the Using Author-it Administrator Guide.

For example, you may use the following workflow:

Role	Responsibility
Authors	Create content in Draft (Source), when complete set to Review (Source).
Reviewers	Review objects in Review (Source), if accepted, set to Released (Source), if rejected return to Draft (Source) with comments in an annotation style.
Localization Coordinator	Receive objects as Released (Source), export to XML and set state to Sent for Translation
Localization Coordinator	Receive translated XML, import and change objects to Translation Review.
Localization Reviewers	Review translated objects in Translation Review state and, if accepted, set state to Released (Translated). If rejected (and this is the important part) revert the object to the English version and set the state back to Released (Source).

When creating release states there are two color attributes to define: an object color and a review color. When a review color is defined, the objects in that release state are highlighted with the review color in the published Word output as a visible indication that they need reviewing.

Defining Release States and User Groups for Localization

Role

Responsibility

See Also