🎯 What can I work on ? (Folksonomy Engine)

[teolemon]

Improve developer experience by creating a continuous loop

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

DevOps

Preview Give feedback

1. Automate the release of the API #33
   github_actions 🎯 P0 📚 Documentation +3
2. Create a dev environment for the Folksonomy Engine #38
   infrastructure 🎯 P1 +2
3. Automate the release to dev
4. Automate the deployment of Folksonomy Engine production #123
   ⭐ top issue infrastructure 🎯 P1 +3
5. Automate the release of the various SDKs generated from API #35
   P2 SDKs github_actions +3

Bugs on Product Opener

Preview Give feedback

1. After changing the value of an existing tag, the website is not updated (although the value is saved) #122
   frontend +1
   

Increase the usage and impact of Folksonomy Engine

Preview Give feedback

1. Deploy the Folksonomy Engine on all Open * Facts projects #62
   0 of 5
   fixed ? infrastructure 🎯 P0 📸 Open Products Facts +4
   
2. Leverage the GS1 schemas to add many relevant properties #52
   P2 📸 Open Products Facts +2

Reliability

Preview Give feedback

1. Transaction handling is buggy - We need a middleware that opens and close transaction on each request. #121
   ⭐ top issue performance 🎯 P0 +3

SDKs & Mobile SDKs

Preview Give feedback

1. Add initial support for the Folksonomy Engine API openfoodfacts-dart#158
   8 of 13
   🎯 P1 📸 Open Products Facts 🔖 Folksonomy engine +3
2. Add support for the Folksonomy Engine in the mobile app (Tracker issue) smooth-app#697
   4 of 13
   Epic folksonomy engine help wanted 🎨 Mockups available 🎯 P1 📸 Open Products Facts +6

Key documentation

Preview Give feedback

1. Harmonize vocabulary #11
   +0
2. Keys discussions, description and documentation #16
   +0

Key discovery

Preview Give feedback

1. Allow to search keys #19
   🔎 Search +1

Adding more constraints

Preview Give feedback

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

Improve API responses

Preview Give feedback

1. If I use the stats API with a non-existent key or value, I get a null back instead of a JSON response #120
   API - Stats P4 +2
2. Streamline and harmonize simple responses across API routes #119
   API P4 +2
3. "Hello" API: the server response is different from the one expected #118
   API P4 +2
4. PUT API response is ambiguous and does not send a ValidationError as expected #117
   API P4 +2
5. Clarify the JSON response if there are no properties #107
   API P4 +2

Authentification

Preview Give feedback

1. Swagger: there is no simple way to authenticate #110
   🔐 API auth 🔐 authentification +2