Duplicate ... Instance Record. Accordion Related Instances. Implement elements

Purpose: To re-order and extend the metadata in Inventory Instance record, the new accordion named Related instances collected in accordance with the Metadata Management SIG discussions, a small working group, and the GAPS analysis done by the Data Migration Subgroup, which are captured in

Inventory Beta - Metadata Elements (tab: Instance Metadata for Inventory) https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit?ts=5b715226#gid=952741439 - see: column: B (UIIN-282), and column I (Related instances)

Spec for MARC mapping - see (Accordion Related instances):
https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=395847026

Acceptance Criteria:

• Inventory Beta - Metadata Elements, column I (Related instances)

• Fields where Jira Story UIIN-282 - see: column: B are in scope for this story

• Elements with a check mark in column C is implemented for alpha, or later updates

• Create, view, edit and clone mode of the instance record all need to be updated

• The UI display should look like the attached UX wireframes

• Metadata elements labels should be as shown in column A "Instance Metadata Elements" column (please pay attention to the label case

• Form edit controls (and values, where applicable) are specified in the "Input Type" column

• Repeatable fields are indicated in column G "Repeatable"

• Required fields are indicated in column H "Required" - include asterisks where noted (these denote that the field is required)

• Please note, some of these have input controls that will ensure they are populated (when records are created via the UI). Others will require a validation message if left blank but that is out of scope for this story

• All other columns in the Inventory Beta - Metadata Elements (tab: Instance Metadata for Inventory) spreadsheet can be ignored