Line 11: |
Line 11: |
| | | |
| === Product name === | | === 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. | + | 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. |
| | | |
− | If it's not a part of the name, it shouldn't contain the number of portions or a quantity: bad examples are "1 Onglet", "10 Burgers", "1L Sirop cerise"; "100% Cacao", "1848 Lait noisette" (name of a product); it shouldn't contain registered trademark symbols ®, HTML code such as <code>&quot;</code>; it shouldn't be in capital letters except if they are used on the product; it shouldn't contain brands except if it's included in the name ("Kinder Bueno" is good while "Kronembourg 1664", "Stella" or "Vodka Smirnoff" are not); it shouldn't contain price. | + | If it's not a part of the name, it shouldn't contain the number of portions or a quantity: bad examples are "1 Onglet", "10 Burgers", "1L Sirop cerise"; "100% Cacao"; it shouldn't contain registered trademark symbols ®, HTML code such as <code>&quot;</code>; it shouldn't be in capital letters except if they are used on the product; it shouldn't contain brands except if it's included in the name ("Kinder Bueno" is good while "Kronembourg 1664", "Stella" or "Vodka Smirnoff" are not); it shouldn't contain price. |
| | | |
| At the beginning of 2020, more than 95% of Open Food Facts products have a product name: | | At the beginning of 2020, more than 95% of Open Food Facts products have a product name: |
Line 25: |
Line 25: |
| ==== Good examples ==== | | ==== Good examples ==== |
| * <code>Nesquick</code> ([https://world.openfoodfacts.org/product/3033710065967/nesquik-poudre-cacaotee-boite-nestle link]) | | * <code>Nesquick</code> ([https://world.openfoodfacts.org/product/3033710065967/nesquik-poudre-cacaotee-boite-nestle link]) |
| + | * <code>111 Filini</code> ([https://world.openfoodfacts.org/product/8008845071119/111-filini-maltagliati link]) |
| + | * <code>Yazoo strawberry</code> ([https://world.openfoodfacts.org/product/5410438044845/yazoo-strawberry link]) => in this example, "strawberry" has a lower font size than "Yazoo" but the flavour here distinguishes between other products, so we can consider it is part of the name |
| | | |
| ==== Bad examples ==== | | ==== Bad examples ==== |
− | * <code>Petit déjeuner Nesquick</code> => you don't have to explain, just put the name from the packaging | + | * <code><u>Petit déjeuner</u> 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 :) | + | * <code>Nutella <u>by Ferrero</u></code> => you shouldn't fill the brand here, there's a field for that :) |
− | * <code>Nesquick®</code> => Don't use symbols ®, ™, © or similar in product name data field or even in other fields. | + | * <code>Nesquick<u>®</u></code> => Don't use symbols ®, ™, © or similar in product name data field or even in other fields. |
| | | |
| === Common name === | | === Common name === |
Line 101: |
Line 103: |
| | | |
| === Labels === | | === Labels === |
| + | Here we put any characteristic of the product which is factual and different from the other fields: organic, vegetarian, religious, etc. |
| + | |
| + | Provenance: many contributors add the origins here: eg, <code>Made in Belgium</code>, <code>Produced in Brittany</code>, ... |
| + | |
| + | Religious labels: namely halal and kosher labels. |
| + | |
| + | Rating labels when they are displayed on the product (even if it's not the same as we compute): Nutri-Score (6+ European countries), Five Start Rating system (Australia, New-Zealand), etc. |
| + | |
| [to be completed] | | [to be completed] |
| | | |
Line 140: |
Line 150: |
| Open Food Facts gathered [https://world.openfoodfacts.org/packager-codes 25,000+ codes] as of 2021-08-18. These codes allow to localize the places on a map: https://world.openfoodfacts.org/packager-code/fr-72-264-002-ce | | Open Food Facts gathered [https://world.openfoodfacts.org/packager-codes 25,000+ codes] as of 2021-08-18. These codes allow to localize the places on a map: https://world.openfoodfacts.org/packager-code/fr-72-264-002-ce |
| | | |
− | We use it to produce the world map of products: https://cestemballepresdechezvous.fr/ (fr) and https://madenear.me/ (en) [down on 2021-08-19]. | + | We use it to produce the world map of products: https://cestemballepresdechezvous.fr/ (fr) and https://madenear.me/ (en). |
| | | |
| === Best before date (expiration date) === | | === Best before date (expiration date) === |
Line 198: |
Line 208: |
| See [https://github.com/openfoodfacts/openfoodfacts-server/issues?q=is%3Aissue+is%3Aopen+traces+label%3Aallergens issues related to <code>allergens_tags</code>]. | | See [https://github.com/openfoodfacts/openfoodfacts-server/issues?q=is%3Aissue+is%3Aopen+traces+label%3Aallergens issues related to <code>allergens_tags</code>]. |
| === Traces === | | === Traces === |
− | The traces are ingredients which are not used for the product itself but lay in the factory or the production process: the product might contains traces of these ingredients. Traces are really important if you are allergic. | + | The traces are ingredients which are not used for the product itself but lay in the factory or the production process: the product might contain traces of these ingredients. Traces are really important if you are allergic. |
| | | |
| This field can be filled by hand, but is also completed by automatic ingredients analysis. | | This field can be filled by hand, but is also completed by automatic ingredients analysis. |
Line 260: |
Line 270: |
| | | |
| '''Answer:''' yes | | '''Answer:''' yes |
| + | |
| + | '''Question''': what do I enter when the label says something like "contains trace amounts of ..."? |
| + | |
| + | '''Answer''': you can enter the word "traces" as the value, and the system recognizes this as "approximately zero". |
| | | |
| === Missing value === | | === Missing value === |
− | When th nutrition facts table is missing some values, enter the "-" (hyphen symbol) for that field. For example the '''''Fiber''''' value is sometime missing. | + | When the nutrition facts table is missing some values, enter the "-" (hyphen symbol) for that field. For example the '''''Fiber''''' value is sometime missing. |
| + | |
| + | == Photos and data check == |
| + | At the end of the page, there is a specific section called "Photos and data check", documented as follow: |
| + | |
| + | "Product pages can be marked as checked by experienced contributors who verify that the most recent photos are selected and cropped, and that all the product data that can be inferred from the product photos has been filled and is correct." |
| + | |
| + | When <code>[x] Photos and data checked</code> is checked, Product Opener save the following data into the database: |
| + | |
| + | * the value <code>on</code> in the field <code>checked</code> |
| + | * the last checked date (Unix timestamp format) into <code>last_checked_t</code>. Eg. <code>last_checked_t: 1704906819</code>. |
| + | * the last user who checked the product into <code>last_checker</code>. Eg. <code>last_checker: benbenben</code>. |
| + | * the users who have checked the products are stored in the field <code>checkers_tags</code>. Eg. <code>checkers_tags: ["benbenben","stephane"]</code>. |
| + | |
| + | When <code>[x] I checked the photos and data again</code> is checked, Product Opener update the following data: |
| + | |
| + | * the last checked date (Unix timestamp format) into <code>last_checked_t</code>. |
| + | * the last user who checked the product into <code>last_checker</code>. |
| + | * the users who have checked the products are stored in the field <code>checkers_tags</code>. |
| + | |
| + | |
| + | When a product is checked, this information is given on the product page, in the '''Data sources''' section, eg. "Last check of product page on January 10, 2024, 6:13:39 PM CET by charlesnepote". |
| + | |
| + | These data can also be retrived via the API. |
| + | |
| + | It's possible to explore the checked products with the dropdown menu "Explore products by...", selecting "Last checked dates", leading to the page: https://world.openfoodfacts.org/last-check-dates |
| + | |
| + | It's possible to combine facets, for example, to get last checked dates of the TOP-1000 products in a country, eg. https://world.openfoodfacts.net/popularity/top-1000-fr-scans-2022/last-check-dates |