Backend changes required to add tags

[duncanpeacock]

This is still under discussion but is likely to involve a new API/backend tables.

HLD
Initial code drop

[duncanpeacock]

HLD issued: https://docs.google.com/document/d/16-DbiLiy7CjK2JyDkehQC3OT5caR_mzJ7szlEb_gWQs/edit#

Potential tickets when finalised are as follows:

Ticket | Contents | Estimate

• Tags-01 | Initial functionality as described in this document. | Around 5 days.
• Tags-02 | Additional molecule/session-project API functionality - to add tag-type/author/user as needed (another 6 APIs). | Around 1 day.
• Tags-03 | Discourse Integration. Further analysis based on Discourse use/requirements. | small/medium (depending on requirements)
• Tags-04 | Replacement of Molgroup functionality. Once the Frontend has changed to use tags, it may be possible to simplify the backend to remove the MolGroup model functionality. Use of scoring functionality in Frontend to be investigated. | small/medium
• Tags-05 | Searches across targets. This adds complexity as it affects authorisation. | medium
• Tags-06 | Autocomplete searches. This is a wider question than just tags as it’s a strategic decision for Fragalysis. A suitable library must be chosen and database changes scoped out. Further analysis required. | medium/large

[duncanpeacock]

Backend code drop for Tags-01 now completed.