Translation Environment Tools (TEnTs) became popular in the early 1990s as a partial solution for coping with ever-increasing translation demands and the decreasing number of translators available. TEnTs allow the creation of repositories of legacy translations (translation memories) and terminology (integrated termbases) used to identify repetition in new source texts and provide alternate translations, thereby reducing the need to translate the same information twice. While awareness of the important role of terminology in translation and documentation management has been on the rise, little research is available on best practices for building and using integrated termbases. The present research is a first step toward filling this gap and provides a set of guidelines on how best to optimize the design and use of integrated termbases. Based on existing translation technology and terminology management literature, as well as our own experience, we propose that traditional terminology and terminography principles designed for stand-alone termbases should be adapted when an integrated termbase is created in order to take into account its unique characteristics: active term recognition, d one-click insertion of equivalents into the target text and document pretranslation. The proposed modifications to traditional principles cover a wide range of issues, including using record structures with fewer fields, adopting the TBX-Basic’s record structure, classifying records by project or client, creating records based on equivalent pairs rather concepts in cases where synonyms exist, recording non-term units and multiple forms of a unit, and using translated documents as sources. The overarching hypothesis and its associated concrete strategies were evaluated first against a survey of current practices in terminology management within TEnTs and later through a second survey that tested user acceptance of the strategies. The result is a set of guidelines that describe best practices relating to design, content selection and information recording within integrated termbases that will be used for translation purposes. These guidelines will serve as a point of reference for new users of TEnTs, as an academic resource for translation technology educators, as a map of challenges in terminology management within TEnTs that translation software developers seek to resolve and, finally, as a springboard for further research on the optimization of integrated termbases for translation.

Translation Environment Tools (TEnTs) became popular in the early 1990s as a partial solution for coping with ever-increasing translation demands and the decreasing number of translators available. TEnTs allow the creation of repositories of legacy translations (translation memories) and terminology (integrated termbases) used to identify repetition in new source texts and provide alternate translations, thereby reducing the need to translate the same information twice. While awareness of the important role of terminology in translation and documentation management has been on the rise, little research is available on best practices for building and using integrated termbases. The present research is a first step toward filling this gap and provides a set of guidelines on how best to optimize the design and use of integrated termbases. Based on existing translation technology and terminology management literature, as well as our own experience, we propose that traditional terminology and terminography principles designed for stand-alone termbases should be adapted when an integrated termbase is created in order to take into account its unique characteristics: active term recognition, d one-click insertion of equivalents into the target text and document pretranslation. The proposed modifications to traditional principles cover a wide range of issues, including using record structures with fewer fields, adopting the TBX-Basic’s record structure, classifying records by project or client, creating records based on equivalent pairs rather concepts in cases where synonyms exist, recording non-term units and multiple forms of a unit, and using translated documents as sources. The overarching hypothesis and its associated concrete strategies were evaluated first against a survey of current practices in terminology management within TEnTs and later through a second survey that tested user acceptance of the strategies. The result is a set of guidelines that describe best practices relating to design, content selection and information recording within integrated termbases that will be used for translation purposes. These guidelines will serve as a point of reference for new users of TEnTs, as an academic resource for translation technology educators, as a map of challenges in terminology management within TEnTs that translation software developers seek to resolve and, finally, as a springboard for further research on the optimization of integrated termbases for translation.

Translation Environment Tools (TEnTs) became popular in the early 1990s as a partial solution for coping with ever-increasing translation demands and the decreasing number of translators available. TEnTs allow the creation of repositories of legacy translations (translation memories) and terminology (integrated termbases) used to identify repetition in new source texts and provide alternate translations, thereby reducing the need to translate the same information twice. While awareness of the important role of terminology in translation and documentation management has been on the rise, little research is available on best practices for building and using integrated termbases. The present research is a first step toward filling this gap and provides a set of guidelines on how best to optimize the design and use of integrated termbases. Based on existing translation technology and terminology management literature, as well as our own experience, we propose that traditional terminology and terminography principles designed for stand-alone termbases should be adapted when an integrated termbase is created in order to take into account its unique characteristics: active term recognition, d one-click insertion of equivalents into the target text and document pretranslation. The proposed modifications to traditional principles cover a wide range of issues, including using record structures with fewer fields, adopting the TBX-Basic’s record structure, classifying records by project or client, creating records based on equivalent pairs rather concepts in cases where synonyms exist, recording non-term units and multiple forms of a unit, and using translated documents as sources. The overarching hypothesis and its associated concrete strategies were evaluated first against a survey of current practices in terminology management within TEnTs and later through a second survey that tested user acceptance of the strategies. The result is a set of guidelines that describe best practices relating to design, content selection and information recording within integrated termbases that will be used for translation purposes. These guidelines will serve as a point of reference for new users of TEnTs, as an academic resource for translation technology educators, as a map of challenges in terminology management within TEnTs that translation software developers seek to resolve and, finally, as a springboard for further research on the optimization of integrated termbases for translation.