Collection hierarchy

[wkmor1]

There are ~30 collections that have records that are not associated with a terminal collection (a collection with no sub/child collections). This is undesirable as it breaks the assumption of unique and persistent identifiers for collections.

• Creating new child collections when necessary and moving records out of parent collections.
• Adding logic systems to prevent
  • records being added or moved to parent collections and
  • child collections being created for collections that have records.
  • Checking systems that might break when we implement 1 and 2 (e.g., api calls that include “includeSubCollections=FALSE” will not return the same data as before).

[wkmor1]

(June 11, 2024) Kotka expert group may discuss collection migration to new kotka soon.