-
-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quality facet - Nutrition - list products where serving size can't be parsed #3029
Comments
For quantity we have one: https://world.openfoodfacts.org/data-quality/quantity-not-recognized |
Thanks. Reminder for further investigation:
|
Stale issue message |
Is this still needed? Thanks to Mirabelle, now we have such list: |
@benbenben2 I think it's good to have it as a facet however. |
@alexgarel @CharlesNepote @stephanegigandet Whereas for this input: This " Nutrition data per serving - Serving quantity is 0 " facet, has been introduced by @stephanegigandet , before the creation of this current issue. On the other hand, another example: https://world.openfoodfacts.org/product/3322680001236/12-crepes-de-landerneau-le-ster So, this is a little bit misleading because this error is raised when there is actually no serving quantity defined. And there is no error raised when serving quantity is 0. What do you want to do there?
|
We should have 3 different errors I think :)
|
What
Serving size has a specific goal: to let Open Food Facts app make a proportional calculation of each nutrient per serving size -- see: https://en.wiki.openfoodfacts.org/Data_fields
But dozens of "serving_size" values can't be parsed. Examples:
30 gr
,2 liters
,60
,9 candies and 2 biscuits
and son on.We should have a new quality facet to list each product where serving_size (and quantity?) has a value that can't be parsed.
Part of
The text was updated successfully, but these errors were encountered: