[[File:Ingredients editing Event storm Sticky wall at OFF days 2023.jpg|thumb|right|Event storm sticky wall at OFF-days 2023]]
[[File:Ingredients editing Event storm Sticky wall at OFF days 2023.jpg|thumb|right|Event storm sticky wall at OFF-days 2023]]
* Deployed to production
* [[File:Ingredients Event Storm - processed.jpg|thumb|All the events as post-its (processed version)]]Deployed to production
* Merged
* Merged
* Change reviewed
* Change reviewed
Revision as of 15:54, 31 October 2023
Events for Ingredients taxonomy
The list below is the result of an Event Driven Design (?j session around the ingredients taxonomy. This took place on 22 October 2023 during the OFF-days. No attempt to order these have been done.
On the wall we, more or less grouped by events answering different questions:
Why editing taxonomy
What is done to edit
What is done after editing it
in the corner it's the current pipeline from edit to deploy
and a summary:
There are 3 reasons to edit taxonomy:
Complete information (add translation, link to other data base)
Refine or reorganize categories (can imply to split a category, or to change its parent)
Complete the taxonomy: ingredients that does not exist yet in it
The main pain-point identified was to see how products get impacted, because you need to merge the modification and reprocess products with a script before seeing the modification (which means a deployment and a reprocessing).
The Events
Event storm sticky wall at OFF-days 2023
All the events as post-its (processed version)Deployed to production
Merged
Change reviewed
Change checked
Changed pushed to Github
See how many products have properties
Related taxonomy updated, e.g. additive, allergen, mineral...
