CSV import

Proceed as follows:
Open the crossTerm Manager and click .
Once the wizard has started, click Next.
Select CSV as import format.
Select an import template if required and if one already exists.
Attention
Use an import template only for another import of the same data, e.g. during the creation of the import template or for an import of other data with the same entry structures and data categories.
Click Next.
Select the file you want to import.
Select the mode with which you want to import the terminology file.
Tip
In the mode without user interaction, all ambiguous terminology entries that would require interaction (e.g., when importing homographs) are saved to a separate TBX file. These terminology entries can later be imported en bloc.
Activate the option Create import log and click Next.
Tip
The log file will be stored locally in the log directory of the respective Windows user. It can also be saved locally by means of a button in the final step of the wizard.
Apart from the selected import settings, the log file contains detailed information on the imported terminology data and on their processing (e.g. information on the successful import of entries and terms and, if not imported, information on why the import did not take place).
Click Next.
Select the character to be used as data delimiter.
If the CSV file you want to import contains entry and/or term GUIDs, you can activate GUID mapping option.
Click Next.
Select the instance that the terminology is to be imported to and click Next.
If the first line of your CSV file contains the column headers of the associated table, Across sorts them out and inserts them in the left side of the window under CSV fields.
If the first row of your CSV file does not contain column headings and is filled with terminology entries, disable the option The first line is a CSV header.
The columns along with the contents of the first line will then appear in a list on the left-hand side of the window.
Assign the corresponding information types.
Attention
Column headings that are not mapped to any Across category will not be imported.
Click Next.
The next step is the mapping of the languages. In this process, the languages and sublanguages of the terms from the import file need to be mapped to those in Across.
Check the specified languages and sublanguages and change them if necessary.
Attention
Languages from the import file that were not mapped to any Across language will not be imported.
Click Next.
Map the data categories as required.
Attention
Data categories that are not mapped to any Across data category will not be imported.
If a data category is missing, click crossTerm Settings and create it.
Click Next.
If you have assigned picklists in the course of the previous mapping, you need to map the individual values from the columns of the CSV file to the Across values.
Assign the corresponding information types.
If a value is missing, click crossTerm Settings and create it.
Click Next.
The dependencies between individual columns of the CSV file are defined. The columns of the CSV file that do not contain any terms, but other terminology information (such as attributes) are mapped to the respective terms.
Example: The CSV file contains a column with German terms, a column with English terms, and a column with gender details for the German terms. In the following step, the column with the gender information is mapped to the column with the German terms, so that the gender details are added to the respective German terms during the import.
Attention
Columns with other terminology information that was not mapped to any column with terms will not be imported.
Select a column of the CSV file that contains terms and click the icon in the respective row.
From the list on the left-hand side, select the columns with other terminology information that are to be mapped to the selected column containing terms.
Then click > in order to transfer the columns to the right-hand area of the dialog, thereby mapping the columns to the selected column containing terms.
Repeat this for all desired information.
Click OK.
Continue until you have mapped the columns containing other terminology information and, if applicable, the term type, for all columns containing terms.
Click Next.
Define how you would like to proceed if entries and/or terms that should be imported already exist in crossTerm.
Tip
The dialog window will only be displayed if the file to be imported contains GUIDs (e.g. for a reimport) and if GUID mapping has been activated.
Click Next.
Determine whether entries or terms that cannot be imported for various reasons are to be written to an exclusion file.
Click Next.
If required, add further attributes to the termbase you would like to import.
Attention
These attributes are used if the relevant attributes have not yet been assigned in the mapping.
If required, enable the Check for already existing terms and show manual correction dialog option.
In the case of duplicate terms, this will cause you to be asked whether you want to merge the information from the two terms. After activating this option, you can also determine that the manual correction is to take place only if both terms are associated with the same relation or the same subject.
Tip
This option is available if the import file does not contain any GUIDs.
If required, specify that the terms to be imported are set to Released.
If required, save your settings in an import template (Save import template).
Click Import to start the import.
The import process will start.
If you activated the option Check for existing terms and show manual correction dialog and a term to be imported already exists in crossTerm, a dialog window will appear.
Determine how the term to be imported is to be processed.
Confirm with OK.
Click Finish to complete the import.
The terminology contained in the import file has now been imported to crossTerm and is available for your translation work.