Support for addition of synonyms and stopwords in frontend

[aadarsh-ram]

The frontend currently allows only addition of nodes of type "ENTRY".

Addition of stopwords and synonyms through the frontend must be also supported, by changing the dropdown menu items in search/SearchResults.jsx and allentries/index.jsx.

The POST request for addition must be sent to the appropriate endpoint (/nodes) in the backend.

[vedant-z]

Hey @aadarsh-ram I figured out that I need to add support for stopwords and synonyms in this part of code <option value={'entry'}>Entry</option> in search/SearchResults.jsx and allentries/index.jsx .

I need some help on what keywords should I add in option value or what needs to be done other than that?

Also in the backend part I need to make changes in backend/entries.py right?

[aadarsh-ram]

Hey @vedant-z. Sorry for the late reply :(

You're right about the changes in frontend part, options have to be added. The frontend currently has a function to send a POST request to add an entry which is handled by handleAddNode(). But, synonyms/stopwords need a separate handler function to POST the ID as the string synonym or stopword and the main_language to the same endpoint (newNode variable is not required for addition of synonyms and stopwords).

The backend part (entries.py) requires a lot of work to include this change, since many functions have to be changed, namely create_node(). The create_node() function needs to be changed to include the suffix number by looking up the last stopword/synonym (Eg: stopwords:1 where 1 is the suffix number).

Another function needs to be written to add this newly created node in the position next to the last stopwords/synonyms node in the Neo4j database. (The current add_node_to_beginning() function cannot be used, because order is important here).

If you'd like to work on this issue, you'd require understanding of the way in which a taxonomy is parsed and stored in the database. As a start, I'd suggest you to read this reference document for the parsing process and test out the application in dev using the instructions given here.

Sorry for the long comment, but hopefully this covers everything that needs to be changed in order to bring support for this. Feel free to ask any doubts!

[aadarsh-ram]

@alexgarel Feel free to include anything that I might have missed :)

[alexgarel]

@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 edited and we don't really seek a large number of contributors on this (this is specialist work as it may have a large impact with lot of possible pitfalls).

[alexgarel]

We decided to avoid displaying synonyms and stopwords (for now) in the UI.

So once, again, this issue is a really low priority issue.