Add simple input for missing tags

[teolemon]

Why

• Some users complain about not being able to add the info like before
• Make the most use of the tag picker #1075 is not here yet

What

• Add a new editing section with simplistic input for all missing tags "Advanced editing"
• This would be a screen with text fields, populated like in V1 by existing values, with a chip input system, with autocompletion
• Categories
• Origins of ingredients Implement simplified origin input #2501
• Packaging Introduce basic (tag based) packaging editing #2355
• Manufacturing places
• EMB Codes/traceability codes
• Labels
• Countries
• Stores

Screenshots from V1

[monsieurtanuki]

@teolemon Regarding autocompletion, we're a bit stuck because of openfoodfacts/openfoodfacts-dart#465
How did you guys do with the android or ios app, in order to go beyond the 25 item limit?

[teolemon]

@monsieurtanuki We never noticed it, and did a query with every key stroke, after the nth first keystrokes

[teolemon]

https://github.com/openfoodfacts/openfoodfacts-androidapp/blob/a51c675ee127db12178b4014bc8dd763371f6e88/app/src/main/java/openfoodfacts/github/scrachx/openfood/network/services/ProductsAPI.kt#L109

[monsieurtanuki]

Then you're lucky and I'm not. We're both using the same cgi/suggest.pl with the same parameters.

• what if you type just 'a': do you see all the categories that contain 'a'?
• what if you type 'soja' (in French): how many "Boissons végétales de soja" do you see?

[teolemon]

[teolemon]

aah @monsieurtanuki I believe we use local taxonomies in V1 for those, actually…

[teolemon]

We only use autosuggest for 2 specific fields (packager codes). Local taxonomies allow for local editing, but they are very heavy

[monsieurtanuki]

@teolemon What shall we do then?

[teolemon]

I would move ahead without waiting for a server fix, the server fix will only make it work better once it's ready.
I'll raise the issue during the Product Opener meeting tonight with @stephanegigandet and @alexgarel

[teolemon]

User can input whatever they wish actually. Suggestions are just for convenience, and we do server side parsing and taxonomization over time

[monsieurtanuki]

Ok then.

[monsieurtanuki]

This will be something like that:

[teolemon]

Labels and Stores are merged. How about Categories ?

[monsieurtanuki]

Ok for categories. Working on it.

[monsieurtanuki]

@teolemon I can work on "Packaging", but the following fields do not exist in off-dart products AFAIK:

• Origins of ingredients
• Manufacturing places
• EMB Codes
• Countries

[teolemon]

Packaging is the next logical target.
Origins of ingredients is actually just origins

[teolemon]

Let's file the relevant issues against openfoodfacts-dart

[monsieurtanuki]

To be honest I'm a bit lost regarding "packaging", because of the discrepancies between TEST and PROD on 5010477348630.

PROD:

{
  "code": "5010477348630",
  "product": {
    "packaging": "Etui en carton,Sac en plastique à jeter,Sachet en plastique,Étui en carton à recycler",
    "packaging_tags": ["fr:etui-en-carton", "fr:sac-en-plastique-a-jeter", "fr:sachet-en-plastique", "fr:etui-en-carton-a-recycler"]
  },
  "status": 1,
  "status_verbose": "product found"
}

TEST:

{
  "code": "5010477348630",
  "product": {
    "packaging": "fr:sac en plastique à jeter,fr:étui en carton à recycler,fr:Etui en carton,fr:Sachet en plastique",
    "packaging_tags": ["fr-sac-en-plastique-a-jeter", "fr-etui-en-carton-a-recycler", "fr-etui-en-carton", "fr-sachet-en-plastique"]
  },
  "status": 1,
  "status_verbose": "product found"
}

[teolemon]

We also have https://world.openfoodfacts.org/api/v2/product/5010477348630?fields=packaging_text_fr which behaves like the ingredients field (multilingual, OCR-compatible)

And it's hairy

"packaging":"Etui en carton,Sac en plastique à jeter,Sachet en plastique,Étui en carton à recycler","packaging_hierarchy":["fr:Etui en carton","fr:Sac en plastique à jeter","fr:Sachet en plastique","fr:Étui en carton à recycler"],

"packaging_lc":"fr",

"packaging_old":"fr:sac en plastique à jeter,fr:étui en carton à recycler,fr:Etui en carton,fr:Sachet en plastique",

"packaging_tags":["fr:etui-en-carton","fr:sac-en-plastique-a-jeter","fr:sachet-en-plastique","fr:etui-en-carton-a-recycler"],

"packaging_text":"",

"packaging_text_fr":"",

"packagings":[{"material":"en:cardboard","recycling":"en:recycle","shape":"en:sleeve"},{"material":"en:plastic","recycling":"en:discard","shape":"en:bag"}]

[monsieurtanuki]

@teolemon Is there any piece of code on the server that could help us understand how we are supposed to read and write packaging?

[stephanegigandet]

Hi @monsieurtanuki , there's no good way to write packaging data currently (the existing packaging tag is deprecated), so I suggest that we wait until we do have a right way and a corresponding API to do it.

There's more details about the current state here: https://wiki.openfoodfacts.org/Packagings_data_structure

[teolemon]

@monsieurtanuki we can clone the ingredients extraction system, the current packaging system on the web works exactly the same way

• Reuse the mechanism for ingredients extraction for packagings #1070