The TAUS Knowledge Base. Communicating Translation Automation. A case study

1. Terminology management
The TAUS knowledge base: Communicating
translation automation

2. Terminology management: Application scenario
 July 2014
 Development of a knowledge base on translation automation for all TAUS
members
 Knowledge base
 A database used for knowledge sharing and management
(Source: Techopedia, http://www.techopedia.com/definition/2511/knowledge-
base-klog)
 Translation automation
 Technologies used to automate the various translation processes
(Source: Jaap van der Meer, CEO, TAUS)
The beginning…

3. Terminology management: Application scenario
 Terminology as a tool for knowledge transfer
 The knowledge base, a community forum, various reports and articles
 Every new concept needs to be documented and entered in the knowledge base
 Terminology also plays a role in the terminological search within the corpora that form the language data
repository
 Strength
 Awareness and attention for terminology
 Weakness
 No systematic approach to terminology
 Terminology is not the organization’s core business
 Opportunity
 A concept-oriented terminological approach was needed
 Threat
 No specific budget  Limited resources available
Terminology within TAUS

4. Terminology management: Application scenario
 Customers
 Freelancer technology consultants, language service providers, translation
technology providers
 Subject matter
 Translation automation
 Existing terminologies
 Reports, articles, case studies, use cases, and a small glossary of some 50
words
 All information and terminology had already been previously verified over the years
 Ongoing undercover project
Analysis

5. Terminology management: Application scenario
 Wikified knowledge base
 A combination of the Wikipedia structure with Termwiki (cfr. Uwe Mügge) for definitions and technical information
 4 main data categories
 Translate
 Customization, Metrics, MT Basics, Training
 MT Basics
 Moses
 Evaluate
 Evaluation type, Metrics, Tools
 Post-Edit (The process of improving a machine-generated translation with a minimum of manual labour. Source:
TAUS report, 2010)
 Data
 Entries
 Definition, See also, Reference links, External links
The platform

6. Terminology management: Application scenario
 Wiki
 Well known, free, structured but flexible
 Collaborative Commons
 Copyright
 Data collection
 Small glossary of English terms with a short definition
 A rather large corpus of documents to process (reports, evaluation projects, use cases, case studies, notes from webinars, etc.)
 Terminology standardization
 A descriptive approach for knowledge transfer
 Terminology guide
 None available – to be developed
 Style guide
 None available – to be developed
 Terminology tool
 None (Manual term extraction)
 Backing and support
 TAUS IT staff configured, run and manage the wiki technical platform
Rationale & Technicalities

7. Terminology management: Application scenario

8. Terminology management: Application scenario

9. Terminology management: Application scenario

10. Terminology management: Application scenario

12. Terminology management: Application scenario
 Technicalities
 Improve the wiki editor
 New options (Save as PDF, Make a book)
 Copyright
 Now Collaborative Commons, maybe Creative Commons
 Terminology guide
 Style guide
 Terminology extraction
 Selection of terminology extraction tool
 Communicate the hidden benefits of the knowledge base
 Hidden ROI
Developments in the pipeline

13. Terminology management: Application scenario