...
- reuse code from datarel, can't use datarel as-is, not generic enough
- ideally, computation related to images should happen in afw, not in datarel or metadata store related code (apps team already agreed to deal with computation related to sources)
- research off-the-shelf systems that might be useful (irods, what fermi did etc)
- when importing external data sets, better to "make it butler-compatible first, then ingest"
- metadata store needs to deal with repositories of configs
- might need to capture in provenance which version of butler was used
- need to discuss with SUI team if sql interface to metadata is sufficient, or web api is needed
- different typed of images in one repo or separate? Let butler drive it: one repository per task is best
- meaningful vs obscure file names - still tbd