Loading managed attribute values (MVals)

This topic describes how to implement a graph to load values for a managed attribute.

Recommended practice is to load managed value attributes after loading standard attributes and managed attributes (PDRs and DDRs). If you add managed attribute values for an attribute that has not already been defined in the data domain, the managed attribute is created with system default values for the DDR and, if necessary, for the PDR.

Use the Add Managed Values component to add managed values to a managed attribute. An instance of the Add Managed Values component can only add managed values to one managed attribute. Adding values to multiple managed attributes requires multiple instances of the component, either in the same graph or in different graphs.

Managed attribute value input file

The input schema of the managed attribute input file is predefined. The first row is the header row and must define the following properties: 
spec|displayname|parent|synonym
where:
  • spec is a unique string identifier for the managed value. This ID is used to associate child values with parent values.
  • displayname is the name displayed in the user interface for the managed value.
  • parent is the parent ID for this managed value. If the value is a root value (in other words, if the value has no parent, but only children), enter a forward slash (/) for this property. If the value is a child managed value, enter the unique ID of the parent managed value.
  • synonym optionally defines one or more synonyms for the managed value. When you add a synonym to a managed attribute value, the value will be returned when users search on the synonym. You can add synonyms to both root and child managed values. You can add multiple synonyms to a single managed value. Specify the delimiter for multiple synonyms on the Edit Add Managed Values dialog.

The following graphic illustrates a simple managed attribute input file:

Simple example of a managed attribute input file

This example defines several parent categories, including CAT_BIKES and CAT_COMPONENTS. The following values are defined as children of the CAT_BIKES value:

and these values are defined as children of the CAT_COMPONENTS value:
  • Handlebars
  • Bottom Brackets
  • Brakes
  • Chains

The input file is typically stored in the data-in directory of the project.

Managed attribute value input graph

A basic managed attribute value input graph consists of two components:

  • A Universal Data Reader

    Specify the location of the input file (typically the data-in directory of the project) in the File URL field.

  • An Add Managed Values component

The two components are joined by a basic edge. See Connecting two components with an edge. The following graphic illustrates a typical configuration:

Typical load managed attribute values graph