Defining Attribute Quality Definition Repository

For each attribute, the AttributeQualityDefinition repository defines the quality of data received from a source. For example, if you have defined the weight of the lastName attribute to 70% received from the SAP source compared with the JDE source which is 80%, then the algorithm within Precedence Management computes the changes made, calculates the new weight based on quality, compares the weight, and decides which value to retain. The weight and decay decide whether the data is stale.

Procedure
1. In TIBCO MDM, click Precedence Management.
   
2. On the Precedence Management page, click the Attribute Quality Definitions tab.
3. Click Create.
   
   
4. In the Quality Details section, enter the required details.
   Note: The following table provides additional information that is useful when filling the fields. This is not an exhaustive list of all fields.

   Field Name	Description
   Weightage	The range for weight can be 1 - 100.
   Decay Type	Select anyone of the following options: None Linear: Select when quality declines linearly over a set time. Half Life: If selected, the quality never becomes zero.
   Decay Period	Define the range with positive integers. Valid range values: 1-999
   Decay UOM	Select the unit of measurement for the decay period. It can be Hour, Day, Month, or Year.
   Note: The Decay Period and Decay UOM fields are enabled only if you have selected the value in the Decay Type list.
   Ignore if null	Define how to handle empty, or NULL attributes in the dataset associated with the precedence set. If this value is set, the following result occurs: Yes: If the new value of an attribute in this dataset is NULL, then the old value is retained irrespective of weight No: If the old value of an attribute in this dataset is NULL, then the new value is retained irrespective of weight Note: When applying precedence, if the existing multivalue attribute has more weightage than the new multivalue attribute, the new value is ignored. Additionally, the weightage is applied to all values of multivalue attributes.
   Ignore this attribute always?	Select Yes to ignore any value coming from a new source. This option is useful to quickly drop some data from the incoming feed. Default value: No
   Associated Change Date	Enter the change date along with the timestamp. The change date value is useful when the change date of incoming data is other than the current date. Consider that the weight of both ORCL and SAP sources is 90. A record, record1 comes from the ORCL source and is updated on 2021-09-28 3:14:07. The same record1 comes from the SAP source on 2021-09-29. However, the value of the Associated Change Date attribute in this record is 2021-08-14 3:14:07. In this scenario, when the precedence is applied, the ORCL data is retained because the value of Associated Change Date of the SAP source is older than the ORCL source. Note: The value of Associated Change Date attribute is considered only when the new-computed weight equals the old-computed weight.

5. In the Source References section, you can enter new records or existing records from the RecordSource repository. See Defining Source.
   
6. Click Validate, and then Save.
   Records are validated and then saved in the AttributeQualityDefinition repository.