Referring to the same concept with the same word across an organisation's documents does not happen by itself; someone has to take these decisions and record them. The terminologist takes on this role. The work is not to translate but to build the language on which the translation will rest.
Definition
The terminologist is the person who builds terminology lists and keeps them up to date. The role is separate from translation. The task is the language infrastructure.
Position of the role
The work runs before the translation and alongside it. It is done not during translation but as preparation for it. The position is different.
Extracting terms
Candidate terms are extracted from the client's existing texts and gathered in a pool. The operation is supported by a frequency scan. This is how the first list comes about.
Filtering candidates
Most of the candidates that the tools extract are not real terms but merely words that occur frequently. The filtering is done by a human, and this is where the real effort lies. The list gets shorter at this step.
Researching equivalents
For each term the possible equivalents in the target language are researched. Sector publications and the client's own texts are scanned. The options are gathered together with their reasoning.
Taking the decision
From among the options gathered, the preferred one is determined and put on record. The reasoning behind the decision is written down too, because the same question will be asked again in future. The record shortens the debate.
Client approval
The critical terms that make up the visible face of the organisation are submitted for client approval. A term that has been approved does not become a matter of dispute later. The step is not skipped.
Writing definitions
A short definition that explains the concept is added to every term entry. The definition prevents similar terms from being used in place of one another. The field is not left empty.
The context example
The use of the term within a real sentence is added to the entry as an example. The example makes the abstract equivalent concrete and shows the correct usage. This is how the entry is enriched.
Recording forbidden equivalents
Equivalents that must not be used are flagged. The scan catches them. The record is critically important.
Distributing the list
The list reaches the whole team at the same time. Different versions produce inconsistency. Distribution is central.
Announcing updates
Changes are announced openly. A silent update creates confusion. Communication is established.
Working with the subject-matter expert
Technical decisions are taken in consultation with the subject-matter expert. The terminologist does not decide alone. Cooperation is established.
Tool knowledge
The use of term database software is known. The field structure is designed. The competence has a technical dimension.
Linking it to the memory
The termbase works together with the translation memory. The integration is set up. The translator sees the two together.
The deviation report
Places where the list has not been followed are scanned and reported. The report is produced regularly. The trend is tracked.
The maintenance burden
If the list is left unmaintained, it quickly loses its value. Regular maintenance is planned. Continuity is ensured.
The role in small teams
In small teams a senior translator takes on this role. What matters is the function of the role, not its name. The practice is flexible.
Its corporate value
A well-maintained termbase makes the organisation's language independent of individuals, and consistency is preserved even if the team changes. This asset gains value over time. The investment is lasting.
What it is confused with
The terminologist is often taken to be a person who compiles dictionaries. Yet a dictionary records the general language, a termbase the approved decisions of a particular organisation; the scope and the binding force of the two are different.