Precedence Management
With Precedence Management, you can ensure that only quality metadata for each attribute is accepted from a data source. You can configure TIBCO MDM such that data is accepted only if the quality of incoming data is better than that of the existing data.
To do this, you must define the quality of each attribute when it is received from a source. With repositories, such data can be easily maintained. During precedence handling, a defined set of repositories captures the quality definition for each source. Precedence Management has an algorithm to compare the quality of incoming data and existing data.
Precedence management requires at least one set of existing data records. The attribute change history (which includes what changed, time of the change, and source details) is used to calculate precedence and to determine the delta of change.
By using the applyPrecedence rulebase action, you can control when the precedence is applied. Ideally, it must be applied as soon as possible, preferably even before storing the data.
Related topics
In the TIBCO MDM Customization guide, the following topics provide more information about the concepts covered here:
- How the Algorithm Works
- Configuration Properties for Attribute History
- How Rulebase is Defined to Measure Absolute Quality
Key Concepts
You must be familiar with the following terms and concepts when handling precedence management:
- Weight is the quantitative measure of the quality of the data.
- Decay is the reduction in the quality of the data over some time. For each attribute, a different decay might apply. For example, linear decay with 6 months means that the data quality declines to 0 after 6 months of receipt of the data.
- Source is the named source of the data provider.
- Half Life is the same as half-life of radioactive materials applied to the quality of the data.
- Change History is the changes to data over some time, along with the source which caused the change.