Standardization function with two standardization roles

Some standardization functions, such as BXNM, support two standardization roles.

The InfoSphere® MDM Workbench Algorithm tab of the Configuration Editor detects the multiple standardization roles by checking the stdtype2 field for the standardization function definition in the engine-metatadata.xml file in the project. If stdtype2 is set to non-NULL, the secondary standardization role property is displayed in the Properties tab. If two standardization roles are supported by the standardization function, the connection from the standardization function to a comparison role or query role have a property named “Standardization role” displayed in the Properties tab when the connection is selected. The Standardization role property is not visible for those connections where the standardization function has stdtype2 set to NULL (or an empty string). This is the only case in the editor in which the connection between two algorithm components has a settable property.

For example, select the Provider algorithm and then select the BXNM standardization function. In the Properties view, the secondary standardization role is added as a property because BXNM supports two standardization roles. If the secondary standardization role is used (meaning, the standardization function has two connections), this property must be set to a non-zero value.

Select the connector between BXNM and one of its comparison roles (or query roles):

Standardization role

requires selection of either Primary standardization role or Secondary standardization role.

A standardization function which supports two stdRoles can be connected to any combination of one or two comparison or query roles. If it has two connections, one connection must have its Standardization role property set to “stdRole1” and the other must be set to “stdRole2”. If the standardization function is connected to only one comparison role or query role (for example, the second Standardization role is not used), the connection Standardization role property must be set to “stdRole1”. Validation rules verify the proper assignment of stdRole1 and stdRole2 when the standardization function supports two roles.

Minimum weight frequency

defines the minimum number of attribute values required in order to be included in the mpi_strfreq table generated by the Generate Frequency Stats job (mpxfreq utility). For example, if "Minimum weight frequency" is 10, only values that occur 10 or more times are listed in the table. In general, the larger the attribute population, the larger this value should be. This property is available for several connections.

Record status filter

defines whether only active (A) or both active and inactive (AI) data elements are used (required). This property is available for several connections.