Currently, users make applications to Resources (partners). If a partner has multiple collections, the user selects a collection as part of their application. This configuration has led to a large amount of code duplication between the resources and streams models, in addition to making a number of features more complicated and/or harder to implement.
We should instead move to having collections (streams) be what users apply for, with 'partners' being a bucket for collections probably containing little more information than the name. This would fix a number of outstanding bugs and feature requests, and simplify future work.
Tasks fully or partially solved by this: