Date
Attendees
Discussion items
Web Data Access Service API
- versions - should we have "current" version?
- break results into pages or not? Large default?
- should image types be part of URI?
- ids. "/image/123" vs "/image?id=123". What if returning multiple images?
- metadata for columns returned by "GET /db/v0/query"
- how about "GET /db/v0/query/explain"? It could return estimated query time, # chunks involved etc.
- how about "GET /db/v0/query/explain"? It could return estimated query time, # chunks involved etc.
- async requests?
- how about "GET /db/v0/query?type=async"?, It could return "queryId=<uniqueQueryId>, location=<url of the result>"
- GET /db/v0/query/status?queryId=<qId? to get status of async query
Terminology
- dataset / repo etc
In IPAC archives, dataset always refers to a collection of data.
For WISE, each data release is a dataset: like preliminary release, allsky release, AllWISE release, ...
For Spitzer, each legacy or exploration team produce a set of data, they are re leased with each team name or the program name
Sometimes a dataset includes both catalogs and images; sometimes only catalogs or images in a dataset.
Inside a dataset, they are further separated into smaller units, sometimes by type (catlog, image, spectrum).
Images can be further separated by level of data products (level1-single frame image, leve2-coadded image), and by wavelength (wise has 4 bands).
For each image, there are also ancillary data associated with it, like artifacts, uncertainty, coverage, PSF file, mask, ...
- organization of data will affect the REST API when specifying resource. What's repo definition?