Difference between revisions of "Ingredients Events list"
Jump to navigation
Jump to search
(Paragraph on questions events answers) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 8: | Line 8: | ||
* What is done after editing it | * What is done after editing it | ||
* in the corner it's the current pipeline from edit to deploy | * 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 | ||
| + | |||
| + | <span data-stringify-type="paragraph-break" class="c-mrkdwn__br" aria-label=""></span>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 == | == The Events == | ||
[[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 | ||
| Line 53: | Line 62: | ||
* Product added | * Product added | ||
[[Category:Ingredients]] | [[Category:Ingredients]] | ||
| − | [[Category: | + | [[Category:Global Taxonomies]] |
Latest revision as of 12:33, 30 November 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
- 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...
- Ingredient added to separate taxonomy
- See impact on ingredient lists
- See how many products affected
- Products ingredients edited
- Processing taxonomy updated
- Track of change recorded
- Manual review of ingredient properties
- See fruit + vegetable content wrong
- Other initiatives needing ingredients
- List of missing ingredients by taxonomy
- See entry with missing translation
- Product added missing ingredient
- Notice data is not in their language
- List of missing translations generated
- Wiki* results
- See ingredient that is not an ingredient
- Matching product not found for ingredient
- List of similar ingredients generated
- See adjacent words
- Entry removed
- Description added
- New entry added
- Add new language
- Added synonym
- Synonyms rearranged (1st = label)
- Property added
- Hierarchy changed
- Entries merged
- Ingredient split
- Global synonym added
- Stopword added
- Product reprocessed
- Bulk of products updated
- Product added
