All Industry Engines* are available for translation through the Language Studio Cloud portal. For accessing engines through a TMS system or through API, all your Custom Engines** that have been published will automatically be set up for API access. However, to access our Industry Engines by API, the specific engines you wish to use need to be set up on your user's account in Language Studio. Please see the footnote explaining what an Industry and Custom Engine is.
If you wish to access Industry Engines by API, please read Part Two - How to access Industry Engines through API. However, if you wish to know how to restrict API access to certain Custom Engines, please read Part Three - Restricting API Access for Custom Engines.
Part One, shows you how to find the DC number for the Industry engines.
PART ONE - What Industry Engines are available
All Industry Engines* are available for translation through the Language Studio Cloud portal. For accessing engines through a TMS system or through API, all your Custom Engines** that have been published will automatically be set up for API access. However, to access our Industry Engines by API, the specific engines you wish to use need to be set up on your user's account in Language Studio. Please see the footnote explaining what an Industry and Custom Engine is.
Below are the steps to get you API access to the Industry Engines:
1. Log into Language Studio Cloud with your user login details.2. Find the Industry Engines you wish to use by looking for which current Industry Engines are available for translation. To do this, access the Translate page, which is found in Menu>General>Translate.
3. In the Language Pair field, click the drop down menu to showcase a pop-up menu showcasing all the Language Pairs available. In this pop-up menu, click the Industry Engines tab.
4. Select the Source that you are looking for, which will then showcase the current Targets available (language variants, such as ESMX, ENUS show by default). Then, select the target you want to match the source with.
5. Once the target has been matched, the Language Pair will be populated. From there, click the Domain field to list all the engines for that Language Pair and their Domain.
6. Make a note of the Domain Codes (the 7 digit number) you are interested in and repeat step 3 if there are other language pairs you are interested in.
PART TWO - How to access Industry engines through API.
8. Select the user you wish to add the access to, by clicking the green arrow to the left of the user.
9. In the User Information page, click the Permissions tab.
10. The Permissions tab lists the current permissions for that user. Under Permissions you will see three sub tabs. Click Engine Access Permissions tab and . Note - the only field you are interested in is the API Industry Engines field, NOT the My Custom Engines field.
12. Here is where you will add the relevant domain codes for the Industry Engines you want to give the user to. If this is left blank, the user cannot access any industry engines through the API. Add the engines you wish the user to have access to. When finished, click Save.
13. Exit the page and now the user will have access to these industry engines through API.
14. It might take a small minute or two for the settings to refresh and whichever TMS or API system you are using, make sure that you reconnect, so that the settings have refreshed.
15. If there are any other users for your account that need this access, please repeat steps 8 to 14 again for that user.
PART THREE - How to restrict API Access for Custom Engines
16. All live Custom Engines on the account are available for API use automatically. If however, there is a need to restrict which engines are available for API use, then just add the engine in the My Custom Engines field under Engine Access Permissions (as described in Part Two). Add the engines you wish the user to have access to (separated by comma). When finished, click Save. Please note - by restricting the engine access in this field, the user will not be able to access other Custom Engines by API.
If there are any problems, please contact support@omniscien.com, with a screen print of the user's permissions, what TMS system you are using and what credentials you are trying to connect with.
Footnote
* Industry Engines
You have access to a vast array of INDUSTRY engines. INDUSTRY engines are domain specific, “off the shelf”, ready to translate engines that you can use without any customization – simply use them out of the box.
The Language Studio team is progressively deploying 12 industry domains across all 540 language pairs – providing the most comprehensive set of pre-built, ready-to-use industry engines and language pair coverage of any machine translation platform. You can immediately access and use all of the deployed INDUSTRY engines as they are released.
** Custom Engines
There are two types of Custom Engines.
BASIC Engines
A Commodity Level Rapid Customization that delivers a working engine in just a few hours.
This is a Do-It-Yourself (DIY) custom engine where a user is in complete control of the process and training is automated. Unlike PROFESSIONAL custom engines that are guided by Language Studio Experts, BASIC custom engines are managed entirely by the user.
PROFESSIONAL Engines
An Expert Guided Comprehensive Customization that is based on a collaborative effort between Language Studio Experts and the user, and which expands the features offered in a BASIC custom engine to deliver the highest possible translation quality and consequently productivity improvements.
Language Studio Experts guide, manage and execute all of the technical tasks and, after submission of relevant data by the user, there is minimal user effort required in most cases. Only tasks where user input or language specific input is required are reverted back to the user. Most tasks are performed by the Language Studio platform and guided by a unique Quality Improvement Plan that is specific to your engine. Through this collaborative effort, a high quality custom engine can be built in a very short time.
PROFESSIONAL customization includes many processes over and above a BASIC customization such as deep data cleaning, data manufacturing, term management, gap analysis and adaptation for writing style and target audience.