Having performed a search, we want to allow filtering by a chosen Key. This can be done by adding a AND clause to the search.
But we need to know all the possible values of that Key for the previous search results (otherwise the user may easily pick a value that gives no results in a new search).
I noticed that a search results from /submitquery includes a "bookmark" ID for pagination.
Perhaps this could be used for retrieving all the Values for a given Key from those results.
Ideally the results of this search would be similar to the searchvalues that is currently used to populate auto-complete and includes image counts:
E.g:
GET /searchengine//api/v1/resources/all/searchvalues/bookmark/123/?key=Gene&value=pax
This would then also work if the user hasn't chosen a Key:
GET /searchengine//api/v1/resources/all/searchvalues/bookmark/123/?key=Gene&value=pax
This is similar to the issue #11
Having performed a search, we want to allow filtering by a chosen Key. This can be done by adding a
ANDclause to the search.But we need to know all the possible values of that Key for the previous search results (otherwise the user may easily pick a value that gives no results in a new search).
I noticed that a search results from
/submitqueryincludes a "bookmark" ID for pagination.Perhaps this could be used for retrieving all the Values for a given Key from those results.
Ideally the results of this search would be similar to the
searchvaluesthat is currently used to populate auto-complete and includes image counts:E.g:
GET /searchengine//api/v1/resources/all/searchvalues/bookmark/123/?key=Gene&value=paxThis would then also work if the user hasn't chosen a Key:
GET /searchengine//api/v1/resources/all/searchvalues/bookmark/123/?key=Gene&value=paxThis is similar to the issue #11