Dataphin:Standard adherence assessment

Background information

After you create a data standard, apply it by associating it with asset objects. Dataphin defines the mapping between standard properties and asset metadata fields. This mapping is a prerequisite for adherence monitoring. For more information, see Create and manage standard adherence mapping rules.

Lost bid monitoring

Adherence monitoring checks whether mapped objects comply with the associated data standards. It includes metadata monitoring and content quality monitoring:

• Metadata monitoring assesses whether the field metadata of an asset object is consistent with the property values defined in the data standard.

• Content quality monitoring assesses whether the content of a mapped asset object, such as a field or metric, complies with the data standard's constraints, such as value range and uniqueness.

  Note

  Content quality monitoring requires the quality monitoring feature. To use this feature, you must purchase the asset quality module.

Metadata monitoring

To configure metadata monitoring, specify the field metadata to monitor and its corresponding data standard property, then configure the validation logic, such as rules for value equality and case sensitivity. If a value cannot be retrieved from the data source for the specified field metadata, the adherence assessment cannot be performed.

For example, the "member registration channel" data standard requires the "data type" to be STRING. If the mapped field "registration_channel" has a data type of INT in the database, it does not comply with the standard, and the monitoring check fails.

Dataphin provides built-in public system properties for common metadata monitoring. When you create a data standard set, you can reference these properties. Data standards in the set inherit the monitoring configurations from system properties by default. For more information, see Create and manage public properties for data standard sets.

Content quality monitoring

You can add content quality monitoring to asset objects in two ways:

• The monitoring rule is linked to a data standard's property value, and the rule configuration is derived from that value. For example, when monitoring a field's range, the rule's range comes from the standard's "range" property. With this method, the Rule configuration is automatically generated, and you only need to define the Validation configuration.

• The monitoring rule is independent of the data standard. However, if a rule configuration is added when the standard is created, all mapped asset objects can reference the pre-configured rule for rapid batch configuration. With this method, both the Rule configuration and Validation configuration are defined manually. For more information, see Step 2: Configure quality rules.