Difference between revisions of "Data quality"
Jump to navigation
Jump to search
(Add section: Data quality issues which can't be fixed) |
(Big refactoring (to be continued)) |
||
| 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. | ||
* No database at all can pretend to zero-default. | * No database at all can pretend to zero-default. | ||
| − | * With more than 2 | + | * With more than 2 700 000 products, there are quality concerns: our goal is to lower the impacts of the issues. |
| − | == Data quality | + | == Data quality principles at Open Food Facts == |
| + | [summary + link] | ||
| − | == | + | == How do we manage data quality? == |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | + | == How to help? == |
| − | + | Anyone can help to improve the data quality. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | === | + | === 1. Adding photos === |
| − | + | Photos allow other contributors to verify and, if necessary, fix the issues. As a contributor, this is the first step to improve data quality. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | === | + | === 2. Fixing a product issue === |
| − | + | As in Wikipedia, anyone can edit at Open Food Facts. If you see an error, don't hesitate to fix it! If you're afraid or hesitating, you can ask your questions on [https://forum.openfoodfacts.org the forum] or in our [https://slack.openfoodfacts.org/ Slack space]. | |
| − | === | + | === 3. Report an issue related to many products or related to data quality === |
| − | + | Sometimes you can discover issues related to many products or related to data quality. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | + | * You can report the issue on [https://forum.openfoodfacts.org the forum] or in our [https://slack.openfoodfacts.org/ Slack space]. |
| − | Some data quality | + | * You can also directly [https://github.com/openfoodfacts/openfoodfacts-server/issues/new/choose report the issue directly on our bug reporting tool]. |
| + | |||
| + | === 4. Help improve data quality with specific missions === | ||
| + | If you want to further, you can check [[Data quality missions|specific missions related to data quality]]. Some missions are fast and easy to achieve. | ||
| + | |||
| + | === 5. Joining the effort to improve data quality === | ||
| + | We organize a public monthly meeting dedicated to data quality. It takes place every first Tuesday of the month at 6pm CET, see [[Events|Open Food Facts' events]] to find the next meetings in our community calendar. | ||
| + | |||
| + | If you have '''technical skills''', you can also do your part for data quality. Head over to [https://github.com/openfoodfacts/openfoodfacts-server/issues/5538 our tracking issue on GitHub] | ||
| + | |||
| + | == Tools == | ||
| + | [to be completed] | ||
| − | == Data quality measurement == | + | === Data quality measurement === |
We have started an initiative to measure and publish continuously some data quality stats. We have created a specific page dedicated to [[data quality stats]]. | We have started an initiative to measure and publish continuously some data quality stats. We have created a specific page dedicated to [[data quality stats]]. | ||
| + | |||
| + | === Quality facets === | ||
| + | [to be described] | ||
| + | |||
| + | === Data quality daily === | ||
| + | [https://mirabelle.openfoodfacts.org/-/data-quality-daily/subscribe Data quality daily] is a daily email suggesting you 3 Open Food Facts products to fix. | ||
| + | |||
| + | * this is ''your'' mission, these 3 products are not sent to other users | ||
| + | * these products should be fixable (photos) | ||
| + | * products' popularity is taken into account (number of scans last year): your fixes have a higher impact | ||
| + | * you also get nice daily stats about data quality, including a contributors' board. | ||
| + | |||
| + | Don't hesitate to [https://mirabelle.openfoodfacts.org/-/data-quality-daily/subscribe register], you can unsubscribe at any time. | ||
| + | |||
| + | === Power User Script === | ||
| + | [https://github.com/openfoodfacts/power-user-script Power User Script] is a user script for your browser, to empower Open Food Facts contribution. It offers many enhancements for contributors, and many features dedicated to data quality. | ||
| + | |||
| + | == Reference / documentation == | ||
| + | |||
| + | === Quality facets === | ||
| + | There are more than 180 data quality facets. You can consult the [[List of data quality errors (generated)|list of data quality errors]]. | ||
| + | |||
| + | === Data quality issues which can't be fixed === | ||
| + | Some data quality issues can't be fixed due to different reasons. See the dedicated page: [[Data quality issues which can't be fixed]]. | ||
[[Category:Quality]] | [[Category:Quality]] | ||
| − | + | [[Category:Data quality]] | |
| − | |||
| − | |||
Revision as of 16:39, 15 February 2023
Some important things to know:
- Quality does not make sense for itself: quality depends on usages.
- No database at all can pretend to zero-default.
- With more than 2 700 000 products, there are quality concerns: our goal is to lower the impacts of the issues.
Data quality principles at Open Food Facts
[summary + link]
How do we manage data quality?
How to help?
Anyone can help to improve the data quality.
1. Adding photos
Photos allow other contributors to verify and, if necessary, fix the issues. As a contributor, this is the first step to improve data quality.
2. Fixing a product issue
As in Wikipedia, anyone can edit at Open Food Facts. If you see an error, don't hesitate to fix it! If you're afraid or hesitating, you can ask your questions on the forum or in our Slack space.
Sometimes you can discover issues related to many products or related to data quality.
- You can report the issue on the forum or in our Slack space.
- You can also directly report the issue directly on our bug reporting tool.
4. Help improve data quality with specific missions
If you want to further, you can check specific missions related to data quality. Some missions are fast and easy to achieve.
5. Joining the effort to improve data quality
We organize a public monthly meeting dedicated to data quality. It takes place every first Tuesday of the month at 6pm CET, see Open Food Facts' events to find the next meetings in our community calendar.
If you have technical skills, you can also do your part for data quality. Head over to our tracking issue on GitHub
Tools
[to be completed]
Data quality measurement
We have started an initiative to measure and publish continuously some data quality stats. We have created a specific page dedicated to data quality stats.
Quality facets
[to be described]
Data quality daily
Data quality daily is a daily email suggesting you 3 Open Food Facts products to fix.
- this is your mission, these 3 products are not sent to other users
- these products should be fixable (photos)
- products' popularity is taken into account (number of scans last year): your fixes have a higher impact
- you also get nice daily stats about data quality, including a contributors' board.
Don't hesitate to register, you can unsubscribe at any time.
Power User Script
Power User Script is a user script for your browser, to empower Open Food Facts contribution. It offers many enhancements for contributors, and many features dedicated to data quality.
Reference / documentation
Quality facets
There are more than 180 data quality facets. You can consult the list of data quality errors.
Data quality issues which can't be fixed
Some data quality issues can't be fixed due to different reasons. See the dedicated page: Data quality issues which can't be fixed.