Data quality: Difference between revisions
(Initial page) |
(No difference)
|
Revision as of 15:02, 31 March 2020
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 1 200 000 products, there are quality concerns: our goal is to lower the impacts of the issues.
Data quality: how to help?
Nutri-Score quality
Some products now have Nutri-Score printed on the front of pack. Some differs from our Nutri-Score calculation. We should take care about that:
- Nutri-Score printed A but calculated E
- Nutri-Score printed A but calculated D
- Nutri-Score printed A but calculated C
- Nutri-Score printed E but calculated A
- Nutri-Score printed E but calculated B
- Nutri-Score printed E but calculated C
- Nutri-Score printed D but calculated A
- Nutri-Score printed D but calculated B
- Nutri-Score printed D but calculated C
- Nutri-Score printed B but calculated E
- Nutri-Score printed B but calculated D
- Nutri-Score printed B but calculated C
There are many reasons why it can differ:
- the label in Open Food Facts does not represent the label printed on the package (easy to solve)
- the label is correct but our calculation doesn't provide the same result:
- check the category,
- then check the nutrition facts: the issue is sometimes the lack of "fibers" information or the lack of "Fruits, vegetables, nuts and rapeseed, walnut and olive oils" percentage.
- it can be a software issue (quite rare but possible)