DICTIONARY MANAGEMENT IN TOTAL ECLIPSE
(Contributed by Gary Stephen, Jr., of Advantage Software for SSG, 11/27/02)
This document will explain how to get the maximum use out of the Job and Edit dictionaries in Total Eclipse, and show you how to handle dictionary management such that the reporterís dictionary will benefit from the scopistís conflict selections.
Total Eclipse allows you to have multiple users. In practice, you would create a different user for each of your clients. To create a new user, click the Create New User button on the User tab of User Settings, and follow the prompts. Having separate users for each of your clients allows you to store each clientís files in a separate folder, and also allows you to have a separate Edit Dictionary for each client.
THE EDIT DICTIONARY
The Edit Dictionary exists on the Edit Station, and is a repository of sorts for your globals. Any ďMainĒ globals performed by the scopist will go into this dictionary. Every so often, the scopist can send this dictionary to the reporter, and the reporter can integrate these entries into their main dictionary if they wish.
By default the Edit Dictionary will have the same name as the Eclipse user you created it under, e.g. FRED.DIX, SALLY.DIX, etc.
To integrate the entire Edit dictionary into their main dictionary, the reporter needs to do the following:
1. Open the Main dictionary.
To integrate only selected items from the Edit dictionary into their main dictionary, the reporter can delete the unwanted entries from the Edit dictionary, then follow the above steps.
NOTE: There are other ways to transfer entries from one dictionary to another. However, only Alt-R will allow the reporter to benefit from the scopistís conflict data.
NOTE ALSO: If the reporter is concerned about overwriting an existing
entry, they can turn on the Create Conflicts option on the Edit tab of
User Settings. With this item on, they will be prompted before any entry
The Job Dictionary serves two purposes.
First of all, it is used to store job-specific dictionary entries, entries you donít want cluttering up the main dictionary (participantsí names, case-specific terminology, etc.) Scopists should follow this practice; the reporter will have a cleaner main dictionary if the scopist keeps job-specific items in the job dictionary.
Second, it is used to convey the conflict resolution information from the reporter to the scopist.
HOW THE REPORTER CAN BENEFIT FROM THE SCOPISTíS CONFLICT SELECTIONS
Total Eclipse has an artificial intelligence feature whereby the program will ďlearnĒ from the conflict choices made during editing, and use this information to automatically resolve conflicts. In a reporter-scopist situation, the reporter needs to follow a series of steps to benefit from the scopistís choices:
1. When translating the job, Make Edit Station Info needs to be checked on the Translate Notes window.
2. When giving the job to the scopist for editing, the job dictionary must also be given. By default the job dictionary will have the same name as the job. If you are using a Master Job dictionary, or if you have selected a different job dictionary, that is the dictionary that will be used.
3. When the scopist selects the conflicts, the conflict selection information will go into the Edit dictionary. This is indicated with the text (AI:1) which will appear after any conflict for which the scopist has made a selection.
4. When the reporter gets the Edit Dictionary back, they need only transfer that entry into their main dictionary using Alt-R.
And thatís it. The job dictionary is used to convey conflict information
from the reporter to the scopist; the Edit dictionary is used to convey
it back. Furthermore, the job dictionary is used by both reporter and scopist
for job-specific dictionary entries.