AlsoComprehensive and efficient terminology management and the underlying coordination processes are becoming increasingly important. But what does a “perfect terminology workflow” look like? Which steps are relevant to ensure that terminology is correctly recorded, maintained and – above all – observed? And which tools pave the way to the ideal terminology workflow? In this new blog series, we’re going to take a closer look at the steps of terminology management in different systems. Today’s focus is the Across terminology management!
How to Terminology
Concept-oriented terminology work has established itself as one of the standard approaches. Most terminology management systems (TMS) on the market follow this approach. The entry structures are also mostly based on a three-level model. This means that they consist of a superordinate entry level (e.g. for images, domain information, etc.), a language level (e.g. for definitions) and a subordinate term level (multilingual terms and their metadata such as status, linguistic information, etc.).
Across Terminology Management in crossTerm
The Across terminology management component “crossTerm” also operates according to this concept-oriented approach. However, here it is easier to achieve the goal here since you are working with two levels only – the entry level and the term level – the language level represents the translation itself.
CrossTerm allows for both manual creation of terminology entries and automatic import of existing terminology databases through various exchange formats, such as TBX. In Across, terminology can also be added or edited interactively, i.e. by exchanging terminology via specific workflows.
Let it flow!
To ensure acceptance and the resulting consistent use of terminology, terminological coordination processes should be introduced. An efficient workflow is essential to ensure that these processes run smoothly. Roles and responsibilities define which participants have which rights as well as for which tasks they are responsible. A workflow can then be used to define how and in what order the process steps are to be perfomed.
In Across terminology management, the roles “project manager”, “terminologist”, “translator”, “editor”, and “proofreader” are already preset, so that users do not have to define all roles themselves. However, these roles are not fixed, but can be adapted and changed. Upon installation, they are then assigned to the individual users by the “Default Supervisor” administrator. The roles can be configured in such a way that a user can, but does not have to, take on any number of roles at the same time.
If you have purchased further licenses for the optional additional components of Across, different roles with specific authorizations are also available for these components. One of these components is crossTerm Now, which can be used to create workflows for terminology coordination processes. However, so that not every single employee in a company is involved in these processes, the roles can be used to determine who can take overactive tasks within a workflow. But how does crossTerm Now actually work?
Workflows with crossTerm Now
This server-based component serves primarily as a search engine for stored terminology, which enables company-wide terminology exchange. The Across Language Server can be used to determine in advance whether persons have read-only or write access.
Terminology should not be maintained and compiled by a single person. Ideally, terminology is negotiated and manifested in coordination processes between the responsible persons. In crossTerm Now, coordination is also possible in the form of workflows that are imported into the application as xml files. For example, users with appropriate authorization can request the translation of a term: Across is the only TMS with integrated terminology workflow for translations “from the manufacturer”.
Users can also make terminology suggestions. Assigned users (usually terminologists) then check this suggestion and either accept or reject it after certain process steps. In either case, the applicant always receives a valid justification.
Approved terminology is then published in the terminology database and made available company wide. It is always possible to adjust the workflow by individually requested correction loops to increase the general quality. This, too, is controlled by various elements within the underlying xml file. Fortunately, you don’t have to be an xml-expert: Across is happy to help!
Interfaces for a well-rounded system landscape
In Across, it is possible to manage and extract terminology, create translation memories (TM), and perform translations. Furthermore, you can implement relatively complex coordination workflows. It can therefore be used as a self-contained system, especially for translation processes. But there is more to it than that, for example through exchange formats such as XLIFF or terminology and TM-APIs. If you as a user want to expand your system landscape outside of Across and thus link terminology, translation, and editing processes, there are many ways to open the system to the outside world. Here, the aspect of data security must be taken into account, but this can be checked individually for each desired interface.
In addition to various interfaces to tools for CMS, layout/design, brand management, PIM, project management, and machine translation, Across also offers linking options to authoring verification systems.
Among other things, the terminology previously agreed upon in the company can be easily used to check texts prior to translation and thus reduce translation costs, for example. It is also possible to access both terminology and translation memories directly during content creation. Optimized content can then be added to existing translation memories and thus be used for later translation projects within the Across translation editor – crossDesk. The same applies to terminology, which can be entered as term candidates directly in the editor of the authoring verification system, enriched with metadata, and transferred to crossTerm.
The perfect terminology workflow is not the same for everyone. Even so, Across itself and in combination with various interfaces to external systems offers the possibility to model such a workflow according to one’s own ideas, meeting the requirements of efficient terminology management as well.
Interested in learning more about how you can efficiently manage your corporate terminology or how you can map the perfect terminology workflow? Then please contact us and we will find the best solution for your needs!
If you have questions for Across, please do contact Ms. Mibs. Reach her at: firstname.lastname@example.org.
Have we piqued your interest in Across? Great! In the next instalment of this blog series, we will go into detail about the connection of the Across Language Server with KantanMT and show you a few special features regarding machine translation.