Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Guidelines

Before reading the content of this article, you may want to familiarize yourself with the process of a 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 Support team side. When requesting such an action, you should provide them with a created .csv file.

Please, find attached the template file.

A provided file can contain multiple users/LSPs' IDs for whom rate cards need to be added.

IMPORTANT!

When creating a file with multiple users/LSPs' IDs, they need to be separated with a comma!

Also, sometimes you may incorporate rate cards that have the same language combination, same workflow steps and same subject matter. Please, keep in mind that this will not work because the rate cards are duplicated and need either different subject matters or workflow steps.

Such file should be built specifically.

Data from the template:

1

lsp id;client;user id;;;;;;;;;;;;;;;;;;

2

mpera2;488169,385306;;;;;;;;;;;;;;;;;;

3

ratecard name;description;activity;language combinations;subject matter;calculate using;charging type;Base Rate;Words Per day;Minimum Charge;Fixed price per project;Fixed price per language;Fixed price per file;Management fee;MinManagementFee;MinChargePerLang;HalvedManagementFee;Currency

4

;;;;;;;;;;;;;;;;;;;

5

rate1;1rate;active;en_GB-pl_PL,en_GB-ar_AA,en_GB-zh_CN;other;Actual price;per word;;2;2;;;;;eur;;;;;

6

workflow step name;fixed price per project;fixed price per language;Fixed price per file;management fee;rush job premium;minimum charge;price per hour;no matching;ice;leveraged;95-99% Fuzzy match;85-94% Fuzzy match;75-84% Fuzzy match;95-99% Fuzzy repeat match;85-94% Fuzzy repeat match;75-84% Fuzzy repeat match;machine translation;Non-translatable;repeat;Fixed price per word

7

translate;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

8

correct;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

EXPLANATION:

  • First line → This is a primary header and it should not be changed.

IMPORTANT!

There should be only one header at the top! Copying this header before each rate card is incorrect.

1

lsp id;client;user id;;;;;;;;;;;;;;;;;;

  • Second line → Either LSP IDs or USER IDs should be provided, but not both! Note that the client field is required, as it should be referred to as the company name the rate card is being imported to.

Example for the user:

2

;mpera2;488169,385306;;;;;;;;;;;;;;;;;

Example for the LSP:

2

123123;mpera2;;;;;;;;;;;;;;;;;;

IMPORTANT!

The LSP / user ID needs to be provided by the LSP account ID and ID respectively, and not from the LSP connection field.

  • Third line → This is a general header and it should not be changed.

3

ratecard name;description;activity;language combinations;subject matter;calculate using;charging type;Base Rate;Words Per day;Minimum Charge;Fixed price per project;Fixed price per language;Fixed price per file;Management fee;MinManagementFee;MinChargePerLang;HalvedManagementFee;Currency

The above headers indicate to this part of the rate card:

  • Fourth line → Breaking line that should not be changed. It may seem empty, but when you edit the file in Excel/OpenOffice Calc/Notepad++, it really is.

For example, if you want to add Minimum Charge, you need to add it to the line below, which is row 5 - not 4. This is how it looks like in the CSV file:

4

;;;;;;;;;;;;;;;;;;;;

  •  Fifth line → Indicates the rate card data being created, as it matches the headers from line 3.

The language combination should be passed, as target_languageCode-source_languageCode, e.g. en_GB-pl_PL. Language codes can be found in the XTM manual.

The format should be en_US-de_DE

When adding more than just one language combination, they should be separated by commas without spaces, e.g. en_GB-pl_PL,en_GB-ar_AA.

5

rate1;1rate;active;en_GB-pl_PL,en_GB-ar_AA,en_GB-zh_CN;other;Actual price;per word;;2;2;;;;;eur;;;;;

  • Sixth line → Headers for the following part of the rate card.

6

workflow step name;fixed price per project;fixed price per language;Fixed price per file;management fee;rush job premium;minimum charge;price per hour;no matching;ice;leveraged;95-99% Fuzzy match;85-94% Fuzzy match;75-84% Fuzzy match;95-99% Fuzzy repeat match;85-94% Fuzzy repeat match;75-84% Fuzzy repeat match;machine translation;Non-translatable;repeat;Fixed price per word

  • 7th, 8th line, and so on → Indicate the data per workflow step (“Translate” and “Correct” respectively).

IMPORTANT!

Any workflow step name you add to this import file must exist on your XTM instance beforehand in Configuration → Settings → Workflow → Workflow steps (only an administrator can add this).

Furthermore, including a certain workflow step without any rates for that step is incorrect (see the 9th line below as an example). Please, remove this step.

7

translate;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

8

correct;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2

9

review;;;;;;;;;;;;;;;;;;;;

IMPORTANT!

The rate card import tool uses commas, not full stops, for decimals. If you notice you used full stops, please replace all characters with commas. There should not be a single full stop in the file.

  • No labels