Details
Description
RFC-894 proposes to remove the LSST Baseline Schema from the Schema browser and to archive sdm_schemas/yml/baseline.yaml as it is not used in any database. The question remains, what to do with LDM-153 and the DPDD.
The LSST Baseline Schema, rendered in LDM-153, is an aspirational schema that provides a concrete realization that complies with the data products described in the DPDD. It was used by science pipelines to guide early development and to produce the sizing model but is no longer up to date with the actual production data model and no longer necessary for the sizing model. Keeping this aspirational schema up to date is a lot of work and provides diminishing return on investment. We hence propose to freeze and archive baseline schema and LDM-153. LDM-153 is still informative as a historical document, but should no longer be used and we should not refer people to it.
The DPDD is in essence a policy statement aimed at the community that describes what LSST data products they can expect. The tables in the DPDD describe conceptual schemas for the data products, i.e what we will deliver but not the implementation details. These tables are useful and we propose to keep these in the DPDD. To make the DPDD conceptual schemas easier to manage and more widely useful, we propose to take them out of their current latex format and store them in a machine-readable source, e.g yaml, and to generate the latex tables needed for the DPDD, and possibly other formats e.g HTML. We also propose to remove the "Type" column from the DPDD tables as it is not prescriptive nor useful to the science user, and can give the erroneous impression that that the conceptual schema represents a concrete implementation. **
Attachments
Issue Links
- is triggering
-
DM-37922 Make LDM-153 obsolete
- To Do
-
DM-38584 Update DPDD tables to remove Type column and move to Yaml format
- To Do
- relates to
-
RFC-894 Remove baselineSchema from schema browser
- Implemented
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
A concern is that more than just the "type" column is going to be different between the DPDD and the production tables. Column names have changed from the DPDD, as have some units. I think it will be a challenge to make a yaml file that is generic enough.