Precision
Characteristic Name: | Precision |
Dimension: | Accuracy |
Description: | Attribute values should be accurate as per linguistics and granularity |
Granularity: | Element |
Implementation Type: | Rule-based approach |
Characteristic Type: | Declarative |
Verification Metric:
The number of tasks failed or under performed due to lack of data precision |
The number of complaints received due to lack of data precision |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
Guidelines: | Scenario: |
---|---|
Ensure the data values are correct to the right level of detail or granularity | (1) Price to the penny or weight to the nearest tenth of a gram. (2) precision of the values of an attribute according to some general-purpose IS-A ontology such as WordNet |
Ensure that data is legitimate or valid according to some stable reference source like dictionary/thesaurus/code. | (1) Spellings and syntax of a description is correct as per the dictionary/thesaurus/Code (e.g. NYSIIS Code) (2) Address is consistent with global address book |
Ensure that the user interfaces provide the precision required by the task | (1) if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. |
Ensure the data values are lexically, syntactically and semantically correct | (1) “Germany is an African country” (semantically wrong); Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong) |
Validation Metric:
How mature is the creation and implementation of the DQ rules to maintain data precesion |
These are examples of how the characteristic might occur in a database.
Example: | Source: |
---|---|
if v = Jack,even if v = John, v is considered syntactically correct, as Jack is an admissible value in the domain of persons’ names | C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006. |
The Definitions are examples of the characteristic that appear in the sources provided.
Definition: | Source: |
---|---|
Data values are correct to the right level of detail or granularity, such as price to the penny or weight to the nearest tenth of a gram. | ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
Data is correct if it conveys a lexically, syntactically and semantically correct statement – e.g.,the following pieces of information are not correct:“Germany is an African country” (semantically wrong);Book.title: ‘De la Mancha Don Quixote’ (syntactically wrong); UK’s Prime Minister: ‘Toni Blair’ (lexically wrong). | KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published. |
The set S should be sufficiently precise to distinguish among elements in the domain that must be distinguished by users. This dimension makes clear why icons and colors are of limited use when domains are large. But problems can and do arise for the other formats as well, because many formats are not one-to-one functions. For example, if the domain is infinite (the rational numbers, for example), then no string format of finite length can represent all possible values. The trick is to provide the precision to meet user needs. | LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub. |
Is the information to the point, void of unnecessary elements? | LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation. |
The degree of precision of the presentation of an attribute’s value should reasonably match the degree of precision of the value being displayed. The user should be able to see any value the attributer may take and also be able to distinguish different values. | REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc. |
The granularity or precision of the model or content values of an information object according to some general-purpose IS-A ontology such as WordNet. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |
Traceability
Characteristic Name: | Traceability |
Dimension: | Reliability and Credibility |
Description: | The lineage of the data is verifiable |
Granularity: | Record |
Implementation Type: | Process-based approach |
Characteristic Type: | Usage |
Verification Metric:
The number of tasks failed or under performed due to lack of traceability in data |
The number of complaints received due to lack of traceability in data |
GuidelinesExamplesDefinitons
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
Guidelines: | Scenario: |
---|---|
Maintain provenance records for the events such as creation, update,transcription, abstraction, validation and transforming ownership, if the data are dynamic. | (1) Inventory system shows the current stocks and keep records for all the transactions that the stocks are subjected to |
In case of multiple sources are available for same data/information, implement a traceability mechanism to view all versions from multiple sources | (1) Content management systems |
Maintain proper protocols/standards/policy to archive data | (1) Every invoice is archived after 120 days of payments. |
Maintain versions of data records where necessary | (1) Customer versions |
Validation Metric:
How mature is the process to maintain traceability in data |
These are examples of how the characteristic might occur in a database.
Example: | Source: |
---|---|
minutes of a meeting will be produced in draft form and reviewed by the members of the committee before being approved. Once this process of creation is finished the record must be fixed and must not be susceptible to change. If a record is changed or manipulated in some way, it no longer provides evidence of the transaction it originally documented. For example, if someone alters the minutes of a meeting after they have been approved, the minutes can no longer be considered an accurate record of the meeting. This is another issue that becomes more important in an electronic context. | K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007. |
The Definitions are examples of the characteristic that appear in the sources provided.
Definition: | Source: |
---|---|
Is the background of the information visible (author, date etc.)? | EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer. |
A data provanance record can include information about creation, update, transcription, abstraction, validation and transforming ownership of data. | ISO 2012. ISO 8000-2 Data Quality-Part 2-Vocabulary. ISO. |
The extent to which the correctness of information is verifiable or provable in the context of a particular activity. | STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733. |