-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
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
searchvalues not returning study Names #54
Comments
In order to replace the manual JavaScript - based approach to searching for Studies, I can use Key-Value pairs to search for studies using the search engine (see IDR/idr-gallery#20) but I still have to use a 'manual' approach or different endpoints for searching for Name and Description. It would be really nice if "Name" and "Description" were considered to be Key/Value pairs on the objects for the purposes of |
I have modified the names endpoint to be able to search both names and descriptions. The user needs to add For example, to search all the studies (screens and projects) which their names or description containing
The current behaviour is maintained if the user does not set It is deployed in |
This is actually working fine for me, but I'm worried this is not going to work so well outside of IDR since it assumes that the Name can be used as a project/screen identifier.
This would also allow us to add other info in future, e.g. group, owner, creation-date etc. |
I also realise that this search really needs to be case insensitive. E.g. https://idr-testing.openmicroscopy.org/searchengine/api/v1/resources/all/names/?value=analysis&use_description=true and https://idr-testing.openmicroscopy.org/searchengine/api/v1/resources/all/names/?value=Analysis&use_description=true should return the same results. |
Trying to find studies by Name or IDR number with:
https://idr-testing.openmicroscopy.org/searchengine/api/v1/resources/all/searchvalues/?value=idr0012&key=Name+(IDR+number)
doesn't return anything. Removing the
key
doesn't help (finds 1 other match but not Name).The text was updated successfully, but these errors were encountered: