This scenario is similar to the first one, related to project packages. The client uploads the files of a new translation job into their Business Management System (BMS). The Automator connects to the client’s vendor portal, accepts the job, creates a new project in its own BMS and downloads the project files from the vendor portal.
The main difference between the project packages and bilingual/original files scenarios is in the preparation work of the package for the translator. For quality reasons, it is recommended to package files, reference materials, term bases and even translation memories. Full automation is possible by applying scripting on the Automator’s side, interacting with the Automator’s CAT tool. If for some reason the scripting changes something that the customer did not want to modify (e.g. converting encoding, etc.), there’s another scripting step before delivery to revert this.
PREREQUISITES FOR AUTOMATION
THE BELAZY SOLUTION
The receipt and delivery of the project files is automated by BeLazy as described in Scenario 1. The main difference with that scenario is within the package or file manipulation step. BeLazy does not provide an out-of-the-box solution for such scripting. The kind of solution will vary according to your specific needs. However, BeLazy can help you with creating such scripting, and connect it to your business management system.
CLIENT’S VENDOR PORTAL
AUTOMATOR’S OFFLINE CAT TOOL
Try BeLazy with your team
Bilingual files, original files or package manipulation
Translation management system roundtrip with packages
Translation management system with online work
Vendor portal work with a link to the end-customer’s translation management system
Tell us more about your workflow and we will get back to you shortly