2.2. Defining lexicon structure

In LEXUS lexica consist of their structure and content. You will always need to define a structure for your lexicon before you can add content to it (i.e. lexical entries). The default structure of a new lexicon is a basic LMF structure and consists of the LexicalEntry data component which, in its turn consists of two data containers: Form (with the by default introduced data category Lexeme) and Sense (see Figure 1.1). As explained before, data containers are holders for data categories, which are in turn the actual value holders. You could compare this to a computer file system. The data containers are the folders and the data categories are the files, which hold their content. It is up to you to decide what you would want the structure of your lexicon to be. Group data categories which relate to the form of the lexical entry under Form (e.g. orthography, image, plural markers etc.) and data categories related to meaning under Sense (e.g. gloss, definition). It is possible to move the elements within the structure (but only within the same data container). To move the elements you need to drag and drop them into a desired location in the tree.

Moving elements in the structure tree

Figure 2.2. Moving elements in the structure tree


For users with no previous experience with LMF we recommend to visit the LMF web site.

2.2.1. Schema Element Editor

Once you have saved your new lexicon, you will be automatically redirected to the Schema and View Editor where the structure of your lexicon is yet to be defined (you can also access it by following Switch To >Schema and View Editor or double-clicking on the lexicon while holding the Shift button).

The Schema Element Editor window consists of two frames. The left frame (called Lexicon structure) shows the default structure of your new lexicon that consists of two data containers: Form (with the Lexeme data category) and Sense. The right frame consists of two tabs: Schema element tab and View Editor tab. The Schema Element tab displays information on the selected element of the schema in the left frame. The information contains the name of the element, a description and specifies whether:

(1) the element is mandatory for lexical entries of the lexicon,

(2) multiples of this element are allowed.

In the View Editor tab you can create various views for your lexicon and the lexical entry display. As explained above, the structure of your new lexicon consists now only of two data containers and one data category. However, it will need to be extended according to the requirements of your lexicon. To add new elements, select e.g. Form and click on the icon below the left frame under the Lexicon Structure. A pop up window, New Schema Element, will appear in which you will be able to specify whether you wish to create a data container or data category. Mark data category and add a name and a description. After having done it, click OK. A new data category item will be created under Form (Figure 2.3).

New schema element pop up

Figure 2.3. New schema element pop up


In the same way you can create data containers in your lexicon. Following the simple folder - file analogy, it is possible to create data containers under other data containers (just like a simple folder-subfolder structure), but it is not allowed to create data categories under other data categories.

To modify an existing item in the structure, select the element in the lexicon structure, and see the Schema Element tab in the right frame. You can modify all the previously added information (i.e. Name, Description, Admin Info (i.e. any administrative info you might want to add) and whether the element should be mandatory or/and allow multiples). Moreover, you can also select a sort order for that given element and write a note. However, in LEXUS the application of the sort order for the structural elements should be done at the very end of the lexicon creation (see Section 1.3).

In case of data categories, you may decide to change from the user-defined type to the predefined data categories: either the Toolbox MDF categoriesor the ISO 12620 registry (ISOcat). For further information about ISOcat see the ISO Data Category Registry website. While changing to a Toolbox-defined data category is useful in those cases where you need maximum interoperability between the newly created lexicon and lexica in your workspace which were imported from the Toolbox application, changing to ISO 12620 data categories enhances interoperability and standardizes your lexicon to a wider accepted conceptual format.

[Note] Note

ISOcat is no longer being developed. Despite the option being present in the application, ISOcat is no longer in use in LEXUS. If you choose to swtich from user-defined to predefined data categories, please use Toolbox MDF instead.

(1) To change to Toolbox MDF categories, select a data category element in the lexicon structure in the left frame. In the right frame, under Registry click Toolbox MDF. Select the Toolbox data category from the list. Note that the description field will fill with information on the Toolbox element.

Toolbox data category selection

Figure 2.4. Toolbox data category selection


(2) To change to an ISO 12620 element, select a data category element in the lexicon structure in the left frame. In the right frame, under Type click 'ISO12620'. Fill in the name of the data category in the search box, select in which repositories you want to search and select one of the elements from the search results (see Figure 2.5). In this example we replace the user created data category by the ISOcat data category 'word'. A description of the data category is given in the search result list. For more detailed information on the data category a link to the ISOcat web site is given under the magnifier glass right of the search results.

[Note] Note

ISOcat is no longer being developed. Despite the option being present in the application, ISOcat can no longer be used in LEXUS. If you choose to switch from user-defined to predefined data categories, please use Toolbox MDF instead.

ISOcat data category selection

Figure 2.5. ISOcat data category selection