The Terminology Manager comes installed with a default set of custom fields based on the TBX-Basic Data Category Specification originally published by the Localization Industry Standards Association (LISA). This specification recommends a subset of the most commonly used fields defined in the ISO 12620 standard. The specification is based on studies of what data the localization industry actually needs from managing terminology, but is also suited for any industry that requires a lightweight approach to terminology. For more information, download the TBX info page.
The following table lists the default custom fields with descriptions primarily taken from the TBX-Basic specification and the ISO 12620 standard.
Field Name |
Context |
Data Type |
HTML |
ISO 12620 |
A.5.3 |
Description |
A sentence that contains the term. TipThis field is the equivalent of the OLIF element |
Field Name |
Cross reference |
Data Type |
Text |
ISO 12620 |
A.10.18 |
Description |
A pointer field or record used in a data collection to direct the user to another related location, for example, another record. |
Field Name |
Customer |
Data Type |
Text |
ISO 12620 |
A.10.3.1 |
Description |
A field used to identify terms that are required for specific customers, in databases that contain terminology for multiple customers |
Field Name |
Definition |
Data Type |
Text |
ISO 12620 |
A.5.1 |
Description |
A statement that describes a concept and permits its differentiation from other concepts within a system of concepts. TipThis field is the equivalent of the OLIF element |
Field Name |
External cross-reference |
Data Type |
Text |
ISO 12620 |
A.10.18 |
Description |
Pointer to external reference information or explanatory text about the term or concept, such as a Wikipedia article. |
Field Name |
Geographical usage |
Data Type |
Text |
ISO 12620 |
A.2.3.2 |
Description |
Term usage reflecting regional differences. |
Field Name |
Image |
Data Type |
Image |
ISO 12620 |
A.5.5.1 |
Description |
Reference (URI or URL) to binary content. |
Field Name |
Note |
Data Type |
Text |
ISO 12620 |
A.8 |
Description |
Supplemental information pertaining to any other element in the data collection, regardless whether it’s a term, term-related, descriptive, or administrative. TipThis field is the equivalent of the OLIF element |
Field Name |
Project |
Data Type |
Text |
ISO 12620 |
A.10.3.3 |
Description |
A field used to identify terms that are required for specific jobs or projects, in databases that contain terms originating from or required for multiple jobs or projects. |
Field Name |
Source of definition |
Data Type |
Text |
ISO 12620 |
A.10.19 |
Description |
Source of the definition. It’s a recognized best practice to document the source of the definition whenever a definition is provided. |
Field Name |
Source of term |
Data Type |
Text |
ISO 12620 |
A.10.19 |
Description |
Source of term. |
Field Name |
Assigned To (ISO: 'Responsibility') |
Data Type |
Text |
ISO 12620 |
A.10.2.2 |
Description |
An identifier assigned to the individual associated with a terminology management transaction. |
Field Name |
Process Status |
Data Type |
List |
ISO 12620 |
A.2.9.4 |
Description |
The status of a term with respect to its advancement within the terminology management process. |
Field Name |
Part of speech |
Data Type |
List |
ISO 12620 |
A.2.2.1 |
Description |
A category assigned to a word based on its grammatical and semantic properties. TipThis field is the equivalent of the OLIF element |
Field Name |
Term type |
Data Type |
List |
ISO 12620 |
A.2.1 |
Description |
A flexible category used to define the form of term entered. Possible values could be:
|
Field Name |
Gender |
Data Type |
List |
ISO 12620 |
A.2.2.2 |
Description |
A category for specifying grammatical gender. |
Field Name |
Subject Field |
Data Type |
List |
ISO 12620 |
A.4 |
Description |
An area of human knowledge to which a terminological record is assigned. TipThis field is the equivalent of the OLIF element |