Duplicate
Details
Assignee
Khalilah GambrellKhalilah GambrellReporter
Molly DriscollMolly DriscollPriority
TBDDevelopment Team
NoneTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Khalilah Gambrell
Khalilah GambrellReporter
Molly Driscoll
Molly DriscollPriority
Development Team
None
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 12, 2023 at 4:31 PM
Updated January 8, 2024 at 9:24 PM
Resolved January 8, 2024 at 9:24 PM
Current situation or problem: ** Within FOLIO, the effective call number contains the following elements in the following order:
Prefix - Call Number - Suffix - Volume - Enumeration - Chronology - Copy Number
RTAC only returns the following elements of the effective call number string:
PRE CALL SUF (ENUM CHRO) or PRE CALL SUF (VOL)
Copy number is the only element that is not eligible for inclusion in the RTAC response. As a result, for libraries who wish to surface this information to their end users, they must add the information to a different field within the item record (e.g. call number). By adding the copy number to the RTAC response, libraries could surface it in discovery without sacrificing the integrity/intent of the item level fields in FOLIO.
In scope
Add copy number attribute to RTAC response
Out of scope
Use case(s)
Proposed solution/stories
Links to additional info
https://folio-org.atlassian.net/wiki/display/FOLIJET/What+gets+returned+in+edge-rtac+response
Questions
Interested parties:
,