984
edits
Changes
Jump to navigation
Jump to search
Line 10:
Line 10: + + + + + + + + + + + + + + + + + + + + Line 21:
Line 41: +
+ product name and common name
=== Fields completed by users ===
=== Fields completed by users ===
[to be completed]
[to be completed]
==== Product name ====
The product name is the main name printed on the packaging. It can be a registered trademark such as Nutella. This data is important and useful as it's one of the most used data.
At the beginning of 2020, more than 95% of Open Food Facts products have a product name:
* [https://world.openfoodfacts.org/state/product-name-completed the ones who have a name]
* and the [https://world.openfoodfacts.org/state/product-name-to-be-completed ones who doesn't]
The product name shouldn't include any other information such as the brand of the product, the weight, etc.
Good examples:
* <code>Nesquick</code> ([https://world.openfoodfacts.org/product/3033710065967/nesquik-poudre-cacaotee-boite-nestle link])
Bad examples:
* <code>Petit déjeuner Nesquick</code> => you don't have to explain, just put the name from the packaging
* <code>Nutella by Ferrero</code> => you shouldn't fill the brand here, there's a field for that :)
==== Common name ====
The common name define the product. It is the name used when you don't want or can't use the product name. This name is very useful for our AI (artificial intelligence): it helps to guess the category of the product.
==== Best before date (expiration date) ====
==== Best before date (expiration date) ====
In the database and in Product Opener software, the technical name for this field is <code>expiration_date</code>.
In the database and in Product Opener software, the technical name for this field is <code>expiration_date</code>.
==== Serving size ====
==== Serving size ====