Term base in CSV format
Below you can see the CSV format of memoQ and QTerm term bases.
The following settings are used for exporting term bases through WS API:
- File format: CSV
- Delimiter:
; - Encoding: UTF-8
- Field headers are written in first row
- One entry per line
- Images are not exported
Custom fields of QTerm term bases are not exported to CSV format.
The order of columns is bound. The first few columns contain entry level properties, followed by language and term level fields. Both of them can be repeated if the term base has multiple languages or an entry has multiple terms for a language.
For example, an English-German term base with only one English term and multiple (one or two) German terms for each entry has the following structure:
- Entry level fields
- Language level fields for English
- Term level fields for English term
- Language level fields for German
- Term level fields for the first German term
- Term level fields for the second German term
The fields for each level are listed below, in the order of columns in the CSV files.
Entry level fields
The following fields are present in the exported CSV of standard memoQ and QTerm term bases. The order of columns is the same as in the following table.
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Id | Entry_ID | Number | The id of the TB entry. |
| Subject | Entry_Subject | Text | The subject of the TB entry. |
| Domain | Entry_Domain | Text | The domain of the TB entry. |
| Client | Entry_ClientID | Text | The client of the TB entry. |
| Project | Entry_ProjectID | Text | The project of the TB entry. |
| Created | Entry_Created | DateTime | The creation UTC date of the TB entry. In format M/d/yyyy h:mm:ss tt with en-us culture. |
| Creator | Entry_Creator | Text | The creator of the TB entry. |
| Modified | Entry_LastModified | DateTime | The UTC date of the TB entry's last modification. In format M/d/yyyy h:mm:ss tt with en-us culture. |
| Modifier | Entry_Modifier | Text | The last modifier of the TB entry. |
| Note | Entry_Note | Text | The note of the TB entry. QTerm does not have a built-in Note field, this column will be present if there is a custom entry level field, called Note. |
| Image | Entry_Image | Text | The image url of the TB entry. Image is not exported through WS API to CSV format, this column is always empty. To get the images through API, use the TBX export functionality. |
QTerm-specific entry level fields
In addition to the fields listed above, QTerm term bases have the built-in Image caption field. When exported to CSV, this is the column next to Entry_Image.
As QTerm term bases have a flexible entry structure, there might be multiple custom entry level fields. These fields get the X_ prefix before their name in the CSV header, e.g. X_MyField, where MyField is the name of the custom field.
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Image caption | Entry_ImageCaption | Text | The caption for the image of the TB entry. |
| Custom metadata field | X_[Name] | Text | Number | True/False | Date | Media | Picklist (single) | Picklist (multiple) | Value for the given custom metadata field (manual export only) |
Warning
Actually, the custom QTerm fields are not exported through WS API. To export these custom term base fields, use the TBX export functionality.
Language level fields
The following field is present in the exported CSV of standard memoQ and QTerm term bases.
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Definition | [Language]_Def | [Language]_[Sublanguage]_Def | Text | The definition of the language. |
Note
Languages:
Languages appear with their English names and they can also contain sub-languages. Words in the language names are separated with _ characters.
Please see the following examples:
- [Language]: English
- [Language]_[Sublanguage]: English_United_States
QTerm specific language level fields
For QTerm term bases you can specify multiple custom language level fields. These fields follow the built-in language level fields and get the X_ prefix before their name, e.g. X_MyField, where MyField is the name of the custom field.
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Custom metadata field | X_[Name] | Text | Number | True/False | Date | Media | Picklist (single) | Picklist (multiple) | Value for the given custom metadata field (manual export only) |
Warning
Actually, the custom QTerm fields are not exported through WS API. To export these custom term base fields, use the TBX export functionality.
Term level fields
The appearance of term level fields is quite different in case of regular memoQ and QTerm term bases. You can see the two formats below.
memoQ term bases
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Term | [Language]_Def | [Language]_[Sublanguage]_Def | Text | Term for the given language |
| Case sensitivity | Term_Info | CaseSense | CasePermissive | CaseInsense | Defines the case sensitivity level of the term (Sensitive, Permissive or Insensitive). |
| Gender | Term_Info | Masc | Fem | Neu | The grammatical gender of the term (Masculine, Feminine or Neuter) |
| Number | Term_Info | Sg | Pl | The grammatical number of the term (Singular or Plural). |
| Grammar part of speech | Term_Info | Noun | Verb | Adj | Adv | PoSOther | The grammatical category of the term (Noun, Verb, Adjective, Adverb, Other). |
| Forbidden | Term_Info | NonTerm | Defines whether the term is forbidden. If it's not given, the term is not forbidden. |
| Matching | Term_Info | NoPrefix | HalfPrefix | Prefix | Custom | Defines the degree to which partial matches are allowed against this term (Exact, 50% prefix, Fuzzy or Custom). |
| Example | Term_Example | Text | The example of the term. |
Note
Term_Info:
In the CSV file Term_Info column contains the Case sensitivity, Gender, Number, Grammar of speech, Forbidden and Matching properties of a term. These properties are separated with ; character, which is also used as CSV delimiter so the string listing the values of this field must be surrounded with " characters. The order of the value is bound, but all of them are optional.
If one of the properties is missing, this means that it's not specified.
For example: "CasePermissive;Noun;HalfPrefix"
When importing a CSV file, if this column is empty, the default values for case sensitivity (Permissive) and matching (50% prefix) will apply, and the other Term info fields will be empty.
Note
Languages:
Languages appears with their English names, they can also contain sub-languages. Words are separated with _ characters.
Please see the following examples:
- [Language]: English
- [Language]_[Sublanguage]: English_United_States
QTerm term bases
For QTerm term bases you can specify multiple custom term level fields. These fields get the X_ prefix before their name, e.g. X_MyField, where MyField is the name of the custom field.
| Property | Column in CSV | Value | Description |
|---|---|---|---|
| Term | [Language]_Def | [Language]_[Sublanguage]_Def | Text | Term for the given language |
| Case sensitivity | Term_CaseSensitivity | CaseSense | CasePermissive | CaseInsense | Defines the case sensitivity level of the term (Sensitive, Permissive, or Insensitive). |
| Forbidden | Term_Forbidden | NonTerm | Defines whether the term is forbidden. If its value is empty, the term is not forbidden. |
| Matching | Term_PrefixMatching | NoPrefix | HalfPrefix | Prefix | Custom | Defines the degree to which partial matches are allowed against this term (Exact, 50% prefix, Fuzzy or Custom) |
| Custom metadata field | X_[Name] | Text | Number | True/False | Date | Media | Picklist (single) | Picklist (multiple) | Value for the given custom metadata field |
Warning
Actually, the custom QTerm fields are not exported through WS API. To export these custom term base fields, use the TBX export functionality.