Project: datamanagement
Issue DM-1916: Fine-tune data access interfaces
Brought up by Gregory via comments on the API page. Data release selection in queries: I see that the /db/... queries take a "?" query parameter "db" with an example value of "DR1", i.e., a data release selector. A couple of remarks: * Will this query parameter be provided for all the Level 2 image data products, e.g., for retrievals of coadded images? **If so, then it needs an equivalent to the M4 "GET /meta/v0/db/" query. * I assume the "db" query parameter defaults to the most recent data release. * Will the M4 query return an indication of which "?db=" value is the current default? * I assume that the numeric-identifier components of the various paths are unique only within a single data release. That means that eventually, in user documentation, we should make sure that they understand that they can't scan through different releases' versions of the same image (for example) just by varying the "?db=" parameter. * Are the identifiers also unique within a particular type (i.e., "raw", "template", "coadd", "calexp", etc.)? ----- Distinguishing L1 and L2 versions of reprocessed data products Since most or all of the L1 data products will be regenerated in each data release, the catalog and image APIs should presumably allow the user to distinguish between the two. I see how this could be done for catalogs - the "?db=" parameter presumably allows selecting something like "L1" (for the actively updated Level 1 database) in addition to the above-documented "DR1", "DR2", etc. Will the L2 table names for the reprocessed L1 data products be generally expected to be the same as for L1? (Barring the discovery of a serious issue that requires revision of the schema for the reprocessing.) How will the L1 and reprocessed-L1 image data products be distinguished?
Story points: 9