Depositing Bound-withs at SLFs
See Best Practices for Decision Pages and Tags for groups
Legend: NOT STARTED IN PROGRESS STALLED DECIDED
Status | IN PROGRESS |
|---|---|
Description | Decide how and if bound-with volumes can be deposited in SLFs. |
Decision summary |
|
Owning group | |
Approver |
|
Consulted | SLFs, Campuses, SCLG (Shared Collections Leadership Group), SPST (Shared Print Strategy Team) |
Informed |
|
Decision-making process |
|
Priority |
|
Target decision date | Sep 30, 2026 |
Date decided |
|
Recommendation
Due to the loss of access that comes with removing bound-with records from a campus’s IZ, we recommend that campuses generally refrain from depositing monographic bound-withs in SLFs.
If a campus does wish to deposit a bound-with to an SLF, they have the option to unbind the volume (assuming the binding is not important) and deposit the items separately; or; create a single record for the entire bound volume.
Note: UCLA and Berkeley have been able to avoid these issues because they share an IZ with the SLF to which they deposit. However, with the new SLF Allocation methodology, deposits may not be guaranteed to go to a particular SLF.
Impact
Stakeholder group | Impact |
|---|---|
SLFs | Difficulties in processing bound-withs are avoided. |
Campuses | Bound-withs must be kept in the stacks or dealt with otherwise. |
SCLG |
|
SPST |
|
Reasoning
Both methods of creating bound-with records in Alma (see below under Background) require linking within the IZ. As soon as the records are removed from the IZ, the linking is broken and the records are no longer connected.
Background
A bound-with is a single physical volume that contains two or more separate, distinct works or publications bound together after they were originally printed. In library catalogs, they are often represented with separate bibliographic records for each individual work, linked in some way to a single holdings/item record.
In Alma, this can generally be done in two ways:
Parent record with 774 fields
A “parent” record is created locally. Since the record is not in OCLC, generally it is kept only in the IZ. The parent record is attached to the holdings and item record.
The parent record contains 774 fields for each constituent part. The 774s use an identifier in the $w (the nightly “MMS - Build Record Relations” job depends on this) and the value “unrelated” in the $9 (to trigger the “Bound with” label in Primo)
The records for the constituent parts can be in the NZ; they have no holdings or item records.
Constituent records with 773 fields
The record for the first constituent part acts as the “parent” record--it is attached to the holdings and item record.
Every subsequent constituent record contains a local 773 field to link to the record for the first part. The 773 uses an identifier in the $w and the $9 “unrelated.”
All constituent records can be in the NZ; they have no holdings or item records.
Because both methods rely on linking from local records (method 1) or local fields (method 2), they present a problem for SLF deposit (when the SLF does not share an IZ with the depositing campus). The SLFs rely on records being in the NZ, and local fields cannot be transferred.
UC SILS documentation: https://uc-sils.atlassian.net/wiki/x/AQBWcg
Alma documentation: https://knowledge.ag-software.clarivate.com/alma/en-us/Product_Documentation/Physical_Resource_Management/Configuring_Related_Records_for_Physical_Inventory.html
OCLC documentation: https://www.oclc.org/bibformats/en/7xx/773.html, https://www.oclc.org/bibformats/en/7xx/774.html
UCLA documentation:
UCSD documentation: https://docs.google.com/document/d/1YczJ9vLQRFwVFEoTxMmrH8YTdllM-6hSYShUuuS4Wl0/edit?usp=sharing
Options Considered
| Option 1 | Option 2 |
|---|---|---|
Description | Campuses refrain from depositing bound-with volumes in the SLFs. | Records are adjusted in a way that can transfer to an SLF. |
Pros | Problems with linking are avoided. | Campuses can deposit bound-withs in an SLF. |
Cons | Campuses must keep bound-with items in the stacks. | Significant cleanup work may be needed to make sure the records can link correctly |
Questions to consider
Ideas for Option 2:
Method 1:
Make parent records an exception to the “all NZ records must have an OCLC number rule,” or, add the parent records to OCLC(?)
Make sure the SLFs know they need to bring all the constituent records into the IZ.
Ensure all linking identifiers are either NZ MMS IDs (assuming that works) or OCLC numbers--not local campus MMS IDs.
Method 2:
Send SLF a file of MARC records to import instead of taking them from the NZ (to make sure the local 773s come through) OR
Add 773s to OCLC record with $5 for the depositing campus before depositing in SLF. SLFs would still need to add $9 unrelated?
Other:
Unbind your bound-withs (if the binding is not important)
Create an original record in OCLC for the entire volume
How are campuses doing it now?
UCSB tries to avoid sending them but are not always successful.
UCSD also tries not to send them. Have unbound a few and did an original records for one using a 501 field.
UCSC also does not send them
UCR sends boundwiths to SLF but don't seem to be doing anything to records, etc
UCM has zero allocation
What about boundwiths the campuses other than UCB and UCLA sent pre-Alma? We locally added 7XX fields to account for the additional titles but those fields will be gone now with WorldCat Updates.