Import terminology from a CSV file

Prerequisite

• Your import file has the CSV format and is UTF-8 encoded.

• You have already created the languages you want to import

• You have already created the fields and, if applicable, the field values of the database.
  
  

Import the CSV file with the import wizard

Follow all the steps and click Next at the end of each step.

1. source
   In the first step, specify the import file.
   Select CSV under Format.
   Click on Select File. Select the source file in the following dialog.

Open

Enter the Delimiter separator. The import supports:

• Tab

• comma

• Semicolon

2. import configuration
   If you have saved an import configuration, you can load it now. To do this, click on Select File.

3. Concept

First select whether you want to add or replace the terms:

• Add: Data that already exists will not be changed. Existing terms are also uploaded. Select this option if the import file only contains part of the desired term set.

• Replace: The content of the TermBase is replaced with the content of the import. Data that was previously saved will no longer be available afterwards. Select this option if the import file contains the complete new database or if you want to replace the existing TermBase.

Then specify whether you want to import the Concept ID from the source. To do this, activate the checkbox.

Open

Select the field in which the concept ID is saved in the source file.

4. Languages

Specify here which languages are to be imported from the source file.

Enter the following information:
Term in original: Column in which the terms are contained.
Original language field: Column that defines the corresponding language for each term.
Then click on the green plus symbol and assign the languages:
Original field: The value in the Original language field defined above
Languages: The target language in the TermBase
Click on the plus symbol again to assign another language. Click on the red X to remove a language from the selection.

5. Mapping
In this step, you assign the fields from the source file to the fields in the TermBase.
For each field from the source file, specify how it should be transferred to TermBase.

The columns mean in detail:
Original field: The field name in the original file.
Level: Selection of whether the field belongs to the entry/concept or to the term.
Type: The field type into which the field is to be imported (for a more detailed description, see TermTiger - Fields - [EN] Documentation v6 - Congree Documentation)
TermTiger field: The exact field into which the value is to be imported.
Original value(s): The content of the field in the original file
TermTiger values: For picklist fields, you can assign the values from the source to the values in TermTiger here
Language Restrictions: Specify if the field content only applies to one language.
Content language: Specify the language for which the content is to be imported.

6. Save import configuration
Click Save Config to save the settings selected so far as a .json file

Start import
Click Start import to start the import.

At the end of the import, you will be informed of how many terms have been imported in a field highlighted in green. If the import has failed, this is indicated in a field highlighted in red.

Notes on the import

Column names
You can use any column names in the CSV file. Mapping takes place during the import. Each column name must be unique.

Minimum configuration
You always need the columns:

• Term (word to be imported)

• Language (to which language does this term belong)

• Usage (preferred, permitted, prohibited)

You can add all other details in separate columns.

Languages

Use standard languages and always use the same language abbreviation for the same languages. Some third-party systems offer sub-languages that are only supported in this system. These sublanguages may not be imported correctly.

Especially if the source file was created manually, it can happen that different specifications are used for the same meaning: English, en, ENG, en-GB. Therefore, check the information: Which (sub)language is actually meant?

For translated field content, use a separate column for each language, e.g. Definition_de and Definition_en. The exact assignment is made in step 5 - Mapping via the Content language column.

Definitions

The CSV file is structured with the terms as a basis, i.e. a separate line is used for each term. The term/concept is only assigned via the concept ID. For this reason, information can occur more than once at concept level. A concept always has the same definition, which applies to all terms, both for preferred terms and for negative terms. The import always uses the content from the first line that belongs to this concept for such fields. Therefore, make sure that this first line always contains all information at concept level. In order to be independent of the sorting of the CSV file, we recommend copying the contents at concept level for all associated terms.

Example: Make sure that the definition field for a negative term contains exactly the same text as the definition field for the associated preferred term.