| Table of Contents |
|---|
Guidelines
Before reading the content of this article, you may want to familiarize yourself with the process of a standard, “manual” we recommend that you find out about standard, “manual" way to create rate cards for users. If so, please see the following article: How to create a rate card for a linguist. |
|---|
The whole process of importing and implementation takes place on the XTM International Support team side. When requesting such an action, you should provide them with create a created .csv file and provide it to them.
Please, find Find attached the template file.
...
A provided file can contain the IDs of multiple usersuser/LSPs' IDs for LSPs for whom rate cards need to be added.
| Note |
|---|
IMPORTANT! When creating a file with multiple usersuser/LSPs' LSP IDs, they need to be separated separate them with a comma! Also, you might sometimes you may incorporate rate cards that have the same language combination, same workflow steps and same subject matter. Please, keep Keep in mind that this will not work because the rate cards are duplicated and either need either different subject matters or workflow steps. |
Such file should be built specificallyA specific version of this kind of file needs to be created.
DATA FROM THE TEMPLATE:
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
6 |
|
7 |
|
8 |
|
...
First line → This is a primary header and it should not be changed: do not change it.
| Note |
|---|
IMPORTANT! There should only be only one header at the top! Copying this header before for each rate card is incorrect. |
1 |
|
|---|
Second line → Either Either enter LSP IDs or or USER IDs should be provided , but not both! Note that the client Client field is required, as it should be referred to is referenced as the company name to which the rate card is being imported to.
Example for the (user):
2 |
|
|---|
Example for the (LSP):
2 |
|
|---|
| Note |
|---|
IMPORTANT! The LSP/user ID needs to be provided by the the LSP account ID and IDrespectively, and not from the LSP connection field. |
Third line → This is a general header and it should not be changed: do not change it.
3 |
|
|---|
The headers above headers indicate point to this part of the rate card:
...
Fourth line → Breaking line that should not be changed. It may might seem empty, but when you edit the file in Excelin Excel/OpenOffice Calc/Notepad++, it really is.
For example, if you want to add a Minimum Charge, you need to add it to the line below, which is row 5 - , not row 4. This is how what it looks like in the CSV file:
...
4 |
|
|---|
Fifth line → Indicates Identifies the rate card data that is being created , as it matches the headers from line 3.
The To specify the language combination should be passed, as , use this format: target_languageCode-source_languageCode, e.g. en_GB-pl_PL. Language codes can be found in the XTM Cloud manual.
The format should be en_US-de_DE
When adding more than just one language combination, they should be separate them with separated by commas without spaces, e.g. en_GB-pl_PL,en_GB-ar_AA.
...
Sixth line → Headers for the following next part of the rate card.
6 |
|
|---|
...
7th, 8th line, and so on → Indicate the data per workflow step (“Translate” and “Correct” respectively"Translate" and "Correct" ).
| Note |
|---|
IMPORTANT! Any workflow step name you add to this import file must exist on your XTM Cloud instance beforehand in Configuration → Settings → Workflow → Workflow steps (only an administrator can add this). Furthermore, including you cannot include a certain particular workflow step without setting any rates for that step is incorrect (see the 9th line below as for an example). Please, remove Remove this step. |
7 |
|
8 |
|
9 |
|
...
| Note |
|---|
IMPORTANT! The rate card import tool uses commas, not full stops, for decimalsas decimal separators. If you notice that you have used full stops, please replace all characters them with commas. There should not be a single full stop in the file. |