Folksonomy Engine

The goal of Folksonomy engine is to unleash an ocean of new usages regarding food knowledge. Folksonomy engine allows all kind of people — citizens, researchers, journalists, professionals, artists, communities, innovators... — to enrich and use Open Food Facts, thanks to free tags and properties of their own, for their own use or to enrich the shared knowledge. Open Food Facts, as the biggest open-food database in the world, already feeds hundreds of data reuses. It will allow thousands of new apps and new usages.

Documentation and communication

Detailed presentation (4 pages)
Project document. (This current document.)

Other directories/documents (if any)

Main directory for documentation

Slack channel: #folksonomy_engine

Who

Skills needed (in short)

Project management
Dev

Project team:

Project owner: ?
End-user tester: ?
Dev: Stéphane
Others?

How

Needed deliverables.

Deliverable	Date	Who
D1. Ideation document: uses cases (report in wiki page)	Feb.	XX
D2. Functional and technical specifications (architecture design) (report in wiki page)	Feb.	XX Stéphane (Review)
D3. Server-side implementation (database and web UI): properties’ database implementation and CRUD interfaces with a minimal UI to validate the design: database implementation (new database or new fields) CRUD interfaces in the backend (Product Opener) web interfaces (in production)	April	Stéphane (dev) XX (tests)
D4. Search and discovery integration and APIs. Making properties accessible using simple search and a discovery engine; integration with the advanced search; API access all dev in the backend	May	Stéphane (dev) XX (tests)
D5. Mobile UI integration on the Open Food Facts apps	June	XX
D6. Two uses cases: move ambiguous “Nutriscore Experiment” labels in tags XXXX (to be found)	Sep.	XX

Wishful deliverables

Here we put wishful deliverables if any.

Questions/ideas

What about a deliverable dedicated to communication?
Use case in collaboration with scientists?