Proposal Pool Administration: Technical Worklists 

Purpose

You can create a technical worklist in Proposal Pool Administration to generate a list of entries in the proposal pool that you can then edit for cleanup purposes.

You can create worklists for the following Purposes:

An ALL worklist provides you with a general list of entries in the proposal pool, regardless of whether they have application standards, exceptions, or length variants defined for them. You can, however, restrict the scope of an ALL worklist so that it only contains proposals created by a specific translator, or proposals created after a specific date, for example. For more information, see Scheduling an ALL Worklist.

An APPL worklist provides you with a list of entries in the proposal pool which have application standards defined for them. You can define this worklist to cover either one individual application node in the proposal pool, or to cover all applications in the proposal pool. For more information, see Scheduling an APPL Worklist.

An EXCE worklist contains a list of entries in the proposal pool which have exceptions defined for them. You can define this worklist to cover either one individual application node in the proposal pool, or to cover all applications in the proposal pool. For more information, see Scheduling an EXCE Worklist.

An OUSE worklist provides you with proposals that are frequently used. You can define a OUSE worklist to contain all proposals that are used more than 20 times in the system, for example. For more information, see Scheduling an OUSE Worklist.

A VARI worklist provides you with those instances in the proposal pool where many different translations exist for one source text. You can define a VARI worklist to contain all entries in the proposal pool where over 10 different proposals have been created for one single source text, for example. For more information, see Scheduling a VARI Worklist.

An APEX worklist combines the APPL and EXCE worklists to provide you with a list of entries in the proposal pool which have either application standards or exceptions defined for them, or both. You can define this worklist to cover either one individual application node in the proposal pool, or to cover all applications in the proposal pool. For more information, see Scheduling an APEX Worklist.

You can use a MARK worklist to provide you with a list of proposals (either from one application or from all applications) that are either flagged for automatic distribution or that are locked. For more information, see Scheduling a MARK Worklist.

See also:

Flagging Texts for Automatic Distribution

A LVAR worklist contains all entries in the proposal pool for which a large number of length variants have been created. You can create a LVAR worklist to contain all entries in the proposal pool for which more than 5 length variants have been created, for example. For more information, see Scheduling a LVAR Worklist.

An IDEN worklist provides you with occurrences in the proposal pool where source text and target text are identical. For more information, see Scheduling an IDEN Worklist

Prerequisites

To create and schedule a worklist in Proposal Pool Administration, you need to have Advanced translator status (value 3) for proposal pool maintenance assigned to you in your translator profile..

Process Flow

  1. For each of the above purposes, you can also define the following, additional criteria to further restrict the scope of your worklist:

These criteria vary depending on the Purpose of your worklist (APPL, EXCE, OUSE, etc.)
  1. After defining the selection criteria and options for your worklist, you can then schedule it to run in the background.
  1. As soon as your worklist run is completed, your worklist is given status Active.

Result

As soon as your worklist has active status, you can begin editing the entries contained in the worklist (in the same way you edit a list of entries in STMP) by choosing Edit WL (STMP) under WL Administration.

See also:

Worklist Administration

Editing a Proposal Pool Worklist