Working with related records (boundwiths)
Examples
Rubenstein child records - https://duke.app.box.com/file/1342146769789?s=zkgpewe4kgxiv1cjh1k2eafdh56i6q29 - from Lauren Reno, data pulled from Aleph
773 data is now being populated in Alma Analytics in the Bibliographic Details folder that appears in many of the subject areas, so reports can be run to generate items from there
Ex Libris documentation
Teams convos
Metadata management:
Erin Nettifee (she/her/hers): Is there a list anywhere of items that are boundwiths?
posted in Alma Implementation / Metadata Management on Monday, June 10, 2024 2:59 PM
Tips / miscellaneous
It was very difficult in Aleph to determine what records were parents because they generally did not have 774 / parent MARC tags
Records that involve Law can be super super messy from the DUL perspective- Law has a collection called “Unclassified pamphlets” where a lot of these are - Jessica Janecki has a lot of experience with these
BW connection information is generally in the 773 (related records)
The relation type for the records in Alma will display as CONTAINS/PART OF
There is a linked records scheduled job that has to be running in order to properly link boundwiths together - called MMS - Build Record Relations
When testing on the sandbox, you must remember to run this job manually since it will not run automatically
OAI-PMH publishing
OAI-PMH will publish item information from the parent if the 773 is part of the bib record and has correct linking info (e.g., an MMSID)
Item enrichment on the child record will be incomplete if the parent is not republished when the child is republished (or has not been republished recently - it’s not clear how the timing on this exactly works. We saw examples in testing in September 2025 where child records would have 940 fields without the 940$b and the issue is that the parent record had not been republished / published in several months. We republished the parent records in those cases, and that made the 940$b start to appear as expected.