Done
Details
Assignee
Mike TaylorMike TaylorReporter
Pennington Jr, BuddyPennington Jr, BuddyLabels
Priority
P3Sprint
NoneDevelopment Team
ThorFix versions
Release
Quesnelia (R1 2024)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Mike Taylor
Mike TaylorReporter
Pennington Jr, Buddy
Pennington Jr, BuddyLabels
Priority
Sprint
None
Development Team
Thor
Fix versions
Release
Quesnelia (R1 2024)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 27, 2023 at 2:55 PM
Updated December 3, 2024 at 11:31 PM
Resolved February 9, 2024 at 4:07 PM
FOLIO Holdings records include a Holdings statement field where libraries can store summary holdings data for serials, journals and/or multi-volume sets. For example, a library may enter something like v.1-25 (1971-1995) in the field. Having this data returned in the z39.50 XML can benefit libraries by allowing ILL staff to quickly determine if they hold the required volume for a journal article request. For example, if the library receives a request for an article from v. 32 of this example journal, ILL staff will know they do not have it and can move on to the next request.
Scanning lists of items is a workaround but for larger libraries and consortia, the item lists for a particular journal can run quite long and my not be in any sensible order, resulting in more staff time determining whether to process or skip a specific request.
I am not sure how this could technically be enabled for the FOLIO z39.50 service but the z39.50 service for Sierra, our former ILS places the equivalent data element into the <holding> <publicNote> XML tag. Example:
<holding>
<localLocation>UMKC DEPOSITORY</localLocation>
<callNumber>Periodical </callNumber>
<publicNote>v.1-95(1932-1979)</publicNote>
</holding>