Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Call number suffix not displaying in EDS

Description

Steps to repro:

  1. Log into Chalmers FOLIO and find a title in Inventory

  2. Edit a holding in the instance to ensure the call number AND call number suffix are populated

  3. Make sure there is an item for this holding

  4. Log into EDS and search for the title

  5. Review the call number info displaying for the item

Expected/Desired : Should include call number suffix (Chalmers needs this) but it might also make sense to include the prefix, as well, as other institutions will almost certainly need this. Including prefix shouldn't affect Chalmers, as they don't plan to populate the prefix. Note: The logic we are using elsewhere for call number display in FOLIO is use item data, if available, otherwise use the holding data. This should work for Chalmers, as they plan to not populate call number data at the item level.

Actual: Suffix and prefix aren't displayed

Reach out to if you have questions

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Martin Tran September 12, 2019 at 9:24 PM

Suffix is shown appended to the circulation number now.
Prefix will be shown prepended to the circulation number if they are populated in inventory.

Magda Zacharska September 11, 2019 at 5:56 PM

Chalmers plans to use suffix part as a specific location on the shelf. For example, if there is an item that is located on shelf tk and is sorted under the author's name Johnson, the call number data would be:
Call number: tk
Call number suffix: Johnson
In order to be readable the space is required:
tk Johnson

Martin Tran September 11, 2019 at 4:41 AM

What should the call number with both prefix and suffix look like? Could it be space-separated such as "prefix callNumber suffix" or something else?

Magda Zacharska September 4, 2019 at 2:01 PM
Edited

According to 's analysis, the implemented logic in other parts of FOLIO is not easily referenced and would come down to copy and paste of existing code. This means if the rules change once https://folio-org.atlassian.net/browse/UXPROD-1626#icft=UXPROD-1626 is ready to be implemented the same code will need to me modified in multiple places and we would need to revisit this code on our side as well. In this in mind, https://folio-org.atlassian.net/browse/MODRTAC-18#icft=MODRTAC-18 will address the issue of holding/item call number logic. In this ticket we will include holding level call number prefix and suffix. This would satisfy Chalmers needs but will prevent us of creating technical debt for other implementations.

Cate Boerema August 29, 2019 at 7:21 AM

would you be the PO for this?

Done

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 29, 2019 at 7:20 AM
Updated January 3, 2020 at 2:22 PM
Resolved September 12, 2019 at 9:24 PM
TestRail: Cases
TestRail: Runs

Flag notifications