We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ChRIS_store/store_backend/plugins/models.py
Lines 186 to 244 in e534438
Currently, only a few search queries are supported. By the looks of it, these are
Lines 241 to 244 in e534438
These options are sufficient for most use cases. However there are some fields, such as author, which currently are not searchable.
author
More fields should be searchable, and individually searchable.
It would be a pain to implement the cross-product of fields as specific query-string options e.g. name_title_category. A preferred paradigm would be:
name_title_category
GET /api/v1/plugins/search/?name=fetal&title=fetal&category=fetal
Moreover, it should be possible to define the boolean operations to apply on search terms. Maybe this would look like
GET /api/v1/plugins/search/?q=(title%3D%22fetal%22ORname%3D%22fetal%22)ANDauthor%3D%22fetal%22
An advanced implementation of search queries might use a search engine like ElasticSearch.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ChRIS_store/store_backend/plugins/models.py
Lines 186 to 244 in e534438
Currently, only a few search queries are supported. By the looks of it, these are
ChRIS_store/store_backend/plugins/models.py
Lines 241 to 244 in e534438
These options are sufficient for most use cases. However there are some fields, such as
author
, which currently are not searchable.More fields should be searchable, and individually searchable.
It would be a pain to implement the cross-product of fields as specific query-string options e.g.
name_title_category
. A preferred paradigm would be:Moreover, it should be possible to define the boolean operations to apply on search terms. Maybe this would look like
An advanced implementation of search queries might use a search engine like ElasticSearch.
The text was updated successfully, but these errors were encountered: