DM-29735, the minimal thing that we specifically require ASAP is:
- One ~2-sentence description of the entire collection of DP0.1-DC2 catalog tables. This will be attached to the dp01_dc2_catalogs "schema" on the TAP service.
- For each of the five tables, one ~2-sentence description of what is in that table, enough to make it clear to a user with minimal additional knowledge what these tables are good for.
- A recommended order in which the five tables should be presented, and especially which one should come first, and therefore be selected by default in the TAP UI.
Melissa Graham, can you work with your CET colleagues to get this to us really soon? It's the last essential missing piece toward getting the data deployed. I'm going to say, COB Monday 4/19?
There's more apple-polishing that could be done, but I think Leanne Guy has decided to call a halt on further tuning at least for now, until we can see these data on the deployment.
- mentioned in
Adding it to the dp01_dc2_catalogs schema is a good idea. We'll also add it to the data product documentation.
I'm merging this and will use this file to generate a TAP schema PR (
The file has the table descriptions as Melissa Graham provided on the ticket and did not incorporate the newer comments such as adding version clarifications. If we want those it can be done in a new PR.
This ticket was literally just about handing the text over to us (RSP) for deployment. So it's done!
We documented it in rtn-001.lsst.io Sect 2.1.2 though that's not really user-facing.
The v2 only applies to object & truth_match tables. The other 3 tables are v1-equivalent (no v2 available in DESC as far as I know); those 3 aren't in the public release either.