Complex relationships

Needed by whom and when

Basic statements about who needs the functionality and by when.

UCB: We need to flesh out some use cases based on PAHMA and UCJEPS and evaluate those to determine priority.

Overview

Need very flexible system of relating things including CSpace relationships and other mechanisms that may have similar function. Need relationships between objects and other objects (groups, subobjects, other object-object relationships); objects and procedures; possibly between object/procedure records and authority items outside their use in specific fields  (e.g., objects and events or activities), authority items and other authority items; media and everything; bibliography and everything; sites, and so on.

We suspect that in some cases the system will need some intelligence based on a relationship type (e.g., parent, child, synonym).

We also suspect that in some cases (many?) the relationship itself will need additional fields to help describe the relationship (e.g., remarks, relationship type).

Question: What are user stories for intelligence based on relationship type?

Question: What are the user stories for additional fields describing relationships?  Some are listed below under use cases.

Question: Can anything with a csid be related to anything else with a csid, and will the functionality be adequate?

Question: When is it best to use relationships as opposed to custom fields tied to vocabularies (custom or otherwise)?  We might want to develop some general guidelines here.

User stories for definition

Please feel to rewrite these or eliminate completely!  Then move to the prioritized headings below.

Complex relationships: System can be configured to initiate behavior based on relationship type.  Question: What are specific user stories for this?

Complex relationships: Additional fields describing relationships - PAHMA: When associating a taxonomic term to a collection object (and there can be multiple per object), PAHMA needs a note or remarks field to describe the relationship (for each term association).

Complex relationships: Additional fields describing relationships - PAHMA: When associating a person with an object or procedure, a role needs to be recorded in addition to the person association. Example, other people related to a loan not specified in loans schemas, e.g., appraiser, sponsor, insurer.  Question: Would this be better handled as adding custom fields to the loans schema for appraiserPerson and so on?  Or add a custom repeatable group (associatedLoanPerson, associateLoanPersonRole)?

Prioritization of user stories

As definitions and priorities are clarified, the user stories above should be moved into relative order below.

Must have for 1.x-MUSEUM (when they go live in system)

Placeholder for required functionality.  As a general rule, functionality that you need and use now should go here or where you have existing data.  However, this is up to the museum.  We will have to balance requirements against resources and timelines.

Placeholder

MUSEUM could wait six to twelve months

What could wait?  These will be re-prioritized at a later date.

Placeholder

MUSEUM would like to have this eventually

These are nice to have but not a near term requirement.

Placeholder