You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We parse the origins of ingredients field to store origins of specific ingredients, and then use this info to complement the ingredients extracted from the list of ingredients.
But the matching does not work for ingredients that are not in the taxonomy, as we get ids that are not taxonomized.
…gredients (#7131)
* fix: use normalized ids for untaxonomized ingredients and specific ingredients #7063
* fix issue with specific ingredients
* fix tests
Co-authored-by: Alex Garel <alex@garel.org>
Describe the bug
We parse the origins of ingredients field to store origins of specific ingredients, and then use this info to complement the ingredients extracted from the list of ingredients.
But the matching does not work for ingredients that are not in the taxonomy, as we get ids that are not taxonomized.
e.g.
Needs to be matched to:
To Reproduce
https://world.openfoodfacts.org/cgi/test_ingredients_analysis.pl?ingredients_text=Peaches.+Some+unknown+ingredient%2C+another+unknown+ingredient.%0D%0A%0D%0AOrigin+of+peaches%3A+Spain.+Origin+of+some+unknown+ingredient%3A+France.+origin+of+Another+Unknown+Ingredient%3A+Malta&type=add&action=process&submit=Envoyer
Expected behavior
Match should be insensitive to case and accents.
Screenshots
No response
Additional context
No response
Type of device
Other
Browser version
No response
Number of products impacted
No response
Time per product
No response
The text was updated successfully, but these errors were encountered: