Data quality issues which can't be fixed: Difference between revisions

From Open Food Facts wiki
VisualWikitext
mNo edit summary
No edit summary
 
Line 39: Line 39:
'''Github issue''': [to be created?]
'''Github issue''': [to be created?]


=== When the error is wrong ===
=== When the data quality error is a bug from Open Food Facts (product opener) ===
Sometimes the data quality error is a parsing bug.
 
Eg. :  
Eg. :  
* https://world.openfoodfacts.org/cgi/product.pl?type=edit&code=3038354191904#ingredients
* https://world.openfoodfacts.org/cgi/product.pl?type=edit&code=3038354191904#ingredients
Line 46: Line 48:
'''Solution or workaround''': none.
'''Solution or workaround''': none.


'''Action''': the product can be tagged with <code>data_quality:product_opener_issue => yes</code>
'''Action''': the product can be tagged with [[Folksonomy Engine]]: <code>data_quality:product_opener_issue => yes</code>


'''Github issue''': https://github.com/openfoodfacts/openfoodfacts-server/issues/7816
'''Github issue''': https://github.com/openfoodfacts/openfoodfacts-server/issues/7816
Line 79: Line 81:
'''Solution or workaround:''' there is no solution. The producer did not mention that the products contains ingredients that should not be counted to compute the energy. For example, if a product is Stevia and contains 99g/100g of carbs, there should not be counted because stevia is not providing any energy.  
'''Solution or workaround:''' there is no solution. The producer did not mention that the products contains ingredients that should not be counted to compute the energy. For example, if a product is Stevia and contains 99g/100g of carbs, there should not be counted because stevia is not providing any energy.  


'''Action''': the product could be tagged with <code>use data_quality:lack_of_data_to_compute_energy</code> ????  
'''Action''': the product could be tagged with [[Folksonomy Engine]]: <code>use data_quality:lack_of_data_to_compute_energy</code> ????  


'''Github issue''': https://github.com/openfoodfacts/openfoodfacts-server/issues/7789
'''Github issue''': https://github.com/openfoodfacts/openfoodfacts-server/issues/7789
Line 138: Line 140:
===When? Chewing gum or equivalents?===
===When? Chewing gum or equivalents?===


Eg. https://world.openfoodfacts.org/product/26038360
Eg.  
 
[./Https://world.openfoodfacts.org/product/27031247 https://world.openfoodfacts.org/product/27031247]


https://world.openfoodfacts.org/product/4009900517430/extra-professional-white-strawberry-wrigley  
* https://world.openfoodfacts.org/product/26038360
* https://world.openfoodfacts.org/product/27031247
* https://world.openfoodfacts.org/product/4009900517430/extra-professional-white-strawberry-wrigley  


'''Solution or workaround''':  
'''Solution or workaround''':  

Latest revision as of 12:41, 30 November 2023

Issues common to all kind of data quality issues

There is no picture of the nutrition table

Eg. https://world.openfoodfacts.org/product/8480000325242/aroma-de-vainilla-hacendado

Solution or workaround: no workaround. Don't copy data from other sources. Our data should be based on our photos.

Action:

  • erase all nutrition facts' values.
  • remove nutrition facts' picture if it is not correct.

Github issue: -

The picture of the nutrition table is lacking data

Solution or workaround: no workaround. Don't try to put data if there are not displayed on the packaging.

Action: put a hyphen (-) where the data are missing.

Github issue: -

en:nutrition-value-over-105-fruits-vegetables-nuts-estimate-from-ingredients

When the package contains more than one product

When the package contains more than one product, each product can have its own list of ingredients. Then fruits and vegetables estimated value from ingredient goes over 105.

Eg.:

Solution or workaround: none.

Action: the products can be tagged with ingredient_list:multiple.

Github issue: [to be created?]

When the data quality error is a bug from Open Food Facts (product opener)

Sometimes the data quality error is a parsing bug.

Eg. :

Solution or workaround: none.

Action: the product can be tagged with Folksonomy Engine: data_quality:product_opener_issue => yes

Github issue: https://github.com/openfoodfacts/openfoodfacts-server/issues/7816

en:nutrition-value-total-over-105

When the product density is greater than the water

When the product density is greater than the water and the weight displayed for 100ml, the total of the ingredients can be greater than 105.

Eg.:

https://world.openfoodfacts.org/product/20271343/sirop-d-agave-bio-sonne

https://world.openfoodfacts.org/product/7501088011375

Solution or workaround: [to be discussed]

Action: the products can be tagged with nutrition_facts:per_ml

Github issue: [to be created?]

en:energy-value-in-kj-does-not-match-value-computed-from-other-nutrients & en:energy-value-in-kcal-does-not-match-value-computed-from-other-nutrients

When? Sugar or equivalents?

Eg.:

Solution or workaround: there is no solution. The producer did not mention that the products contains ingredients that should not be counted to compute the energy. For example, if a product is Stevia and contains 99g/100g of carbs, there should not be counted because stevia is not providing any energy.

Action: the product could be tagged with Folksonomy Engine: use data_quality:lack_of_data_to_compute_energy ????

Github issue: https://github.com/openfoodfacts/openfoodfacts-server/issues/7789

When? Soup or equivalents?

Eg.:

Solution or workaround:

Action:

Github issue:

When? Tea or equivalents?

Eg. https://world.openfoodfacts.org/product/4056489024354

Solution or workaround:

Action:

Github issue:

When? Lemon juices?

It seems that many lemon juices are reporting errors: more than 225 as of 2022-12-15, which is nearly half of all the lemon juices (577).

Eg.

Solution or workaround:

Action:

Github issue:

When? Vinegar or equivalents?

It seems that many vinagers are reporting errors: more than 608 as of 2022-12-15, which is nearly 20% of all the vinegars (3528).

Eg. https://world.openfoodfacts.org/product/3182384011012

Solution or workaround:

Action:

Github issue:

When? Chewing gum or equivalents?

Eg.

Solution or workaround:

Action:

Github issue:

When?

Eg.

Solution or workaround:

Action:

Github issue:

en:energy-value-in-kcal-does-not-match-value-in-kj

When energy values are low (1-10 Kcal)

When energy values are low, there are often matching issues between the energy in Kcal and KJ. This often because producers are rounding the values.

Eg.

Solution or workaround: use the values per serving if the serving is higher than 100g/100ml.

Action: -

Github issue: energy-value-in-kcal-does-not-match-value-in-kj: false positive for low values

When?

Error maybe?

Eg.

Solution or workaround: ?

Action: -

Github issue: energy-value-in-kcal-does-not-match-value-in-kj: false positive for low values


en:energy-value-in-kcal-does-not-match-value-computed-from-other-nutrients

When it is a beer?

Eg.

Solution or workaround: delete?

Action: -

Github issue:

Retrieved from "https://test-wiki.openfoodfacts.org/index.php?title=Data_quality_issues_which_can%27t_be_fixed&oldid=20161"