Meta Data Configurations

Identifying the correct Mapping for any given business case becomes more difficult as the number of your mappings grows. To make this task easier, you can use Meta Data Configurations. Imagine, for example, that Meta Data Configurations correspond to the following sticky note scenario.

  • If you could attach sticky notes to each project, you could write on each note, exactly the bits of information you require to match the Mapping to a business case. These bits of information would fit into patterns, each becoming something like a template.
  • With Meta Data Configurations, you can define what kinds of information should be in the template (what you wrote on the sticky notes). Within the Mapping Project, the Meta Data Configuration is displayed as an input mask. It would be like adding a template to the sticky notes with input fields, list boxes, and so on. So continuing with this scenario, if you were a Mapping developer, you would enter the text (the actual Meta Data) into a configuration, like the text what you wrote on the sticky notes.
  • It is exactly this information (Mapping + Meta Data + input data) that allows you to identify the mapping to which the sticky note (the Meta Data Configuration) is attached. You can view and edit the contents defined in the Meta Data Configuration within the Mapping Project itself.

You can apply a Meta Data Configuration to any number of Mapping Projects, Mappings, and if using DML, to Document Identifiers. You can have more than one configuration, each serving a specific purpose. By having different configurations you could, for example, divide your mapping projects, assigning configuration A to all mappings linked to supplier A and configuration B to all mappings linked to supplier B.

Configuration type

A Project Meta Data Configuration can have different types:

  • Internal configurations
  • The configuration type Internal is saved in your local preferences store in your workspace. You can export these configurations to share them. For internal configurations, you do not have to define a location.

In addition, the following types allow the storing of configurations in the file system:

  • External configurations
  • External configurations allow you to refer to a configuration outside your workspace. For external configurations, you must enter or select the path to the configuration file, when creating the configuration.
  • Remote configurations
  • Remote configurations allow you to refer to a configuration outside your workspace using HTTP or HTTPS. When creating the configuration for remote configurations, you must enter or select the URL to the configuration file.
  • Built-in configuration
  • A built-in configuration is shipped with your installation as a template for creating your own specific configurations. This configuration is read-only, but you can copy and then edit the copy.

Categories - entries

Each Meta Data Configuration is structured into categories, which in turn, contain entries. You can define different entry types. An entry can be a:

  • Text box
  • List box
  • Combo box from which pre-defined values may selected
  • Check box
  • Many other entry types

You can specify if entries have a default value and whether they are mandatory.

Note An error is produced if there are Mapping Projects, with an assigned Meta Data Configuration that contain mandatory fields that are not filled.

Related topics

Meta Data

Meta Data Configurations

Define Meta Data Configurations

Assign Meta Data Configurations

Manage Meta Data Configurations

Edit Meta Data Configurations

Export Meta Data Configurations

Version Management and Project Meta Data

Related Links