This chapter describes the different basic data that is used in the IFS Translation Manager. All term basic data are managed in the same Manage Term Basic Data feature. This feature is accessed from the Basic Data Administration navigator entry, see figure 1 below.
Figure 1. Use the navigator entry Basic Data Administration to manage term basic data.
All terms has a registered owner. The term owner states the ownership and gives an answer to the question; Who is responsible for a specific term? The term owner concepts also reflects how the term xml files are stored into the version handling system. Term owners are managed in the Manage Term Basic Data feature, see figure 1 below.
Figure 1. Term Owners are presented in a hierarchy with one top node (IFSAPP).
The following four attributes can or needs to be registered for a particular term owner record;
New term owners are registered by right clicking on a owner node in the Owner Hierarchy column and using the Insert menu option. The Parent Owner ID will be defaulted to the specific owner you selected in the hierarchy tree. Enter the owner id and description and save, if needed enter a responsible person.
To remove a owner, select the owner, right click and select the Delete menu option.
Owner leaf nodes can be connected to a set of components, this connection is used when exploring term bindings and text translations. A single component can only be connected to one owner. To connect a component, select the owner in the grid and click the Add Component link. To remove an existing owner-component connection, select the component that should be removed, right click and use the Remove Component menu item. This removes the connection, not the component itself.
If you select a parent owner the Add Component link is disabled. Selecting a parent owner displays all components that are connected to any child owner in a read only mode.
As you may have read in the about description so is a term defined as one or several words with a precise meaning, in a specific domain. There can exists several terms, with the same name but in different domains, that has different meanings. The domain is an essential part to understand what the term actually represents. For example the term "Fly" in a zoological domain can represents something entirely different than the term "Fly" in an aerodynamic domain.
Term domains in IFS/Applications can be managed in the Manage Term Basic Data feature, see figure below. One domain can be set to default, this default domain will then be suggested to the user when a new term is registered.
Figure 3. Term domains in IFS/Applications.
Term domains can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
Lifecycles that can be found in the list on the Lifecycle tab in the Manage Term Basic Data feature is used primarily on term usage definitions. A usage definition needs to be reviewed, both regarding content and linguistics before it can be translated. Lifecycles are the means to follow up the authoring and review progress of a particular usage definition.
The pre-defined lifecycle chain contains seven different steps, ranging from Draft to Approved for Translation, see figure below. The ordinal determines in which order these activities should be performed, e.g. content review comes prior the linguistic review.
Figure 4. The list of lifecycle stages sorted by ordinal.
The last lifecycle stage is indicated as a Release Stage. This means that when the usage definition is set to this stage so will it automatically be Released. Only one lifecycle stage can be indicated as a release stage. The first lifecycle, the one with the lowest ordinal number, is automatically defaulted to newly created usage definitions.
The Clean RTF indicates that the basic definition will be cleaned when a usage is set to that lifecycle stage. The cleaning is done by removing any font, color, highlighting and paragraph spacing in the basic definition. A history log entry will be registered so you can see the text before and after the cleaning was performed.
Lifecycle stages can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
The stop list that can be found on the Lifecycle tab in the Manage Term Basic Data feature is used for preventing certain erroneous term names. When a new term is saved so is the term name validated against the list of Stopped Term Names. If the specified term name appears in the stop list, a message is displayed and the term cannot be saved.
Figure 5. An example of the message that is displayed if the term name is stopped.
Figure 6. Examples of stopped term names.
There are currently three different reasons for why a term name can be stopped;
The Stop Reason and the Suggested Name are used when alerting the user about the stopped term name. You can change stop reason by selecting a value in the drop down list, see figure below.
Figure 7. The list of stop reasons.
The suggested name should provide information to the user how the term name should be formalized. Stopped term names can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
Identifiers that can be used on term usage definitions are managed in the Identifier list in the Manage Term Basic Data feature.
Figure 8. Examples of usage identifiers.
Identifier is used to group certain usage definitions together. This can be useful if you need to follow up all definitions for a specific task or project. A Phase Out Date can be given for an identifier. This is a good way to limit the number of active identifiers that can be used. An identifier that has been phased out cannot be used in the application.
The Hide Inactive check box is used to hide inactive identifiers, i.e. identifiers which phase out date is in the past. Identifiers can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
Terms can be alerted with a list of user-defined alerts. These are managed in the Alert list in the Manage Term Basic Data feature.
Figure 9. Examples of term alerts.
An alert consists of an identifier, the actual Alert and a Description. See Alert Terms for further information about how alerts can be used on terms. Alerts can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
It's possible to relate languages with each other in the Manage Term Basic Data feature.
Figure 10. Examples of related languages.
Related Languages are used when translating terms and texts. Here any related translation (based on the related languages setup) is displayed to the translator as an additional support.
Related Languages can be inserted or deleted by right clicking in the list and selecting the Insert or Delete menu item.
During development functionality in export language files and scan translatable code windows is using the "Use For Development" flag to set the default layer when opening the window.
Figure 11. Layer
It is only possible to change the Use For Development, only one layer can be checked.