Terminology Entry Quality
Checklist
TERMBASE ENTRY MANAGEMENT ISSUES
 |
The entry of any term into the database includes a check for doublettes in the database and resolution of duplicate entries for the same concept. |
|
All data in entry pertain to entry concept |
|
No other entry in database documents the concept treated in this entry |
|
Homographs representing other concepts are treated in other entries |
|
Entry has been assigned to the appropriate subject field |
|
Terms are present for all languages to be treated in the entry |
|
Terms are spelled correctly |
|
Terms are in lowercase unless commonly used in uppercase in texts |
|
Terms are reported in the singular unless always used in context in the plural. |
|
Entailed terms present in database are cross-referenced |
|
Only one term [including multi-word terms] is entered in each term field |
|
Each term (e.g., synonym, abbreviation, full form, TL equivalent) is entered in its own term field |
|
No terms (synonyms, abbreviations, full forms) are embedded in definitions or notes |
|
Articles (le, la, der, die, das, etc.) are not entered in term field (noun terms) |
|
Infinitive particles (to, à, zu, etc.)are not entered in term field (verb terms) |
|
Only one definition is entered in a single definition field |
|
Definitions that do not pertain to the concept in question are entered in a second entry that treats the other concept |
|
Definitions consist of a single predicate-like statement |
|
No note-like material is embedded in definitions |
|
Neither the term nor a synonym (abbreviation or full form) for the term is restated in the definition |
|
No finite verb is included in the definition statement (e.g., the verbs is, refers to, etc.) |
|
Definitions conform to the general principles for writing definitions and to any specific criteria specified for the database in question |
|
Punctuation and capitalization in the definition field conform to styleguides set for the database. |
|
Context field contains a text chunk, which includes the term in question |
|
Context contains situational, definitional, explanatory, or associative information about the term and its concept |
|
Punctuation and capitalization in the context field conform to styleguides set for the database. |
|
Context contains a manageable amount of textual information (neither overly brief or excessively long) |
|
Sources of text-related information are appropriately cited (e.g., definitions, contexts, notes if quoted) |
|
Sources of terms are documented if required by database guidelines |
|
Bibliographic entry with appropriate ID has been created for each printed source |
|
URL for Web-resident information has been documented in accordance with the guidelines for the database |