Could someone familiar with F-Droid package / add the app there?
The app code is on github: https://github.com/openfoodfacts/openfoodfacts-android
In fact if you highlight barley, then Gluten will be added in the list of allergens.
Here is an example: http://world.openfoodfacts.org/product/5053947059803/orkney-crab-pate-tesco-finest
We have a list of ingredients containing gluten:
en:gluten, wheat, rye, barley, oats, spelt, kamut
In the ingredients list, we try to enter exactly what is written on the package.
Then on our side we can try to some matching for things like allergens. I'm not familiar with malt flavouring. Is it written on the package that this one comes from barley?
Otherwise we could have a "May contain gluten" label applied when there is just "malt" (and no "gluten-free" label).
At this time we don't have a good system for that kind of products. What we are doing is listing all those "special" products on the wiki so that when can look at all those examples to design a solution that works well for as many cases as possible: http://en.wiki.openfoodfacts.org/Noteworthy_Products
We have a "packaging" field where we have put some of this information, but at this time it's a free form field. It would indeed be good to structure it a bit.
We are now recognizing the UK * EC codes. See http://madenear.me.uk for a use of those codes!
Thanks a lot for the information!
So at this point, you can add a packer code in any format you want. Even if the format is not recognized, it will still be indexed, so you will be able to see all the products from the same packer.
There are two more things I do for the French packer codes:
1. normalization: e.g. emb 64304 a is the same as E64304A.
2. identifying the city and also indexing the city so that we can find all products from a city even if they are from different manufacturers.
So what I would suggest is to add all the codes that are on packages. And then we can list them, see what they look like, and try to do extra things like finding the actual name of the company, or its location etc. using publicly available APIs / databases if they exist. (and if they don't exist, we could try to create them)
There is a field for EMB / packaging codes. Here is the list of the ones we have so far:
We use it also for http://cestemballepresdechezvous.fr
Is this request about making this field more proeminent? One thing we could do is to add it to the few fields that can be entered through the mobile app.
So we have the uservoice forum http://openfoodfacts.uservoice.com/ where I have moved your question. :-)
It's supposed to be for Ideas, but we can use it for Questions / Issues as well. I added all your questions on it, with (question) at the end of the title.
I'm also open to try and/or create other channels. For the French version, we use a Facebook group a lot for keeping ourselves updated about news. But it's not very good for deep discussion as it's quite difficult to find old discussions. We also have a mailing list, but it is not very active. And there is a blog with comments: http://fr.blog.openfoodfacts.org
What I can do is to create a blog and a mailing list for English too (and possibly other languages as well if there are several motivated contributors)
2 very good questions for which I do not know what is the best answer yet.
For products that are available only in some countries, the best way to solve that would be to find a way to list the countries where they are available. Then we could let users decide if they want to see all products in Spanish, or only products that are widely available in Spain or Argentina.
The issue then becomes: how do we know in which countries a product is available? We could try to crowdsource it. If we create an iphone / android app that is widely used, then we could check where the scans for a product are coming from.
Or we could try to connect with some online stores to see if they sell the product or not.
Or maybe there are other ways. Any ideas ?
For the reverse question (products that are available in multiple languages), at this point they should be only listed in the language that is the most visible on the product. (but it may be that some brands translate the packaging while still using the same barcode...)
One thing I was thinking to do is to someday automatically translate the product information (the ingredients mostly). Then this question becomes the same as the first one: if we know in which countries a product is sold, then we can show it to the right users.
I was going to suggest to use the more formal way, but then I checked Wikipedia, and they are using the "tu" form:
So for Spanish, I can think of 2 different ways to create the categories:
1. same approach as French. I create a file to describe the Spanish hiearchy of categories on Google Docs, and little by little people can create the hierarchy.
2. we think of a more global approach, where we have an international hierarchy of categories, the same for every language and country, with category names translated in multiple languages.
Maybe we could start with 1, and then later add translations and possibly unify the categories.
I started a file for the Spanish categories:
For the French version, we intentionaly started with a chaotic approach to categories: everybody was welcomed to put whatever they wanted in the categories field of each product. The idea was to see what kind of categories people put intuitively.
And then we started to put some order to the chaos, in a very incremental way, by starting to normalize the categories names (e.g. we decided to put all of them in the plural form: "Cakes" instead of "Cake") and by creating a sort of hierarchy of categories. ("Orange juices" being a sub-category of "Fruit juices", itself a sub-category of "Drinks" etc.)
So now we ask people to put only the most specific product category they can think of. e.g. "Pineapple juices from concentrate". And all the parents categories are added automatically.
The parents categories can be added retroactively, so it does not matter if the "Pineapple juices from concentrate" category does not exist yet.
The approach is different than the wikipedia way: instead of reviewing the products and moving them to more specific categories sometime later, we start with the most specific category, and then we review the hierarchy of categories to add the new categories that are not in the hierarchy yet.
The "hierarchy" is not strictly speaking a hierarchy: categories can have multiple parents. e.g. "Pineapple juices from concentrate" is a child of both "Pineapple juices" and "Fruit juices from concentrate".
For French, the "hierarchy" of categories is created collaboratively with this file:
And I use the file to create a graphical view:
This is a very interesting suggestion. One one hand I’m trying to keep the product form as simple as possible, so that products can be added as quickly and effortlessly as possible. And on the other hand, more information is better.
Maybe we could try to offer an alternate representation of the list of ingredients, in a table as you suggest. The table view would be constructed from the plain text data, and contributors could add extra information like origin, whether the ingredient is organic, from fair trade etc. or not.
It’s not as easy as it sounds though, as sometimes the ingredients list contain sub-ingredients etc. so the table might not always work.
Sorry for my very late reply, I didn't see it when you posted it last month.
That's a very good idea. It may be difficult to implement though: if the label does not mention how an additive was made, then it could be difficult to guess (unless there is only one way to create it). I read that a lot of them can be extracted from natural sources, or can be obtained by chemical synthesis. I also read some can be produced by genetically modified bacterias.
If the information is available, we could try to list the different sources, and which ones are the most common.
What do you think?
That’s a good idea. I started a file some time ago to list the hierarchy of brands and companies:
I’m guessing the file can be international. We may get a few conflicts here and there (different brands with the same name) but hopefully we’ll find a way to solve them.