Precedence Management
With Precedence Management, you can accept quality metadata for each attribute supplied by a source. While accepting data, you can accept data only if the quality of incoming data is better than what is existing.
To implement precedence handling, a defined set of repositories captures the quality definition for each source. You must define what the quality of each attribute is as it is received from a source. When using repositories, you can easily maintain this data.
To support precedence calculation, MDM maintains attribute change history, such as what changed, when it changed, and what was the source. The attribute change history is used to determine the delta of change. Therefore, there must be a previous record to evaluate the attribute change history to manage precedence.
A new rulebase action "applyPrecedence" allows you to decide when the precedence should be applied. Ideally it should be applied as soon as possible, preferably even before storing the data.
- Weight is the quantitative measure of quality of the data.
- Decay is the reduction in quality of the data over a period of time. For each attribute, a different decay may 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 radio active materials applied to the quality of the data.
- Change History is the changes to data over a period of time, along with the source which caused the changed.
The Precedence Metadata project is within TIBCO MDM Studio. If you want to use Precedence Management, you have to deploy the Precedence Metadata from TIBCO MDM studio (on demand). Studio does not handle the resource security, and if you want to restrict the Create, Modify, View, or Delete record actions on the Precedence metadata repositories (RecordSource, AttributeQualityDefinition, PredenceDefinition) for a particular role, it must be done manually.