# Create metadata form

Please note

When configuring metadata forms, the number of forms used should not reach double-digits.

A separate search index is built for each metadata form. A large number of metadata forms therefore requires a large amount of RAM and hard disk space for the ELO iSearch.

This applies for first generation and second generation metadata forms.

'Add metadata form' button

  1. Click the Add metadata form button (green plus icon).

The New metadata form dialog box opens.

  1. Enter a name for the metadata form in the Name field.

'New metadata form' dialog box

  1. Enter all other information for the metadata form in the New metadata form dialog box.

Information

Read the following information for notes on the corresponding fields and options.

  1. Click Save to save the metadata form.

# Basic data

Basic data

Name: Enter the name of the metadata form here.

Translation variable: This field is where you define a variable that can be used for customizing the program with scripts or for translations, e.g. the name of the metadata form.

Last change: In this field, you can see when the metadata form was modified last.

ID: Identification number of the metadata form. This is automatically assigned by the system.

GUID: This field contains the GUID of the metadata form, which is allocated by the system.

Save data as a table: Select the Save data as a table function if you do not want to save the data of the entries filed with this metadata form in the usual database structure (objkeys table). The entries are saved to a flat database table instead. This database table has one column per index value and one row per document. This may be required in specific cases to optimize search performance.

Important

You cannot convert data back to the usual database structure. Check carefully if this setting is necessary in your case. You will find more information under ELO server - Installation and operation > Optimization > ELO metadata table (opens new window).

# Use

'Usage' area

Folders: If you enable this option, the metadata form can be used to enter metadata for folders.

Documents: If you enable this option, the metadata form can be used to file documents.

Search: Select this option to use the metadata form for searches.

Relation: If this option is enabled, you can establish a link between the metadata form and Relation type fields. With Relation type fields, you can only select metadata forms in which this option is enabled.

Example of a relation field

Relation fields establish a connection to the corresponding relational metadata forms. Relation fields can be used to display the priority fields of the associated metadata form as a keyword list. You can recognize relation fields by the chain icon.

Information

Double-click to transfer an entry from the keyword list to the field. Only the short name is copied into the field. You can sort the keyword list using the columns.

# Restriction

Usage determined by parent element: If the option Usage determined by parent element is enabled, then this metadata form is only available if you file or create a child entry in a folder that is restricted to this metadata form.

See the option Restrict selection of metadata forms for child entries.

Restrict selection of metadata forms for child entries: Enter which metadata forms may be used for the child entries here.

Enter the metadata form you want to use in the Enter name of metadata form field. ELO suggests possible metadata forms as you type.

Click a suggestion to add the respective metadata form to the list. To remove the metadata form from the list, select the X icon to the right.

# Dashboards

Dashboards (gen. 2) can also be created for metadata forms (gen. 1).

Go to dashboard designer: Select this link to create dashboard views for metadata forms (gen. 1).

The individual steps are described in the following.

# Create a dashboard

Dashboards belong to views. So, first you have to create a view. Note the following steps for creating a dashboard.

  1. Open the Go to dashboard designer link.

    'Form designer' page

    The Form designer page opens in a separate tab.

  2. Select the plus icon.

    'Create view' dialog box

    The Create view dialog box opens.

  3. Enter a technical name in the Identifier field.

    Information

    Only capital letters (without umlauts and special characters), numbers, and underscores are allowed. The first character must be a letter.

  4. Enter a display name in the Display name field.

    Optional: If you want to offer translated texts, you can select/create a translation variable. You will find more information under ELO packages > Other topics > Translations > Use translation variables (opens new window).

  5. The form designer (gen. 2) opens.

    On the Charts tab, you can choose between the following chart types:

    • Bar chart
    • Line chart
    • Doughnut chart
  6. Drag a chart type to the layout area using drag-and-drop.

    Properties of the charts

  7. Under Properties, you can configure the chart.

    The following configurations are possible:

    • Component: You can change the selected chart type at a later point.
    • Alignment: In a bar chart, for example, you can select whether you want to arrange the bars vertically or horizontally.
    • Breakdown by field: The chart is based on a field with aspect mapping from the metadata form. Select a previously created field for the chart in the drop-down menu. Additional settings are available depending on the field type selected.
    • Metric: Different metric selections are available depending on the field type. While Count is especially suitable for field types such as keyword lists or text, use Average, Minimum, Maximum, Total for numeric field types.
    • Filter: Select the plus icon to add a field with aspect mapping as a filter.
    • Color palette: Select a color scheme for the chart.
    • Mapping type: You can assign colors by selecting the pencil icon next to the Mapping type field. You will find more information in the following Configure mapping section.
    • Title translation key: The field name is applied by default. If needed, select a different translation variable for the title of the dashboard.
    • Title: Select a title for the dashboard. Otherwise, the field's technical name is shown.
    • Subheader localization key: Select a translation variable for the dashboard subheader as needed.
    • Subheader: Select a subheader for the dashboard as needed. This can help users better understand the purpose of the chart.
    • Size: Select a size for the chart. This determines how the chart is arranged on the dashboard relative to other charts. The way the charts are arranged adapts to the size of the screen.
  8. Repeat these two steps until you have placed all the desired charts.

  9. Select Save.

The dashboard is saved and is now available.

  1. To close the form designer, close the corresponding tab.

Information

For fields with the assigned localization key field there are two optional methods:

  • Available translation variable: Select one of the available translation variables from the drop-down menu. The Name field is completed automatically.
  • Manual entry: Enter a new translation variable manually. Enter a name in the Name field. The data is saved automatically.

# Configure mapping

For color palettes, you can assign specific colors data values. This makes sense for multi-color color palettes.

Example of assigning colors according to minimum and maximum values

  1. Select the pencil icon beside the Mapping type field.

  2. Select a mapping type.

    • Minimum and maximum value: Assign the minimum value a different color than the maximum value.
    • Threshold: Define a threshold. All values below the threshold are assigned a different color than the values above the threshold.
    • Rule-based: Define one or more rules as to which color should be assigned to which value/value range.
  3. Select Apply.

The mapping type is saved.

For more information on how to create dashboards, refer to ELO packages > Metadata > Metadata forms > 'Content' tab > Create dashboards (opens new window)

Last updated: June 17, 2024 at 2:07 PM