
If translation priorities change, you may need to remove collections from a translator's assignment.
If a translator leaves the project for good, however, you can simply delete the translator and the collection assignments are automatically deleted. For more information, see Maintaining Translators.
Your translator profile includes authorization object USCO with the value 01 (if you are only deleting collection assignments for translators in your team) or value 02 (if you are deleting collection assignments for translators irrespective of which team they belong to, or whether they belong to a team or not).
To delete the assignment of collections that are not assigned to you, you need authorization object COSE with value 01.
To delete the assignment of collections to translators into more than one target language at once, you must be defined as a coordinator for all languages **** in transaction Translation Environment (LXE_MASTER).
The procedures for deleting collection assignments:
|
Activity |
Procedure |
|---|---|
|
Delete assignments of collections to one translator (all coordinators) |
|
|
Delete assignments of collections to multiple translators (coordinators for one or multiple specific target languages) |
|
|
Delete assignments of collections to multiple translators (coordinators created for all target languages) |
|
|
Delete assignments of deleted collections to translators |
|
The collections you selected are no longer assigned to the translator(s) that you selected. The translator(s) can no longer display statistics for, or call up a worklist for objects belonging to the collections that you deleted from their assignment.
If these collections are still relevant for translation, you need to assign them to other translators.
If these collections are no longer relevant for translation, consider locking them and running an evaluation with the Replace Existing Worklist checkbox selected. This removes the objects belonging to these collections from the statistics and worklists.