[Aeon] Process 773 Fields for Constituent Records into Solr so Data Can Be Passed to Aeon

[kevinreiss]

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 passed over to Aeon in the ItemVolume Field

Possible Data Structure

Each 773 could be stored in as a key in an array of hash structures that look like this.

Example 773 Data from: https://catalog.princeton.edu/catalog/9917554523506421 (this is has two 773 that each point to a different host MMS ID).

773 0 3| Derrida copy 1 w| 99125489801606421 g| folder 9 o| 2.4.2.3 (M)
773 0 3| Derrida copy 2 w| 99125489791106421 g| folder 4 o| E39

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.

Need some clarity on where this new data lives, does it live in the context of making it available to the request data passed to Aeon, does it live on the host or constituent record?

[kevinreiss]

this ticket needs some clarification and an updated example before it can be worked on.