951
edits
Data fields: Difference between revisions
Best before date (expiry date) initial documentation
(+ database name of "serving_size") |
(Best before date (expiry date) initial documentation) |
||
| Line 9: | Line 9: | ||
=== Fields completed by users === | === Fields completed by users === | ||
[to be | [to be completed] | ||
==== Best before date (expiration date) ==== | |||
The expiration date is a way to track product changes over time and to identify the most recent version. It's a data for manual usages. At this moment (2020-03), Open Food Facts apps and website don't make any usage of this field. An issue is open to [https://github.com/openfoodfacts/openfoodfacts-server/issues/76 throw off very old products in averages], it could be useful for it. | |||
Be aware that, for the moment, this field is NOT normalized, so it probably contains dates in various formats that can be ambiguous (31/12/2019, 12/31/2019, 13 mai 2018, etc.). | |||
It is possible to see: | |||
* [https://world.openfoodfacts.org/state/expiration-date-completed how many products do have an expiration date] (a bit more than 10% at the beginning of 2020) | |||
* and [https://world.openfoodfacts.org/state/expiration-date-to-be-completed how many don't] | |||
In the database and in Product Opener software, the technical name for this field is <code>expiration_date</code>. | |||
==== Serving size ==== | ==== Serving size ==== | ||