User Community Service Desk Downloads
If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Enrichments

For configuring enrichments, you can only use plans.

Plan providers generate a plan with Integration Input and Output steps, where you define the enrichment behavior. Plans can return multiple values so that several attribute values can be suggested in the application along with the one that is currently edited.

To configure enrichments you need to:

  1. Define enrichments.

  2. Configure enrichment plans.

  3. Map enrichments to specific entities and columns.

Define enrichment

You can define enrichments in GUI Configuration on the Enrichments and Autocorrects tab.

Enrichments and Autocorrects tab

To define an enrichment:

  1. Under GUI Configuration > Enrichments and Autocorrects > Enrichments, select Add to add a row. Alternatively, double-click the asterisk (*).

    Adding new row in Enrichments section
  2. Choose the enrichment provider type. Currently, only Plan Enrichment Provider is available.

    Choosing provider type
  3. A new row is now added. Double-click the number of the row and specify the following parameters:

    Enrichment provider plan window
    • Name: Unique name of the enrichment.

    • Label: Technical name that will be used for localization purposes and generated to the mda-label.gen.properties file when set.

    • Enrichment Columns: One or more columns used for the defined enrichment.

      • Name: Column mapping name.

      • Type: Enrichment output data type. Possible values are BOOLEAN, STRING, DAY, DATETIME, FLOAT, INTEGER, LONG.

      • Output: When selected, the column is generated to the Integration Output step and can be replaced by the selected value in MDM Web App. You need to select at least one column.

  4. Confirm your choice by selecting OK. Repeat steps 1-3 for all enrichments needed.

  5. Once the list is complete, confirm by selecting OK on the Enrichments and Autocorrects tab.

  6. Right-click GUI Configuration and select Generate. This updates the nme-enrichments.gen.xml file with the new configuration and generates the plans.

Configure an enrichment plan

After you define an enrichment, you now need to configure an enrichment plan.

To do so:

  1. Under Files > engine > enrichments > enrichment, double-click the name of the plan you defined in the previous step.

    Selecting plan in ONE
  2. Complete the plan by adding steps as needed. For example, a completed address plan might look as follows:

    Enrichment plan example

The Integration Output step has a confidence column predefined. You can specify how the confidence score is calculated by adding an expression while configuring steps.

For example, an expression for calculating confidence for street values might look as follows:

Confidence expression example

Map enrichment to columns

To map the defined enrichment to a specific column:

  1. In the Logical model, select the entity.

    Each enrichment can be mapped only once per entity.
  2. On the GUI Settings tab, select Enrichments and Autocorrects composite element.

    GUI Settings tab
  3. In the tab that opens, under Enrichments, select Add to add a new row. Alternatively, double-click the asterisk (*).

    Adding new row on Enrichments tab
  4. Double-click the number of the row. In the window that opens, specify the following:

    Defining enrichment settings
    • Name: Name of the enrichment. It is prefilled with the name defined in the first step of the enrichment configuration.

    • Enrichment Column Mapping:

      • Enrichment column: Name of the enrichment column.

      • Model column: Name of the model column to which the enrichment is mapped. All enrichment columns need to be mapped to model columns.

      • Clickable: Specifies if the value from this column is displayed in MDM Web App as an enrichment suggestion and can be selected. Only numeric (integer, long, float) and string values can be clickable. At least one column needs to be clickable.

        A column with defined reference data (lookup) cannot be configured as clickable.

Was this page useful?