Termbase Maintenance: Why Does Your Glossary Decay Over Time?

A termbase is at its cleanest on the day it is built; everything after that depends on maintenance. Termbase maintenance is the regular reviewing, cleaning and updating carried out so that the termbase keeps its currency and consistency over time. Without maintenance, even the best-built termbase slowly decays.

Contents

This decay is silent; it does not happen in a day but accumulates over months. As Hann discusses in the appendix to his dictionary, once the relationships between terms become inconsistent the glossary turns unreliable. In this article we look at why a termbase decays, what symptoms it shows, how ageing terms should be handled and how maintenance can be sustained.

Why Is Termbase Maintenance Necessary?

A termbase is not a static document but a living resource. Every new project adds new terms to it; every product change makes some terms obsolete. Left unchecked, this constant flow gradually turns the termbase into a confused and contradictory heap. Maintenance keeps the flow in order.

An unmaintained termbase leads to a loss of trust. If a translator consults it and finds two conflicting equivalents, they cannot tell which to rely on and may give up on the termbase altogether. And a termbase that nobody uses is a dead one. Maintenance keeps the termbase not merely correct but trustworthy, and therefore usable.

That trust, once shaken, is hard to win back. When translators find a termbase wrong a few times, they stop looking at it entirely and revert to their old habits. From that moment on the termbase is effectively out of use, however thoroughly it may be corrected afterwards. Maintenance therefore has to be continuous, so that problems are caught before they grow; protecting trust is easier than repairing it.

Another justification for maintenance is cost. A small piece of decay is cheap to put right early; untangling an accumulated mess later is expensive. Regular maintenance heads off large and costly clean-up projects. A little maintenance often is always more economical than a lot of it rarely.

How Does a Termbase Decay?

The most basic form of decay is inconsistency between records. The example Hann gives in his appendix is instructive: when subordinate terms do not form the same kind of relationship with the superordinate term, the hierarchy becomes confusing. If a concept is attached to a node both as a “part” and as a “type”, the system contradicts itself and misleads the reader.

The second form of decay is the silent process known as obsolescence. An equivalent that was once correct loses its validity as the field moves on, but nobody updates it. The termbase carries on presenting terms that are no longer in use as though they were current. These stale records can steer the translator in the wrong direction.

The third form is uncontrolled growth. Every project adds new terms to the termbase; but if those additions go unchecked, multiple records for the same concept appear, along with orphan terms attached to no subject field at all. Growth is not good in itself; unchecked growth is the most common cause of a termbase decaying.

These three forms of decay usually advance together and feed one another. Uncontrolled growth multiplies duplicates; duplicates give rise to contradictions; and unresolved contradictions erode trust. Past a certain point the termbase becomes so tangled that rebuilding it makes more sense than correcting it. The purpose of maintenance is precisely never to reach that point: to catch small pieces of decay before they grow.

Duplicate and Conflicting Records

The problem maintenance deals with most often is the duplicate record. The same concept may be entered twice, at different times and by different people; this is all but inevitable when synonyms are not merged. When two records propose different preferred terms, consistency collapses at the root.

Type of decay	Symptom	Maintenance action
Duplication	Same concept in two records	Merge the records
Contradiction	Different preferred terms	Decide on a single standard
Obsolescence	Equivalent no longer in use	Update or archive
Orphan term	Record with no subject field	Assign a field or delete

Resolving conflicting records is not simply a matter of deleting one of them; it means deciding which is correct, recording the reasoning and flagging the other appropriately. That calls for a considered decision. Catching duplicates early saves you the cost of keeping one concept alive twice over.

The best way to deal with duplicates is not to clean them up afterwards but to prevent them at the outset. Checking whether a concept already exists in the termbase before a new term is added cuts most duplication off at source. This small check is easier in a concept-oriented structure, because a concept-centred search also brings together the different names for the same concept. Prevention is always cheaper than clean-up.

Regular Review

The backbone of maintenance is regular review. Alongside the small additions made continuously, someone needs to look at the termbase as a whole at set intervals. In such a review, duplicates are screened out, ageing terms are flagged, contradictions are resolved and records missing subject-field information are completed.

How often review takes place is set according to the size of the termbase and the pace of change in the field. A fast-moving technology field needs frequent maintenance; a settled field needs it less often. What matters is that review is tied to a calendar and carried out to a plan rather than “when there is time”. The material in our knowledge centre gives examples of how to set up a maintenance calendar.

Review also draws on how the termbase is used. Why translators skip a particular term, and which equivalent they prefer instead, is valuable data for review. Tracking usage shows how the termbase actually performs and grounds maintenance in reality. The best maintenance learns from use, not from the desk.

The output of a review is not only the records corrected but the lessons learned. A concept that keeps causing confusion shows that its definition is inadequate; a term that is frequently duplicated betrays a weak search arrangement. These lessons make the next review still more targeted. Maintenance thus becomes a self-improving cycle, each round leaving the termbase a little sounder.

Who Does the Maintenance, and How?

Maintenance should be a defined responsibility, not scattered goodwill. Whoever is responsible for term decisions, or the terminologist, takes maintenance on as well. If no one is designated, maintenance becomes nobody’s job and is neglected; and the termbase quietly decays. A clear role is the first condition for maintenance continuing at all.

The work of maintenance can be partly supported by tools. A tool can automatically scan for duplicate records, terms without a subject field or formatting inconsistencies. But it is still a human who decides which record is correct and which is out of date. The tool shows the symptoms; the person responsible makes the diagnosis and applies the treatment.

The way to make maintenance sustainable is to keep it small and frequent. A short check each time a new term is added is easier than one giant clean-up a year. Once maintenance becomes a natural part of the workflow, it stops being a burden. Sustainable maintenance is a habit, not an act of heroism.

Delete a Term or Archive It?

A decision that comes up often during maintenance is whether an ageing term should be deleted. The first instinct is to delete it, but that is usually wrong. A deleted term is no longer recognisable when it turns up in an old document or a source text, and the translator has to research it all over again. Information is lost the moment it is deleted.

The safer course is to archive an ageing term rather than delete it. The term stays in the record but is flagged as “old” or “not in use”, while the current equivalent is clearly brought to the fore. A translator who comes across the term in an old document then both recognises it and sees what to use in its place. An archive shows the future without erasing the past.

This approach also preserves the history of the termbase. When there is a record of why a term changed and when it aged, future decisions can draw on that history. Deletion is appropriate only for records that are genuinely wrong or appear in no document at all. The rule is simple: every term that has been used deserves to leave a trace. Archiving turns maintenance from a process of loss into a process of accumulation.

The Türkiye context

In Türkiye, termbases are often built for a single project and then left to their own devices once the project ends. This is the most common maintenance failure: the termbase is built once and forgotten, then found out of date at the next project. Yet the rapid coining of technical equivalents in Turkish makes regular updating particularly necessary.

Another local factor is that Turkish equivalents shift over time; the equivalent for a new technology settles within a few years and the older candidate terms fall away. Reflecting that shift in the termbase takes regular maintenance. At our office in Ankara Kızılay we run maintenance on the termbases we build as a continuing service, clearing out duplicate records and updating ageing terms. The termbase therefore carries on living with the client after the project has finished. That continuity also removes the considerable waste of rebuilding the termbase for every new project.

What does this mean for you?

If you have a termbase, or plan to build one, that investment will lose its value over time without a maintenance plan. To keep your termbase alive:

1. Name a person or an external partner clearly responsible for maintenance.
2. Set up a regular review calendar; do not leave it to “when there is time”.
3. Run a short duplication and subject-field check on every new term you add.
4. Archive ageing terms and flag the current equivalent instead of deleting them.

We run maintenance on the termbases we build as a continuing service; our translation services cover that maintenance. To have us assess the health of your existing termbase, write to us through the contact page.

Frequently asked questions

What is termbase maintenance?

It is the regular reviewing, cleaning and updating carried out so that a termbase keeps its currency and consistency over time. Without maintenance a termbase slowly decays.

Why does a termbase decay?

As new terms are added, duplicate and conflicting records build up, some terms age and the field itself changes. If that build-up goes unchecked, the termbase grows steadily unreliable and confused.

How often is maintenance needed?

Alongside continuous small additions, a comprehensive review at regular intervals (once a year, for instance) is advisable. The frequency is set according to the size of the termbase and the pace of change in the field.

Who should carry out maintenance?

Whoever is responsible for term decisions, or the terminologist. Maintenance should be a defined responsibility rather than scattered goodwill; otherwise it becomes nobody’s job and is neglected.

References

• Hann, M. (1992). The Key to Technical Translation, Vol. 2. John Benjamins.
• Sager, J. C. (1990). A Practical Course in Terminology Processing. John Benjamins.
• ISO 26162:2012. Design, implementation and maintenance of terminology management systems.