Availability and Accessability |
Currency |
Reliability and Credibility |
Usability and Interpretability |
Uniqueness
Compare with other Characteristic
Characteristic Name: | Uniqueness |
Definition: | The data is uniquely identifiable |
Dimension: | Consistency |
Granularity: | Record |
Characteristic Type: | Declarative |
Implementation Form: | Rule-based approach |
Verification Metric:
The number of duplicate records reported per thousand records |
Validation Metric:
To what extent required rules have been identified and implemented to maintain the declarative characteristic in concern. |
BackgroundGuidelines
The original definitions given below formed the basis of the consolidated definition of the characteristic.
Definition: | Source: |
---|---|
The entity is unique — there are no duplicate values. | B. BYRNE, J. K., D. MCCARTY, G. SAUTER, H. SMITH, P WORCESTER 2008. The information perspective of SOA design Part 6:The value of applying the data quality analysis pattern in SOA. IBM corporation. More from this source |
Asserting uniqueness of the entities within a data set implies that no entity exists more than once within the data set and that there is a key that can be used to uniquely access each entity. For example, in a master product table, each product must appear once and be assigned a unique identifier that represents that product across the client applications. | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. More from this source |
Each real-world phenomenon is either represented by at most one identifiable data unit or by multiple but consistent identifiable units or by multiple identifiable units whose inconsistencies are resolved within an acceptable time frame. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. More from this source |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
Guidelines: | Scenario: |
---|---|
Ensure that every entity(record) is unique by implementing a key in every relation | (1) Key constraint |
Ensure that same entity is not recorded twice under different unique identifiers | (1) Same customer is entered under different customer ID |
Ensure that unique key is not-null at any cost | (1) Employee ID which is the key of employee table is not null at any cost |
In case of using bar codes standardise the bar code generation process to ensure that Bar codes are not reused | (1) UPC |
Availability and Accessability |
Currency |
Reliability and Credibility |
Usability and Interpretability |
Leave a Reply
Be the First to Comment!
You must be logged in to post a comment.