- As a consumer of datasets who uses the butler to access them, I'd like to be able to access datasets generated by/according to specifications of an older version of the butler using a newer version of the butler. In this scenario, it's perfectly acceptable and even desired to be able to migrate repositories to be compatible with the newer version of the butler. Succinctly - the user desires a repository migration process.
- As a consumer of other astronomical datasets, I typically use astropy and other provided interfaces to access data from other astronomical datasets. I'm familiar with the vocabulary and terminology used by these interfaces, as well as their functional aspects. I need to be provided an interface/ API which I can understand, hopefully which I'm familiar with, when accessing the data of the LSST.
- As a user of the DAC, I'd like to be able to bring in arbitrary images and catalogs to process within the DAC, including both historical and simulated data. I'm not an LSST expert, and I'm not an expert on the data I'm bring, so I'd like the lowest overhead possible in using this data with the LSST applications.
- As a user of the DAC, I'd like to request the instantiated dataset objects returned an interface be available in several supported instantiations, such as afw.image/afw.table, astropy nddata, pandas dataframe, dask dataframe, and potentially other formats.