With so much work on Admin Sets now (autumn 2016), it's worth documenting the current understanding of how "nested collections" ought to work. This document attempts to explain in functional terms what the needs are. Note that Admin Sets are not based on PCDM.

Use Case 1: Agencies and Sub-agencies

The top-level collection is an agency (a data provider). Some of these agencies have sub-agencies, so the nested collection is the sub-agency. The layering here is useful in terms of navigation: a user should be able to view top-level agencies together and be able to drill down into sub-agencies.  Additionally, a search for everything in an agency will return works in the agency and all sub-agencies under that agency.

Requirements

Questions

 


 

Use Case 2: DSpace communities and collections

Data currently stored in DSpace will be migrated to a compatible structure in CC or Sufia.

DSpace nested structure:

User interactions related to nesting:

Features

Reference:   Required Feature Matrix (compiled by DSpace/Hydra Interest Group)

Of interest to this discussion:

 

Reference:  Collection Specs for Hydra Community

This document describes nesting requirements and other assumptions for behavior within a Hydra app for supporting a DSpace type structure.

Questions

Questions from the Collection Specs for Hydra Community document.

 

Implementations requiring multiple level of communities: