FE: Browse call numbers by their type
Description
Priority
Fix versions
Development Team
Spitfire
Assignee

Solution Architect
None
NoneParent Field Value
None
Parent Status
None
is cloned by
is defined by
Checklist
hideTestRail: Results
Activity
Show:

(OLD ACCOUNT) Erin Nettifee July 13, 2022 at 2:18 PM
should the release field on this be updated to Orchid as well?

Khalilah Gambrell July 6, 2022 at 8:01 PM
Lets aim to have the requirements defined in Nolana so that Spitfire can plan to do the work in Orchid.

Magda Zacharska May 13, 2022 at 7:57 PM
- unfortunately we will not be able to address it in Morning Glory. I just moved it to Nolana.

Khalilah Gambrell May 13, 2022 at 7:04 PM
Hey - will this be include in Morning Glory release?
Done
Reporter

PO Rank
0
Estimation Notes and Assumptions
BE estimate depends on results from architectural review and POC
Front End Estimate
Large < 10 days
Front End Estimator

Front-End Confidence factor
100%
Back End Estimate
Out of scope
Back End Estimator

Rank: Cornell (Full Sum 2021)
R3
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 17, 2022 at 8:24 PM
Updated May 9, 2024 at 7:23 PM
Resolved December 19, 2023 at 3:34 PM
TestRail: Cases
TestRail: Runs
Current situation or problem:
The current implementation allows for browsing all call numbers in one search but does not support narrowing the browse to the specific types.
Requirements/In scope
Add new browse options to limit browse to one of the following call number types on the Item record:
Dewey Decimal
LC
Local call numbers (source: "local")
NLM
Other scheme
SuDoc
Retain option to browse by all call numbers
Implement SuDoc normalization for sorting
Implement NLM normalization for sorting
Sort results by Effective call number (item), shelving order
Proposed solution/stories
UI modifications to limit browse by the call number type in new browse options
Modify call number browse on the backend so that it takes into consideration the value of the call number type (items or holdings)
Additional information:
Call Number browse use cases: https://folio-org.atlassian.net/wiki/display/MM/Browse+Use+Cases
MM SIG meeting (Feb 17, 2022): https://folio-org.atlassian.net/wiki/display/MM/2022-02-17+Metadata+Management+Meeting+notes
Call number browse priorities - survey results (to be linked)
Shelving order tickets:
LC: https://folio-org.atlassian.net/browse/MODINVSTOR-381
Dewey: https://folio-org.atlassian.net/browse/MODINVSTOR-876
Other scheme: https://folio-org.atlassian.net/browse/MODINVSTOR-877