Creating Object Hierarchies

Within the Cataloging procedure, users may create object hierarchies. To create a broader (parent) or component (child) relationship between object records, first create or edit an object record. In this example, we will create an object record (2013.001.0001a) with a broader object (2013.001.0001) and two object components (2013.001.0001a.1 and 2013.001.0001a.2). 2013.001.0001a is a separable part of 2013.001.0001, and 2013.001.0001a.1 and 2013.001.0001a.2 are non-separable parts of 2013.001.0001a.

At the bottom of the Cataloging data entry screen is the “Object Hierarchy” information section. In the screenshots below, the ID number in blue is the number of the Primary record.

To add a broader object to the Primary record, enter the identification number of the broader object into the Broader object field. This field uses a predictive-text interface; if the broader Cataloging record already exists, it will appear in the list. If it does not already exist, a new record may be created using this interface. To create a new, blank, record, select “Create New.” To create a record that copies data from the Primary record, select “Create New from Existing.” Select a relationship type from the dropdown, and save the record.

To add components to the Primary record, enter the identification number of the component into the Object component field. In the below examples, the components do not yet exist. Component 2013.001.0001a.1 uses Create from new and component 2013.001.0001a.2 uses Create from existing. The record for component a.1 will be blank apart from the ID number, and the record for component a.2 will be a copy of the record for 2013.001.0001a. An object may have multiple components, but only one broader object.

Selecting the small gray arrow to the left of either component record will allow the user to pivot to that record. Within the hierarchy section for 2013.001.0001a.2, 2013.001.0001a appears in the Broader object field.

Relationships selected from the dropdowns are reciprocal. Using the examples from above, record 2013.001.0001a.2 has the object component type Non-separable part. If the user pivots to the record for 2013.001.0001a.2, the broader object record 2013.001.0001a will appear in the Broader object field with an Broader object type of Work (non-separable part).

Browser not supported