Alex Garel

@Anway-Agte you are welcome :-)

@urek696969mazino if @AnshMasand do not react until the end of this week, let's do it. Otherwise there are other issues.

@aapatil2004 this is an old issue which is not up to date, I'm closing it !

@aadarsh-ram, @stephanegigandet @teolemon, I see two main solutions here: * track node changes by properties on the node (eg. create a tags_fr_orig if we modify tags_fr) * track node changes...

Here is a schema of what it looks like after adding a new entry and editing some entries.  draw io source: [taxonomy-orig-neo4j.zip](https://github.com/openfoodfacts/taxonomy-editor/files/9383688/taxonomy-orig-neo4j.zip)

discuss with @aadarsh-ram : if we remove a node this is a bit like the contrary of adding a node: * the original node, is still pointing to previous parents...

@aadarsh-ram we should create a separate issue for backend part. Note that this issue is not a very high priority issue for me as stopword and global synonyms are rarely...

We decided to [avoid displaying synonyms and stopwords](https://github.com/openfoodfacts/taxonomy-editor/issues/173) (for now) in the UI. So once, again, this issue is a really low priority issue.

@aadarsh-ram I believe this is not that the property isn't created, but it's not shown. If you click submit, and reload, the property is here. Can you confirm and change...

IMO, for the stores data, it is a data of interest, even if contrarily to Open Prices, this is not a "sold now" data, so I would keep it, as...