About Termbase Objects

- database used to store terminology and related information. Consists of a termbase definition outlining the structure of termbase entries, and termbase data.

- termbase object that specifies how you want the entries in your termbase to display in MultiTerm and MultiTerm Online. Use the Layout Wizard to create or modify layouts.You can save the layout to the file system as an XDL file.

- termbase object that is used to specify export parameters. For example, the export definition specifies which fields are for export. The export definition can be saved to the file system as an XDX file.

- termbase object that acts as a template for adding and editing termbase entries. The input model can also be used to control access to certain fields.Use the Input Model Wizard to create or modify input models.

- termbase object that is used to define a subset of termbase data for search, import or export purposes. When you apply a filter to one of these operations, MultiTerm evaluates entries according to the filter criteria and distinguishes between matching and non-matching entries during further processing.

- termbase object that is used to specify import parameters. For example, the import definition specifies how to treat import entries that have entry numbers that already exist in the termbase. The import definition can be saved to the file system as an XDI file.

- import definition file saved in XML format with the extension *.xdi.

- feature that allows you to import termbase data from another application, for example MultiTerm 5 or MultiTerm '95 Plus. Use the Import Wizard to add new entries to your termbase or to change existing entries. Termbase data for import must be available in the new MultiTerm XML format.

- Extensible Markup Language. XML is a metalanguage written in SGML. It provides a flexible way to create information formats for sharing on the web and with other applications. MultiTerm exports termbase data to an XML file.

- export definition file saved in XML format with the extension *.xdx.

- layout definition file saved in XML format with the extension *.xdl.

- input model file saved in XML format with the extension *.xdm.

- filter definition file saved in XML format with the extension *.xdf.

- also known as JET (Joint Engine Technology). Database engine developed by Microsoft and used by MultiTerm to store local termbases. Jet was designed to support single-user environments or very small multi-user environments and is used, for example, in Microsoft Access.

- term used to refer to the sum of a user’s rights on MultiTerm Server. This includes rights at server level, access to termbases, membership of termbase roles and object ownership.

About Termbase Objects

Each termbase contains a catalogue of termbase objects. Termbase objects allow users to manipulate termbase data. Objects are based on the termbase definition and therefore, they are termbase-specific.

Each newly created termbase has a number of default objects. Default objects are available to all termbase users but they cannot be edited or deleted. There are five default layout objects, three default export definition objects, and one default object for the input model filter and import definition.

You can create and modify termbase objects using the object wizards. You can save objects to the file system and reload them using the Save As and Load commands. This is useful for exchanging objects with other users of the MultiTerm system. However, because termbase objects are termbase-specific, they can only be reloaded to the same termbase or to a termbase whose definition is compatible with the object for exchange.

All objects are XML-based but when saved externally they have different file types as follows:

In MultiTerm, you can use the Termbase Catalogue dialog box to manipulate and manage termbase objects. You have exclusive access to objects that belong to the catalogue of a local Jet termbase.

You can use the Save As and Load commands to exchange objects with other unconnected users of MultiTerm, provided that they are working with the same termbase or a termbase whose definition is compatible with the object for exchange.

Note: Objects created in the older versions of MultiTerm cannot be used in MultiTerm iX.