10
edits
Data quality: Difference between revisions
m
no edit summary
Jayaddison (talk | contribs) mNo edit summary |
Jayaddison (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
* Quality does not make sense for itself: quality depends on usages. | * Quality does not make sense for itself: quality depends on usages. | ||
* We always try to favor ease of use and ease of collection. Data quality control, data verification and data fix should never be an obstacle to data gathering. | * We always try to favor ease of use and ease of collection. Data quality control, data verification and data fix should never be an obstacle to data gathering. | ||
* No database at all can pretend to zero-defect. With more than 2,900,000 products, there are quality concerns. Data quality is done on a "best effort" basis. The effort on data quality includes measuring quality, setting objectives, publishing them and implementing them. | * No database at all can pretend to be zero-defect. With more than 2,900,000 products, there are quality concerns. Data quality is done on a "best effort" basis. The effort on data quality includes measuring quality, setting objectives, publishing them and implementing them. | ||
These principles and our high level objectives are described in the following short document, which you should read at first if you want to go further: | These principles and our high level objectives are described in the following short document, which you should read at first if you want to go further: | ||