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 date 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 March 2020 and April 2021.
List all files from LC-MS assays that have file extension RAW that were created after May 2022.
Target
Developers of applications that would call the API.
Technical Translation
Return an ElasticSearch query response that can handle date ranges.
The endpoint for Use Case 4 returns values that exactly match. Use Case 5 handles numeric date ranges. This endpoint will need to handle date ranges--e.g.,
start date
end date
Solution options
Ability to specify date ranges in endpoints.
The text was updated successfully, but these errors were encountered:
AlanSimmons
changed the title
search-api endpoint enhancement: Which "entities" satisfy ranges for date criteria?
search-api endpoint enhancement: Which "entities" satisfy *ranges* for date criteria?
Jan 6, 2023
Use case 6 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 date ranges. Examples:
Target
Developers of applications that would call the API.
Technical Translation
Return an ElasticSearch query response that can handle date ranges.
The endpoint for Use Case 4 returns values that exactly match. Use Case 5 handles numeric date ranges. This endpoint will need to handle date ranges--e.g.,
Solution options
Ability to specify date ranges in endpoints.
The text was updated successfully, but these errors were encountered: