On October 24-27, I had the honor of presenting at the 53rd American Translators Association Annual Conference in San Diego, California. In my presentation about Terminology Management, I talked about 6 case studies of how Terminology Management can make or break a project. If you’ve read my blog before, you know that I’m passionate about Terminology Management and have talked about how it affects both translators and interpreters alike here.
I presented 6 case studies of the good, the bad and the ugly of terminology management: 3 translation projects, 2 interpretation projects and 1 voice-over project. My original idea for this presentation came as a final project presentation I did in order to obtain the ECQA Terminology Manager – Basic Certification, from TermNet.
If Terminology Management is to be seen from a Project Management point of view, it is an item in the project management flow and budget and, theoretically, should have client and translation agency’s buy-in. In other words, both the client and the translation agency have to understand and support the fact that Terminology Management can save cents and sanity.
For this very reason, terminology database design should make sense to stakeholders, with relevant fields, usable fields, number of fields. After all, a database that translators find hard to use and to add terms to will not work, as terminology database access should be sustainable, scalable and allow for seamless integration with linguist’s CAT tools.