Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Recognize ingredient + origin (e.g. "lait origine France") in origins field, use it to attribute origin to ingredient #4461

Open
Tracked by #9096
, #5510 ,  #5503 ,  #5520
...
stephanegigandet opened this issue Nov 2, 2020 · 2 comments
Open
Tracked by #9096
, #5510 ,  #5503 ,  #5520
...

Recognize ingredient + origin (e.g. "lait origine France") in origins field, use it to attribute origin to ingredient #4461

stephanegigandet opened this issue Nov 2, 2020 · 2 comments
Labels
🌱 Green-Score https://world.openfoodfacts.org/eco-score-the-environmental-impact-of-food-products 🥗🔍 Ingredients analysis https://wiki.openfoodfacts.org/Ingredients_Extraction_and_Analysis 📍 Origins Origins are used for Eco-Score computation. We want to have structured origins. ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it.

Comments

@stephanegigandet
Copy link
Contributor

stephanegigandet commented Nov 2, 2020 •
edited by teolemon
Loading

What

  • The origins field can contain origins for specific ingredients: "Cocoa from Peru", "Lait origine France" etc.
  • We need to recognize the ingredient + origin combination, store it in a specific way, display it correctly, and also take it into account during ingredient parsing so that we can attribute the proper origin to the ingredient.

Part of
@stephanegigandet stephanegigandet added ✨ Feature Features or enhancements to Open Food Facts server 🥗🔍 Ingredients analysis https://wiki.openfoodfacts.org/Ingredients_Extraction_and_Analysis 🌱 Green-Score https://world.openfoodfacts.org/eco-score-the-environmental-impact-of-food-products 📍 Origins Origins are used for Eco-Score computation. We want to have structured origins. labels Nov 2, 2020
@aleene
Copy link
Contributor

aleene commented Nov 2, 2020

This could also be used for a free format origins field.

@github-actions github-actions bot added the ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it. label Feb 1, 2021
This was referenced Aug 21, 2021
Open
Open
Open
stephanegigandet added a commit that referenced this issue Jul 1, 2022
@stephanegigandet
feat: parse origins of ingredients field #4461
8a3330e
stephanegigandet added a commit that referenced this issue Jul 1, 2022
@stephanegigandet
feat: parse origins of ingredients field #4461
dc95232
stephanegigandet added a commit that referenced this issue Jul 1, 2022
@stephanegigandet
feat: parse origins of ingredients field #4461
5456f5c
@stephanegigandet stephanegigandet mentioned this issue Jul 1, 2022
Merged
stephanegigandet added a commit that referenced this issue Jul 7, 2022
@stephanegigandet
feat: parse origins of ingredients field (#6995)
79fa9ae 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
stephanegigandet added a commit that referenced this issue Jul 12, 2022
@stephanegigandet
refactor: parse origins of ingredients field (#7026)
a2a157f 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* refactor based on PR suggestions

* refactor based on PR suggestions
@manon-corneille
Copy link
Contributor

Hi everyone,
A producer having trouble with this issue got back to me :-) Any idea when this is going to be fix?

Thanks

LandonPattison pushed a commit that referenced this issue Jul 24, 2022
@stephanegigandet @LandonPattison
feat: parse origins of ingredients field (#6995)
6906784 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
LandonPattison pushed a commit that referenced this issue Jul 24, 2022
@stephanegigandet @LandonPattison
feat: parse origins of ingredients field (#6995)
7d605e9 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
LandonPattison pushed a commit that referenced this issue Jul 24, 2022
@stephanegigandet @LandonPattison
refactor: parse origins of ingredients field (#7026)
0bb54ad 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* refactor based on PR suggestions

* refactor based on PR suggestions
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
feat: parse origins of ingredients field (#6995)
c851a6b 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
refactor: parse origins of ingredients field (#7026)
1b39781 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* refactor based on PR suggestions

* refactor based on PR suggestions
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
feat: parse origins of ingredients field (#6995)
d449e76 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
refactor: parse origins of ingredients field (#7026)
c83e7b7 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* refactor based on PR suggestions

* refactor based on PR suggestions
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
feat: parse origins of ingredients field (#6995)
fa2a4e7 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461
LandonPattison pushed a commit that referenced this issue Jul 25, 2022
@stephanegigandet @LandonPattison
refactor: parse origins of ingredients field (#7026)
5d67225 
* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* feat: parse origins of ingredients field #4461

* refactor based on PR suggestions

* refactor based on PR suggestions
@teolemon teolemon mentioned this issue Oct 12, 2022
Open
@teolemon teolemon mentioned this issue Oct 2, 2023
Open
1 task
@teolemon teolemon moved this to To discuss and validate in 🍊 Open Food Facts Server issues Apr 19, 2024
@teolemon teolemon removed the ✨ Feature Features or enhancements to Open Food Facts server label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🌱 Green-Score https://world.openfoodfacts.org/eco-score-the-environmental-impact-of-food-products 🥗🔍 Ingredients analysis https://wiki.openfoodfacts.org/Ingredients_Extraction_and_Analysis 📍 Origins Origins are used for Eco-Score computation. We want to have structured origins. ⏰ Stale This issue hasn't seen activity in a while. You can try documenting more to unblock it.
Projects
Ingredient analysis
Status: To do
🍊 Open Food Facts Server issues
Status: To discuss and validate
Milestone
No milestone
Development

No branches or pull requests
4 participants
@aleene @teolemon @stephanegigandet @manon-corneille