Documentation Center

Converting nested structures in MultiTerm 5

When converting MultiTerm 5 format files you can also create nested structures, provided that you respect the limitations of MultiTerm 5.

Below is an example of a nested structure in MultiTerm Desktop:

English

Term

Context

Year

In this case, MultiTerm Convert will be able to map the old structure to the new structure only in the following situation:

  • The old structure is similar to the new nested structure.
  • The field to be nested is an attribute field - also known as a picklist field.

The reason for this limitation is that all text fields in MultiTerm 5 format are by default on the same hierarchy level, so that nesting is not possible for text fields, but is possible for attribute fields.

For example, the MultiTerm 5 structure is as follows:

<English>

<Context>

<Year>

If the nested structure as described at the top of this section is defined in MultiTerm Convert and if the Year field is an attribute/picklist field in the MultiTerm 5 database, the Year field will appear as a nested field under the Context field in the MultiTerm XML format file.

If, however, the Year field is a text field in the MultiTerm 5 database, it will be ignored during conversion as it is located on the same level as the Context field and thus cannot be converted to a subordinate field in the MultiTerm XML file.

If the same nested structure as described at the top of this section is defined in MultiTerm Convert and the structure in the MultiTerm 5 database is as outlined below, the Year field will also not be included in the target file as it does not match the entry structure defined above.

<English>

<Context>

<Year>