Scanning for Duplicate Proposals for the Same
Source Text
Use
You can scan the proposal pool to find cases where two identical proposals exist for the same source text. For example, where a system standard and application standard are exactly the same translation. In this case, you can delete the application standard without causing any modified lines, and reduce the size of the proposal pool at the same time, which improves the performance of the translation tools.
Prerequisites
See the Prerequisites section in DEMS Objects for Quality Assurance.
Procedure
1. Call up transaction LXE_MASTER.
2. Choose Environment → DEMS Objects.
3. Choose the Duplicates pushbutton next to Selection via Proposal Pool.
4. Define the criteria for your scan as follows:
Source language |
In the S_LANG field, enter the required source language for the scan. |
Target language |
In the T_LANG field, enter the target language for the scan. |
Name of DEMS objects |
Enter a text string in the NAME field that will help you recognize the DEMS objects when you call them up in transaction SE63. |
Description of DEMS objects |
You can enter a description of up to 40 characters in the DESCRIPT field to document how you created the DEMS objects, for example. |
Minimum number of duplicate proposals |
Enter the minimum number of duplicate proposals in the MIN_FREQ field. For example, if you only want the DEMS objects contain source texts that have two or more duplicate proposals for this target language, enter 2 in this field. |
Maximum number of source texts |
In the NUMBER field, you can specify a limit to how many source texts are contained in the DEMS objects produced by the scan. If you want the scan to find all instances that match your selection criteria, set this number to a suitably high value. |
Domain to be scanned |
You can restrict the scan to search only in the application standards and exceptions created in a specific domain by entering the 2-character ID for the domain in which you want to scan (e.g. LO for Logistics General) in the DOMANAM field. To search in all domains of the proposal pool, make sure the fields DOMATYP and DOMANAM both contain the value *. |
Split DEMS objects according to domain |
If the worklist contains objects from collections belonging to different domains, we recommend that you create your top texts according to domain. If you leave the field NO_APPL blank, the system creates domain-specific top texts. For example, the system creates separate top text objects for the source texts in objects from Basis (domain BC) that match your selection criteria, and so on. This allows translators to create application standards for the domain in question; in cases where it is not possible to create a system standard for the source text, but an application standard for domain BC is perfectly possible. |
Schedule top text job in the background |
Ensure the BATCH field contains the value X so that the job to create the top texts runs in the background. |
5. Choose Execute (F8) and schedule the job to run in the background.
Result
The system scans the proposal pool and creates DEMS objects in accordance with your selection criteria. The DEMS objects contain source texts in the requested source language for which duplicate proposals exist in the requested target language.
You can now trigger processing of these DEMS objects. For more information, see Processing DEMS Objects for Quality Assurance.