Importing a TBX File

The TBX format is the default WorldServer format for importing and exporting terminology databases (TDs).

1. From the term management screen at Tools > Term Databases > Term Database: <TD>, click Import TD....
2. Select the TBX option and the TBX file to import. This file can be in a zip file. Also, select an Import status. You can choose whether to import each term's existing status or to assign a selected status to every term. For details, see the topic on "Importing Term Statuses."
3. Click Next >>. The field and language matching page displays—Import TBX Entries into Term Database <TD>(Step 2 of 2). This screen allows you to select the languages and attributes that correspond to the import file. The language drop-down only shows choices if there is some ambiguity as to the country. That is, a language of EN might map to US or UK English.
   Note: You can create a new attribute by selecting (create new) for a term or entry attribute. This brings up the new attribute editor—Import TBX into Term Database <TD> (Step 3 of 3)—when you click Import. Configure the appropriate attribute types.

   XCS (eXtensible Constraint Specification) is the TBX way of specifying constraints on metadata. It lists languages, data category names and permissible picklist values for a termbase file. In WorldServer terms, XCS lists the languages, attribute names and selector attribute values of a term database. TBX specifies a default XCS file with data category information based on a selection from ISO 12620, which in turn attempts to define a standard list of data category names and definitions. Having a substantial standard list to choose from gives terminology users a common vocabulary, greatly improving interoperability and blind interchange. WorldServer takes advantage of this common vocabulary where possible.

   In this Import TBX into Term Database <TD> (Step 3 of 3) screen, you can create attributes on the fly to match data categories in the TBX import file that do not yet have a WorldServer equivalent. If these data categories are present in the default XCS file, WorldServer attempts to create attributes that correspond to its knowledge of these data categories. If the data category has a picklist data type, WorldServer prepopulates the attribute creation dialog with a selector attribute, its values already prefilled with the default XCS' definitions. Other data categories result in text fields. TBX import does not read the incoming TBX file's companion XCS file or enforce its constraints.

4. Match both languages and attributes in the import files to WorldServer counterparts, or ignore them. Click Import.
   Note: Because TBX format is XML and the encoding is stored in the prolog, you do not need to specify the encoding.

   WorldServer imports the TBX file. You are done.