The concept of having two types of "containers" (both Community and Collection) does not seem to meet any modern IR need. It also complicates our content model, and forces DSpace users into a very specific hierarchy of content.
We should replace this hierarchy with a single type of "container" (working title: Collection). This new type of "Collection" should be able to either contain Items or sub-Collections or both. This would allow Collections to replace Communities altogether.
Use Cases / Needs
- Determine all areas of codebase which will be affected by this refactoring:
- User Interface
- REST API
- SWORD(v1 and v2)?