Add copy number to Edge RTAC response

Description

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:

,  

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Molly Driscoll January 8, 2024 at 9:14 PM

I think you can close this as a duplicate. I don't see any missing requirements on https://folio-org.atlassian.net/browse/EDGRTAC-81?

Khalilah Gambrell January 5, 2024 at 6:45 PM

Hey   - can we close this issue as a duplicate to this https://folio-org.atlassian.net/browse/EDGRTAC-81? Or does have a requirement that is missing in EDGRTAC-81?

Molly Driscoll January 5, 2024 at 5:44 PM

happy new year! I think these two tickets could be consolidated. This ticket () specifically calls out the item copy number, but I could update it to include the holdings copy number, too. Would you like me to do that?

Khalilah Gambrell January 5, 2024 at 3:17 PM

Happy   - does this requirement https://folio-org.atlassian.net/browse/EDGRTAC-81 duplicate this one? 

Duplicate

Details

Assignee

Reporter

Priority

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
TestRail: Cases
TestRail: Runs