When you import terms from another terminology management system into Acrolinx your data may be organized into fields that are different from the fields Acrolinx uses. To import your data correctly, you must indicate which column or element in the import file matches a corresponding field in the terminology section. This process is called mapping.
You can use the field mapping page to configure how the term import wizard matches your source data to fields in the terminology section.
The source data mapping page has the following parts:
Part |
Used to |
---|---|
Source data section |
Select and map columns or elements from your import file. |
Show mapped columns/elements button |
Show or hide columns and elements that you’ve already mapped in the source data section. By default, mapped columns and elements are displayed in gray formatting. |
Mapping buttons |
Map a selected column or element to a corresponding field (Mapping Term Columns, Mapping Identifier Fields, Mapping Descriptive Information). |
Term template section |
Add new term templates (Mapping Term Columns, Mapping Identifier Fields, Mapping Descriptive Information) and manage mapping and global values for fields within term templates. |
Unmap buttons |
Unmap columns or elements from fields. |
Field State icons |
Indicate the current state of completion for a particular field. A field can either be mapped to your source data or have a global value. |
Global value dropdown |
Set a global value for a field. |
Automap button |
Automatically map a selected column or element to a field on a term template with a similar name. |
Batch Unmap button |
Unmap a selection of columns or elements with one click. |
Add Field button |
Create a new field for a column or element in your source data. |
Field Panels |
Show or hide a group of fields on a term template. |
The term template section always contains at least one term template. A term template contains all of the fields that store information about a term in Acrolinx. You use a term template to define how the term import wizard should populate the values for each of the fields.
You can create additional term templates if you have a CSV, which contains more than one term column. Additional term templates enable you to define different field settings according to the types for terms you have in each column.
The fields on a term template are grouped into collapsible panels based on the type of information that they store.
A term template contains the following field panels:
Panel Name |
Contains |
---|---|
System fields |
Fields that are compulsory for a term. |
Identifier fields |
Fields that identify a term or term entry |
Administrative fields |
Fields that contain information about the edit history of a term. This panel is only available when importing ACTIF files or when using an ACTIF custom XML transformation. |
Advanced term setting fields |
Fields that control advanced linguistic settings |
Custom fields: conceptual |
Custom fields that contain information relating to an entire concept. |
Custom fields: Term-specific |
Custom fields that contain information that is specific to an individual term. |
Acrolinx provides two types of identifiers for term entries and individual terms.
Type |
Use to |
---|---|
Custom identifier |
Retain identifiers generated by another system. The following fields are used to store custom identifiers:
You can also edit custom identifiers in the terminology section. If you don’t have your own identifiers a 13-digit number is automatically generated and stored in this field. |
Universally Unique Identifier |
Generate and store a Universally Unique Identifier (UUID) for term entries and individual terms. You can use Universally Unique Identifiers to ensure that your terminology identifiers remain unique when transferring terms between different installations.
WarningAcrolinx requires all term entries and terms to have a UUID. If your terms don’t have UUIDs, Acrolinx generates one for you when you create a term. |
After you have finished mapping columns or elements in the source data section, review the field states on the term template section to see if any further action is required to import your file.
A field can have the following states:
Icon |
State |
Means |
|
---|---|---|---|
|
Incomplete |
The field is a system field, is unmapped, and doesn’t have a global value. |
|
|
Mapped |
The field is mapped to a column or element in your source data. |
|
|
Ignored |
The field will be ignored during the import. Tip: All custom fields are set to 'ignored' by default. |
|
|
Global value |
The field has a global value defined. |
|
|
Same as head term |
The instance of the field uses whatever value is defined for the field on the head term template. This state only applies to an instance of a field on an additional term template. Example: If 'status' is set to 'proposed' on the head term template, you can configure the German term template to use the same status value as the head term template. If you change the status to 'preferred' on the head term template, the status for German terms will be automatically updated to 'preferred' as well. Tip: All system fields on additional term templates are set to this state by default. |