openfoodfacts / smooth-app

🤳🥫 The new Open Food Facts mobile application for Android and iOS, crafted with Flutter and Dart
https://world.openfoodfacts.org/open-food-facts-mobile-app?utm_source=off&utf_medium=web&utm_campaign=github-repo
Apache License 2.0
841 stars 281 forks source link

What else required to calculate Nutri-Score #5121

Closed sineptic closed 6 months ago

sineptic commented 7 months ago

Problem

Screenshot_20240320_121828.jpg app say that some information needed, but not say what I need to add.

Proposed solution

Additional context

Screenshot_20240320_122421.jpg

Screenshot_20240320_122416.jpg

teolemon commented 7 months ago
monsieurtanuki commented 7 months ago

@teolemon Low hanging fruit suggestion: I guess that nutriscore-related nutrients don't change very often, so we could hard-code them and highlight them in the nutrition fact page, possibly with a "needed for nutriscore" subtitle.

monsieurtanuki commented 6 months ago

Several remarks...

Nutrition fields needed for the nutriscore computation

(as interpreted in compute_nutriscore_score_2023 @ Nutriscore.pm)

=> a solution to fix the issue would be to systematically consider those fields as part of the nutrition facts edit screen.

More relevant choice of nutrients to display

For historical (good) reasons, starting from the European version of nutrient hierarchy, we decided to display a specific set of nutrients: all those with "important": true. But we could as well use "display_in_edit_form": true, which is slightly the same. But it's not the same for Russia or Canada: count Europe Russia Canada
display_in_edit_form 11 11 16
important 10 5 4

=> a solution to fix the issue would be to consider "display_in_edit_form": true instead of "important": true:

Unfortunate discrepancies with the website

For some reason

image