-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Labels
PO (review)featureUpdates on existing feature or a new feature requestUpdates on existing feature or a new feature request
Description
User story
A special collections staff member I would like to have 773 data available (particularly subfield g) so that it can be passed over to Aeon when someone requests the item.
Acceptance criteria
- Subfield g values from the 773 are added to the index
- These values maintain their association with their host record MMS ID listed in subfield w of the 77 field since Aeon request data depends on these associations.
Concrete example
Each 773 could be stored in as a key in an array of hash structures that look like this.
constituent_details: [
{ host_mms_id: "{a host mms_id}", constituent_container_label: "Folder 17" },
{ host_mms_id: "{another host mms_id}", constituent_container_label: "Folder 18" },
]
Implementation notes, if any
See this note added to this closed ticket for details and examples of complex constituent records that have multiple 773 values. We currently process 773 data but only to persist the MMS IDs of host records into the "contained_in_s" key.
A report prepared of SC constituent records is available.
Metadata
Metadata
Assignees
Labels
PO (review)featureUpdates on existing feature or a new feature requestUpdates on existing feature or a new feature request
Type
Projects
Status
Backlog