Improve developer experience by creating a continuous loop

Are you a beginner ? You can take a jab at good first issues

DevOps

• Automate the release to dev

Bugs on Product Opener

• After changing the value of an existing tag, the website is not updated (although the value is saved) #122

Increase the usage and impact of Folksonomy Engine

• Deploy the Folksonomy Engine on all Open * Facts projects #62
• Leverage the GS1 schemas to add many relevant properties #52

Reliability

• Transaction handling is buggy - We need a middleware that opens and close transaction on each request. #121

SDKs & Mobile SDKs

• Add initial support for the Folksonomy Engine API openfoodfacts-dart#158
• Folksonomy Engine in the mobile app (Tracker issue) smooth-app#697

Key documentation

• Harmonize vocabulary #11
• Keys discussions, description and documentation #16

Key discovery

• Allow to search keys #19

Adding more constraints

• Proposal: add types as part of property keys (e.g. marketing:contains_toy.boolean = true) #21
• barcode limit: 13 digits or more? #49

Authentification

• Swagger: there is no simple way to authenticate #110

Features to discuss

• UI for Versioning and history tracking of all data changes.
• Support for atomistic revert of changes
• Supports for references for statements (URLs, images…)
• I18n Support for properties (names, documentation…)
• Tools for monitoring data quality and consistency of folksonomy properties and values
• Allow reporting Folksonomy Properties and/or values to Nutri-Patrol
• Tools for importing and aligning data with external sources.
• Support for sameAs relationship, especially with Wikidata properties to avoid reinventing the wheel
• Support for Wikidata imports of Wikidata items (eg 400k books with a barcode)
• Webcomponent-based interface for creating, editing, documenting and managing properties.
• Support for property constraints to ensure data quality.
• Defines specific data types (string, number, date, entity, etc.) properties can be constrained to