You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an enhancement of the endpoint for Use Case 4 described in #601.
Story
As a consumer of the search-api, I want to be able to obtain information on a set of "entities" with values that fall within certain numerical ranges. Examples:
Return data for all datasets from CODEX assays that were performed on tissue samples that were obtained from the small intestines of female donors between the ages of 40 and 60.
List all files from LC-MS assays that have file extension RAW and that have a file size of over 200 MB.
List all antibodies from a particular vendor with catalog numbers in the range X to Y.
Target
Developers of applications that would call the API.
Technical Translation
Return an ElasticSearch query response that can handle numeric ranges.
The endpoint for Use Case 4 returns values that exactly match. This endpoint will need to handle ranges--e.g.,
minimum values (e.g., >=)
maximum values (e.g., <=)
Solution options
Ability to specify ranges in endpoints. This would likely require some custom parsing of parameters, such as discussed here
The text was updated successfully, but these errors were encountered:
AlanSimmons
changed the title
search-api endpoint enhancement: Which "entities" satisfy ranges for numerical criteria?
search-api endpoint enhancement: Which "entities" satisfy *ranges* for numerical criteria?
Jan 6, 2023
Use case 5 of #590
This is an enhancement of the endpoint for Use Case 4 described in #601.
Story
As a consumer of the search-api, I want to be able to obtain information on a set of "entities" with values that fall within certain numerical ranges. Examples:
Target
Developers of applications that would call the API.
Technical Translation
Return an ElasticSearch query response that can handle numeric ranges.
The endpoint for Use Case 4 returns values that exactly match. This endpoint will need to handle ranges--e.g.,
Solution options
Ability to specify ranges in endpoints. This would likely require some custom parsing of parameters, such as discussed here
The text was updated successfully, but these errors were encountered: