Structured Object Management Requirements

Definition

The management of hierarchical relationships among objects.

Requirements

  • User can create an object record with "sub-parts," or "items in a set"
  • User can add more than one hierarchical level to a object record (e.g. an item in a set may have a sub-part)

Standards, Guidelines + Use Cases

Use Cases

In the CollectionSpace system, Object records can participate in a containment hierarchy. In other words, a CollectionObject can be a part of something and it can also have sub-parts. For example, a CollectionObject can represent a chess set with each piece of the set also being represented by a CollectionObject:

Unknown macro: {multi-excerpt-include}

Visualization from the CIDOC CRM:

Numbering Recommendations from The New Museum Registration Methods

Parts of a whole, e.g. pieces in a chess set: If the accession number for the chess set as a whole is 2009.1.1, each piece would receive a letter: 2009.1.1a, 2009.1.1b, 2009.1.1c, etc.

Items in a set, e.g. drawings in a folio: If the accession number for the folio as a whole is 2009.1.1, each drawing would receive an additional number: 2009.1.1.1, 2009.1.1.2, 2009.1.1.3, etc.

Wireframes

Service Descriptions

Fields

User Story Summaries

Structured Object User Story Summary