Writing templates for TBX elements

A large part of the mapping file consists of templates for TBX elements. When processing your data, the converter program will refer to these templates to determine what kind of element to create, how to derive its content from the content of your MultiTerm fields, where to place it in the new TBX document, etc. This information can be collected under five headings, whose initials spell TEASP, and therefore we have adopted the name teasp for these templates.

You will need to write at least one teasp for each field. If one field (or multiple fields with the same name) are used on different structural levels (concept, index, term), you will need a teasp for each. Finally, if one field corresponds to two or more TBX data categories, each TBX data category will also need its own teasp, and you may choose to write an additional teasp as that field's default (or fallback) mapping.

The pages below will show how to collect the information for a teasp and how to encode it in JSON format for our converter. The letters of TEASP stand for Target, Element, Attributes, Substitution, and Placement, but we will alter this order slightly for easier learning:

  1. Substitution of picklist values, and other transformations of your field's content.
  2. Element and Attributes used in TBX for your data category.
  3. Placement of your (transformed) data within the TBX element.
  4. Target of the TBX element within its containing structure.
  5. Assembling one teasp.
  6. Assembling one field's teasps.