Inventory search. Support browse searches, e.g. call numbers (UXPROD-2988)

[UXPROD-3569] FE: Browse call numbers by their type Created: 17/Feb/22  Updated: 08/Feb/24  Resolved: 19/Dec/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Inventory search. Support browse searches, e.g. call numbers

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Christine Schultz-Richert
Resolution: Done Votes: 0
Labels: LC-priority1, LC1, browse, cataloging, consortia-ebsco, loc, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4327 BE: Browse call numbers by their type Closed
Defines
is defined by STCOM-1183 CLONE - Add new browse options to lim... Closed
is defined by UIIN-2358 Add new browse options to limit brows... Closed
is defined by UIIN-2385 Restrict modifying and deleting syste... Closed
is defined by UISACQCOMP-155 CLONE - Add new browse options to lim... Closed
Requires
requires UIIN-2499 "Effective location (item)" facet is ... Closed
Epic Link: Inventory search. Support browse searches, e.g. call numbers
Front End Estimate: Large < 10 days
Front End Estimator: Christine Schultz-Richert
Front-End Confidence factor: 100%
Back End Estimate: Out of scope
Back End Estimator: Christine Schultz-Richert
Estimation Notes and Assumptions: BE estimate depends on results from architectural review and POC
Development Team: Spitfire
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

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

  1. Add new browse options to limit browse to one of the following call number types on the Item record:
    1. Dewey Decimal
    2. LC
    3. Local call numbers (source: "local")
    4. NLM
    5. Other scheme 
    6. SuDoc
  2. Retain option to browse by all call numbers
  3. Implement SuDoc normalization for sorting
  4. Implement NLM normalization for sorting
  5. 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:



 Comments   
Comment by Khalilah Gambrell [ 13/May/22 ]

Hey Magda Zacharska - will this be include in Morning Glory release?

Comment by Magda Zacharska [ 13/May/22 ]

Khalilah Gambrell - unfortunately we will not be able to address it in Morning Glory. I just moved it to Nolana.

Comment by Khalilah Gambrell [ 06/Jul/22 ]

Lets aim to have the requirements defined in Nolana so that Spitfire can plan to do the work in Orchid.

Comment by Erin Nettifee [ 13/Jul/22 ]

Magda Zacharska should the release field on this be updated to Orchid as well?

Generated at Fri Feb 09 00:33:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.