30\/07\/2024<\/small><\/p>\n<\/div> A translation is the result of many small steps within a process chain. This begins with commissioning the project, continues with the provision of relevant information and requirements to the service provider, and ends with the delivery of a finished translation. There are some complex intermediate steps where human input is required: this is particularly important when preparing files for translation with translation memory systems or quality checks.<\/p>\n<\/div> At other points in the translation process, however, there is potential for automation<\/a>. Repetitive tasks, such as importing and exporting files or creating orders in the customer portal when content is moved from one tool to another (e.g. from the CMS to the CAT tool), can now be completed automatically. Performing these steps manually not only costs a lot of time and patience, but every manual intervention also represents a risk, as errors can creep in during repetitive tasks. For this reason, effort is being made in translation to automate avoidable manual tasks in the process chain.<\/p>\n This usually involves using new technology and software. The advantage of automated processes is that they are consistent and precise. They increase efficiency, accelerate projects and reduce errors. This enables people to concentrate on complex and creative tasks.<\/p>\n<\/div> But implementing this is often difficult, which can cause technical and corporate complications, even within departments. When automating processes between two different parties \u2013 such as clients and service providers, as is the case with translation \u2013 many more aspects need to be taken into consideration. In an ideal scenario, you should first evaluate whether automation is possible and worthwhile.<\/p>\n Fortunately, a technical solution is already available for exchanging data between editorial systems and translation technology. The Association of German Editorial and Management System Manufacturers (Verband Deutscher Redaktions- und Content Management System Hersteller, DERCOM) developed its own interface for precisely this purpose: the Common Translation Interface (COTI<\/a>) (only available in German). It has three levels for different applications. While level 1 still requires manual export, import and exchange of files, levels 2 and 3 enable different levels of process automation between the client and translation service provider.<\/p>\n<\/div> From COTI level 2, it is possible to link the tool on the client side (e.g. an editorial system) with the tool on the translation service provider side (e.g. a CAT tool or a translation management tool, such as oneTask<\/a>). This means that both sides have access to a shared folder or service and the tools can store and retrieve files and exchange information independently without either of the parties having to intervene. Files no longer need to be manually imported or exported before or after the translation, and compiling project information (e.g. languages and delivery dates) and commissioning the translation can also be automated. From level 3, the interface can even do without files altogether and communicate information between the tools using just pure data. Below we look at the pros and cons of introducing an interface for automation.<\/p>\n<\/div> Advantages:<\/p>\n Disadvantages:<\/p>\n Advantages:<\/p>\n Disadvantages:<\/p>\n In addition to direct connections using an interface, it is also possible to automate translation processes in other ways. In practice, particularly complex process steps are simplified by specific programming. In terminology management, for example, manually checking and then processing the company’s own terminology databases can be partially automated. Depending on the size of the terminology database, several thousand entries in different languages may need to be scrutinised, a task which is time-consuming and susceptible to errors. oneword combats this problem with script-based partial automation at several points. Targeted, automated analysis makes it possible to quickly gain an overview of the clean-up potential in a database. The necessary corrective measures that are identified and initiated from the analysis can also be simplified by partial automation, for example by automatically checking the corrections before they are added to the database. This service is called oneCleanup<\/a>. We also use scripting to simplify translation-related terminology work for everyone involved, such as adding foreign-language terminology, and to clean up translation memories.<\/p>\n Last but not least, there are also options for automation when using additional software that is customised to simplify certain process steps. For national corrections and reviews, for example, we rely on our online review platform oneReview<\/a>: Automated workflows and centralised real-time access for all parties involved make complex review processes efficient and less susceptible to errors. The links to common CAT systems also automate project creation and the final transfer of changes to the document and your translation memory.<\/p>\n<\/div> The automation of translation processes, especially through interfaces such as COTI, offers considerable advantages, such as increased efficiency and a reduction in errors. It enables repetitive tasks to be processed smoothly and takes the pressure off everyone involved, leaving more time for complex and creative tasks. Remember that every purchase and connection also comes with costs and technical effort. However, the advantages clearly outweigh the disadvantages in most cases.<\/p>\n<\/div> Would you like to find out more about your individual options for automation, connecting your tools to our systems, interfaces or other options for process optimisation? Then feel free to get in touch with our contact person for process management at e.tillmann@oneword.de<\/a>.<\/em><\/p>\n<\/div> Learn more about what we do and what sets us apart from traditional translation agencies.<\/p>\n We explain 8 good reasons and more to choose oneword for a successful partnership.<\/p>\n<\/div>Automating translation processes between clients and service providers: what options are there?<\/h1><\/div>
Potential for automation<\/h4><\/div>
Challenges during implementation<\/h4><\/div>
Available solutions: the COTI interface<\/h4><\/div>
Advantages and disadvantages of integrating a COTI interface<\/h4><\/div>
Internal use case:<\/em> Connecting an editorial system (e.g. a CMS or PIM) to the company’s internal translation technology<\/h6><\/div>
\n
\n
External use case:<\/em> Connecting an editorial system (e.g. a CMS or PIM) to external translation service providers (e.g. to the customer portal oneTask<\/a>)<\/h6><\/div>
\n
\n
Further automation options in the translation process<\/h4><\/div>
Summary<\/h4><\/div>
Recent Posts<\/h4><\/div>\n\t\t
\n\t\t\t\t\t\t\t\t\t\t\t
8 good reasons to choose oneword.<\/h5><\/div>