Salesforce

How to create a termbase from a termbase definition (XDT) and termbase data (XML) file in MultiTerm

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentMultiterm 2021
Multiterm 2019
Multiterm 2017
Symptoms/Context
You receive a termbase definition file (*.xdt) and a file containing termbase data (*.xml) exported from an existing termbase from your translator/client/customer to create a termbase with and to use it for your terminology work or translation project. However, you do not know what to do with these two files or how to create a termbase based on the termbase definition (*.xdt) and the exported termbase data (*.xml).
Resolution

Step 1 - Create a new termbase

  1. Start MultiTerm

  2. Create a new termbase via File > New Create Termbase from the menu: 

  3. Select a location and enter a name for the termbase: 

  4. Click Next.

  5. Select Load an existing termbase definition file and click on Browse…:

    User-added image

  6. Select the termbase definition with the *.xdt extension and click Open:

     

  7. Back in the Import Wizard, you will see the path of the Termbase Defnition:

  8. Click Next.

  9. Enter a name for your termbase and, if required, add a description and copyright notice.

  10. Now click Next through all the following wizard steps until you reach the Termbase Wizard step Wizard Complete and click Finish.

 

Step 2 - Importing termbase data

  1. Open the Termbase Management view.

  2. In the navigation tree, find your termbase and select Import:

  3. Select Default import definition from the list on the right-hand window and then select Process... from the menu to call up the Import Wizard

    User-added image

  4. The Import Wizard starts. Click on Browse… and select the *.xml file that you received and you want to import into the termbase you created based on the termbase definition:

     

    NOTE:

    • Select Fast Import (import file is full compliant with MultiTerm XML) if you do not want validation checks to be performed on the entries in the import file.
    • Select Perform full reorganisation after import if, for example, you are updating an existing termbase with new/changed data and are experiencing problems. It may be that you are getting errors after the import such as unwanted duplicates or the fuzzy search is not working correctly. Selecting this option rebuilds the indexes from scratch directly in the import wizard and prevents the need for a full manual reorganization after import.
  5. Click Next.

  6. In step 3 of the Import Wizard you will see the Validation Settings. Click Save As… and browse to a location of your choice:

  7. Enter a name for the Exclusion file in the Save As.. browse dialog and press Save to close the dialog again:

  8. You will return to the Validation Settings page of the Import Wizard where you see the path to which the exclusion file will be saved:

     
     

    About the Exclusion file: Termbase entries that are excluded from an import because they failed a validation check are placed in an import exclusion file. The exclusion file is an *.mtf.xml file which itself can be imported into a termbase, if required.

    Additional options:

    • Select Allow incomplete entries to import entries where they hold no data for a field that is mandatory.
    • Select Allow over-complete entries to import entries where they have more fields than the termbase entries. The additional fields and data are not added to the existing termbase definition.
    • Select Ignore sub languages to ignore sublanguages when importing entries.
      • If you do not select this option, the Import Wizard adds terms to the correct sub-language. However, if the input file contains sub-languages but the termbase does not, the import wizard will not create the sub-language indexes as part of the import.
      • If the import file contains sublanguages but the termbase does not, all entries are imported to the relevant super-language.
      • If the import file does not contain sublanguages but the termbase does, all entries are imported to the first sub-language index in the termbase.
      • If both the import file and the termbase contain sublanguages, then all entries from the import file are imported to the first sub-language index in the termbase. This applies whether or not the sublanguages in the import file and the termbase match.
  9. Click Next.

  10. In step 7 of the Import Wizard you will see the Import Definition Summary.

  11. When you click on Next, the import will start.

  12. When the import is finished, you have created the termbase.

Root Cause
This article describes how to create a termbase from a termbase definition and termbase data file.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by