Line 18: |
Line 18: |
| * Ability to reuse the data for products in a easy to edit wiki | | * Ability to reuse the data for products in a easy to edit wiki |
| * Vitality of the codebase | | * Vitality of the codebase |
− | * Vitality of the ecosystem | + | * Vitality of the ecosystem (Gamification apps, Bot ecosystem) |
| * System to enable gamification exist for wikidata | | * System to enable gamification exist for wikidata |
| * Ability to have a product be composed of two other products | | * Ability to have a product be composed of two other products |
Line 26: |
Line 26: |
| * Need to code a beautiful frontend to visualize the data | | * Need to code a beautiful frontend to visualize the data |
| * Need to code a friendlier frontend to edit the data | | * Need to code a friendlier frontend to edit the data |
− | * faire un OFF par dessus un wikibase c'est un très gros boulot pour arrivée à la parité fonctionnelle comme tu dis | + | * Lot of work to rebuild an OFF on top of Wikibase (feature parity with current OFF) |
− | * il y a un risque pour que qq chose qu'on veut faire ne soit pas modélisable dans wikibase | + | |
− | * il y a un risque pour qu'au niveau performance ça ne tienne pas la route pour le genre de requêtes qu'on fait sur OFF (par exemple toute la navigation par facettes) | + | ==Risks== |
| + | |
| + | * Can wikibase support everything we want to model in the Open Food Facts database? |
| + | * Can wikibase support the type of queries done on Open Food Facts with enough performance? |
| + | ** e.g. Open Food Facts is a very heavy user of tag queries for its navigation by facets, that need to return results instantly |
| + | *** (/tagtype1/tag1/tagtype2 -> list of all tag2s for products that have tag1) |
| + | *** (/tagtype1/tag1/tagtype2/tag2 -> list of all products that have tag1 and tag2) |
| + | *** queries to build maps, graphs. |
| | | |
| == Wikibase Install Guide == | | == Wikibase Install Guide == |