Fix Version/s: None
We've talked in the past about adding umbrella CHAINED collections for each instrument to gather raws, calibs, refcats, masks, etc. It's time to do that now.
We should also make sure any RUN-type collections created by ConvertRepoTask are truly going to be valid forever or hidden behind CHAINED collection links. For example, it's not appropriate to put the particular version of the HSC bright object masks we find in repos today as "HSC/masks"; we probably want them to go in "HSC/masks/<version>" and have an "HSC/masks" CHAINED collection referencing that.
Here's a more complete proposal: https://confluence.lsstcorp.org/display/DM/Standard+Collections+and+Collection+Naming+Conventions
- is triggered by
RFC-741 Policies and Conventions for Organizing Gen3 Data Repositories
I've taken a look and made some comments previously. Removing myself from the reviewer list.
Simon Krughoff, did you spot this review request, and do you think you'll be able to get your piece of it done sometime today or early tomorrow?
Jim Bosch sorry about letting that fall off my plate. I've reviewed my two PRs and only have one trivial comment.
ctrl_bps passed jenkins test. Made pull request. Changing input collection name in example yaml must wait for pipelines_check changes.