ss-1668 New app keywords form field to be used with Invenio records #448
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Jira: https://scilifelab.atlassian.net/browse/SS-1668
This PR introduces changes for the autocomplete functionality of app tags using controlled text. The tags will be used as metadata in the Invenio records when minting an app.
To improve speed, pickled data; optimised for the autocomplete functionality and containing 1000s of entries, was used. The data is assembled separately using a standalone script. This data is loaded to memory on startup instead of being loaded during app creation. An API endpoint is used to query the data when a user starts typing a keyword.
Other changes include removing the current form field for free-text tags and using text from this new field introduced here as value for the attribute in the database. This will then be used during app filtering.
Data sources:
MeSH Medical Subject Headings
EuroSciVoc The European Science Vocabulary
GEMET General Multilingual Environmental Thesaurus
Checklist
If you're unsure about any of the items below, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Further comments
Anything else you think we should know before merging your code!