Demonstration (DEMS) Objects

Demonstration (DEMS) objects are virtual short text objects that provide a gateway to the proposal pool, enabling you to create proposals for source texts with a high level of repetition, or clean up proposals created by a specific user, for example.

DEMS objects have two main purposes:

• DEMS objects for productivity improvement

  The DEMS objects created for this purpose are called top texts. They pinpoint the source texts with the best potential for automatic distribution. A top text object offers the source texts that have high levels of repetition in your translation project, sorted according to frequency, with the source text that occurs most frequently for translation appearing first in the first top text object.

  You can call up a top text object in the short text editor and create high quality proposals for the source texts that only require one translation in all contexts. This reduces the manual translation volume as soon as automatic distribution takes place, as long as you have created high quality proposals for source texts with a high level of repetition.

• DEMS objects for quality assurance

  You can generate DEMS objects for quality assurance purposes. For instance, all proposals created by a specific user in March, all domain standards for domain SD, a scan for a specific generic text string in the source text and/or target text if you need to make a terminology change, and so on.

Before you create demonstration objects, you need to do the following:

• If you are creating top texts, ensure that you have a basis for your top texts (either an object list or worklists).

• Define distribution parameters for the target language(s) in question. For more information, see Defining Distribution Parameters.

• Ensure that the users who will process the DEMS objects have sufficient authorization to create proposals with quality status A. For more information, see Translator Profiles.

• Ensure that the users who will process the DEMS objects understand the proposal pool and the dangers of processing top texts incorrectly. If a translator creates an incorrect or unsuitable translation in the proposal pool while processing top texts, or assigns an unsuitable quality status, the proposal could be automatically distributed for all occurrences of the source text in question. It would be time-consuming to correct all occurrences of the incorrect translation after distribution has taken place.

You create demonstration objects in transaction LXE_MASTER by running a background job that scans the source texts for your translation project or the contents of your proposal pool, depending on the type of DEMS object you have selected.

You process DEMS objects in transaction SE63 using the short text editor. You can call them up directly (using the object type shortcut dems), or you can include them in a worklist.

After you have processed top text objects, but before you start manual translation via worklists, you start an evaluation with distribution to distribute the proposals that you have created and reduce the manual translation volume.

You create top texts for your translation project. The first source text in the first object is Save and it occurs 1,000 times for translation in your project. In the proposal pool, you create a translation that suits all possible contexts of the source text Save. You define the translation as a system standard with status A. You then start an evaluation with automatic distribution. This reduces the manual translation volume by 1,000 lines and saves approximately 2 days of manual translation.