Line 8: |
Line 8: |
| ** Bilingual products | | ** Bilingual products |
| *** Products where all the texts on the label are in two (or more) languages | | *** Products where all the texts on the label are in two (or more) languages |
− | *** Common in bilingual countries (Belgium, Canada...) | + | *** Common in bilingual countries (Belgium, Canada, Luxembourg, ...) |
| *** e.g. most Cora products have all the text in French and in Dutch: http://world.openfoodfacts.org/brand/cora | | *** e.g. most Cora products have all the text in French and in Dutch: http://world.openfoodfacts.org/brand/cora |
| * Products with some information in multiple languages | | * Products with some information in multiple languages |
Line 99: |
Line 99: |
| ==== Taxonomize all or most multilingual tag fields ==== | | ==== Taxonomize all or most multilingual tag fields ==== |
| | | |
− | * Packaging, origins of ingredients and purchase places are tag fields (they contain comma separated values) that are not yet taxonomized | + | * Packaging, origins of ingredients and purchase places are tag fields (they contain comma separated values) that are not yet taxonomized. (Origin of ingredients is a two part tag: ingredient+origin. How to keep them apart? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET)) |
− | * The existing taxonomy system will take care of the mapping between different languages | + | * The existing taxonomy system will take care of the mapping between different languages (country and language specific labels? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET)) |
| * The taxonomies need to be created or completed | | * The taxonomies need to be created or completed |
| * To be determined: what to do with brands? | | * To be determined: what to do with brands? |
Line 106: |
Line 106: |
| *** But exceptions exist | | *** But exceptions exist |
| ** Could benefit from being taxonomized in order to have a hierarchy | | ** Could benefit from being taxonomized in order to have a hierarchy |
− | | + | ** An Hierarchy could also help to normalize brands, i.e. remove errors --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:05, 15 November 2015 (CET) |
| | | |
| ==== Selection/crop of images in more than one language ==== | | ==== Selection/crop of images in more than one language ==== |
Line 121: |
Line 121: |
| * Create new fields suffixed by _lang, with a hash | | * Create new fields suffixed by _lang, with a hash |
| ** "ingredients_text_lang":{"en":"Chocolate, milk", "fr":"Chocolat, lait"} | | ** "ingredients_text_lang":{"en":"Chocolate, milk", "fr":"Chocolat, lait"} |
| + | ** So multiple languages can be found in the same field. --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET) |
| * Create new languages field | | * Create new languages field |
| ** Hash that contains languages for which we have values for at least one field | | ** Hash that contains languages for which we have values for at least one field |
| ** "languages":{"en":"1", "fr":"1"} | | ** "languages":{"en":"1", "fr":"1"} |
| + | ** What is the purpose of this field? --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET) |
| + | Could there be conflicts between the ingredients_text qnd ingredients_text_lang fields? And how should these be resolved? |
| + | Could the number of hashes in *_lang fields be different? Also different in content (i.e. "it" and "en" in one field and "fr" and "nl" in another field) |
| + | --[[User:Aleene|Aleene]] ([[User talk:Aleene|talk]]) 19:18, 15 November 2015 (CET) |