Folksonomy Engine is not playing well with sister projects
Opened this issue · 3 comments
CharlesNepote commented
What
One has added a memory_size property to product 0194252014912, but this product only exists in Open Products Facts:
- on https://world.openfoodfacts.org/property/memory_size the link is broken
- https://world.openfoodfacts.org/product/0194252014912 does not exist
- https://world.openproductsfacts.org/product/0194252014912 exists but is not linked to any UI related with Folksonomy Engine.
To Reproduce
Expected behavior
We have to discuss the expected behavior:
- should we avoid Folksonomy Engine on sister projects?
- should we launch separated instances of Folksonomy Engine?
- should we make a distinction between different projects inside Folksonomy Engine database?
- ....
Code pointers
You can find some code pointers here. If some are missing, feel free to add them yourself in this file, or to ask them.
- https://github.com/openfoodfacts/openfoodfacts-server/blob/main/templates/web/common/includes/folksonomy_script.tt.html
- https://github.com/openfoodfacts/openfoodfacts-server/blob/main/html/js/folksonomy.js
Part of
teolemon commented
github-actions commented
This issue is stale because it has been open 90 days with no activity.
teolemon commented
- "on https://world.openfoodfacts.org/property/memory_size the link is broken" >> we could add a "This property is not used on Open Food Facts, you may try Open Pet Food Facts, Open Beauty Facts or Open Products Facts"
- "https://world.openfoodfacts.org/product/0194252014912 does not exist" >> "0194252014912 does not exist, you can add it using the Open Food Facts mobile app (with a QR-Code), or if you came from a Folksonomy Engine link, you can try OBF, OPF or OPFF" (Note: I don't understand how you can arrive at this point. Note 2: we could soon solve it even better when we're aware of products on other projects)
- "https://world.openproductsfacts.org/product/0194252014912 exists but is not linked to any UI related with Folksonomy Engine." > (will be solved by deployment to OPF, I guess ?)