L11: Terminology for Interpreters/Termbases and Terminology Management Systems Overview

Lecture 11 Week 6

Preparation stages in the interpretation booth

Theme-based, linguistic, translation, and interpretation preparation. Terminology work is present throughout all stages.

Glossaries in interpretation

Glossaries are active tools, not finished products. They require updates after interpretation sessions to avoid information loss.

Interpreter term record features

Include hypernyms, synonyms, abbreviations, proper names, client preferences, pronunciation notes, phraseology units, and verb-noun collocations.

Visual format tailoring for term records

Customizable formats—colors, fonts, character sizes, and box sizes. Records should be highly personalized for each interpreter.

Mini-databases for interpreters

Small, specialized databases tailored to a specific client or conference. Avoid large macro-databases.

Key features of interpreter mini-databases

Speed of consultation, intuitive navigation, in-booth updating, flexible structure, and multiple filtering options.

Semasiological approach in termbases

Focuses on meaning and concept orientation, ideal for interpreter-specific termbases.

Terminology Management System (TMS)

Software for managing terms and related data. Also called Terminology Management Tool (TMT).

TMS vs. Translation Management System

Both share the abbreviation TMS. In this course, TMS refers to Terminology Management System.

Integrated TMS

Part of larger suites like CAT tools. Examples

Standalone TMS

Independent from other tools. More generic, repurposable, and often support TBX standard. Examples

TBX standard

Terminology exchange standard. Standalone TMS often support TBX for better interoperability.

Client/server vs. cloud-based TMS

TMS may be client/server applications or cloud-based. Standalone-from-outset tools tend to be more robust.

Concept orientation in termbases

Allows multiple terms per language and multiple languages per entry.

Term autonomy

Each term can have its own full set of fields.

TMF compliance

TMF (ISO 16642) requires three nested levels

Customizable data model

TMS should allow creation of custom fields, picklists, field order, and mandatory/optional settings.

Field assignment flexibility

Fields can be assigned to concept, language, or term level—or multiple levels.

Field types in TMS

Picklist, free text, date, multimedia, relational.

Mandatory fields

Fields like "Part of speech" can be set as required before saving entries.

Nested fields

Fields with subordinate fields, e.g., Definition and Source.

Repeatable fields

Allows multiple instances of a field, like several context sentences.

Field order

Most-used fields should appear at the top to reduce scrolling.

Rename fields

Field labels should be editable at any time.

Graphics and attachments

TMS should support images and document uploads, typically at concept level.

Terminology data categories

TMS should support all categories defined in terminology standards.

Workflow fields

Fields like "Process status" enable automated workflows (e.g., proposed, under review, finalized).

Picklist management

Add, remove, change values, set order and defaults.

Sections in termbases

Large termbases benefit from sub-structures like divisions or sections.

Reusable data model

Once created, a termbase model should be savable and reusable.

File depository

Graphics and attachments should be stored in an accessible repository linked to the termbase.

Identifiers

Each concept and term should have unique IDs for cross-referencing.

Change history

All edits should be tracked and viewable.

Revert capability

TMS should allow reverting to previous states using change history.

Deleted entry records

Deleted entries should be stored and restorable, purgeable when needed.

TMS integration features

APIs and connectors allow integration with other enterprise tools and user environments.

Local installation of remote termbases

TMS should allow offline access by installing termbases locally.

Language flexibility in TMS

No fixed source/target languages. Users can choose SL and TL dynamically.

Script considerations

Japanese (Kanji, Hiragana, Katakana), Punjabi (Gurmukhi, Shahmukhi), Chinese (Simplified, Traditional) require script-aware termbase design.

Chinese script handling

Use a Geographical variant picklist with values for Simplified and Traditional Chinese.