[UIIN-2358] Add new browse options to limit browse by call number type Created: 21/Feb/23  Updated: 06/Oct/23  Resolved: 13/Jul/23

Status: Closed
Project: ui-inventory
Components: None
Affects versions: None
Fix versions: 10.0.0

Type: Story Priority: P3
Reporter: Christine Schultz-Richert Assignee: Dmytro Melnyshyn
Resolution: Done Votes: 0
Labels: front-end
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Browse_CallNoByType.PNG     File UIIN-2358_search_all_CN_types_OK.mp4     File UIIN-2358_search_different_CN_types_OK.mp4     File Wrong_CN_types_in_search_result_Issue.mp4    
Issue links:
Cloners
is cloned by STCOM-1183 CLONE - Add new browse options to lim... Closed
is cloned by UISACQCOMP-155 CLONE - Add new browse options to lim... Closed
Defines
defines UXPROD-3569 FE: Browse call numbers by their type Closed
Relates
relates to MSEARCH-557 Call Numbers Browse with call number ... Closed
relates to MSEARCH-599 NLM, SuDoc, and LC call numbers not s... Closed
relates to UIIN-2499 "Effective location (item)" facet is ... Closed
relates to MODINVSTOR-1046 Support basic call-number types Closed
relates to MSEARCH-514 Support typed call-number field Closed
relates to MSEARCH-515 Support browsing by typed call-number Closed
relates to MSEARCH-559 SPIKE Call Numbers Browse with call ... Closed
relates to FAT-5756 Review of C387475 test case Closed
relates to FAT-5757 Review of C387477 test case Closed
relates to FAT-5758 Review of C387478 test case Closed
relates to FAT-5759 Review of C387480 test case Closed
relates to FAT-5969 Review of C388548 test case Closed
relates to FAT-5970 Review of C388549 test case Closed
relates to FAT-6193 Review of C396366 test case Closed
relates to FAT-6885 Review of C400668 test case Closed
relates to MSEARCH-558 No exact match for call number with s... Blocked
relates to MSEARCH-570 Call number Browse: Local call number... Closed
relates to FAT-5769 Review of C387486 test case Closed
relates to FAT-5770 Review of C387487 test case Closed
relates to FAT-6541 Review of C398024 test case Closed
Sprint: Spitfire Sprint 169
Story Points: 3
Development Team: Spitfire
Release: Poppy (R2 2023)
RCA Group: TBD

 Description   

Purpose: Call number browse results are often used as a shelf list, which shows items in the order that they appear on the physical shelves. It is common for libraries to utilize different classification types in different locations, so to produce an accurate shelf list, the library needs to be able to refine by type.​

Requirements

  1. Add new browse options to limit browse to one of the following call number types on the Item record:
    1. Dewey Decimal classification
    2. Library of Congress classification
    3. Local (call numbers with a type source of: "local")
    4. National Library of Medicine classification
    5. Other scheme
    6. Superintendent of Documents classification
  2. Revise "Call numbers" browse option to "Call numbers (all)"
  3. Call numbers (all) and the above options should be a subgroup of Call numbers option, potentially utilizing this component: https://folio-org.atlassian.net/browse/STCOM-1121 
  4. User should be able to either browse by all call numbers, or browse by call numbers of a single type (i.e., cannot browse by both LC and Dewey) 

Out of scope: Other call number types not listed above and call numbers with no assigned type. If the assigned call number type is one that is not on the list above, the results should only include these items when browsing by all call numbers. 

 



 Comments   
Comment by Denys Bohdan [ 29/May/23 ]

Hey Christine Schultz-Richert, should we only show system call number types in the options list?

Comment by Christine Schultz-Richert [ 30/May/23 ]

Hey Denys Bohdan  - We should show any call number type where the source is system, and any types that have a source as local will just show up under a single "Local" option. This will be a fixed list.

Comment by Khalilah Gambrell [ 11/Jun/23 ]

Hey Christine Schultz-Richert, do you know what back-end issue is required to implement this story?

Comment by Christine Schultz-Richert [ 12/Jun/23 ]

Hey Khalilah Gambrell - I linked related backend stories; no other backend work is required for this particular ticket. If work begins in this ticket, we just won't be able to test the sorting per NLM and SuDoc.

Comment by Yauhen Viazau [ 11/Jul/23 ]

Verified on Snapshot-2 - browse options work as expected

See attached screencasts as examples:

Comment by Yauhen Viazau [ 12/Jul/23 ]

Issue found:

When browsing call numbers by type, results include call numbers of wrong types if they come from the same instance that has call numbers of expected type,

e.g., if we have instance with two Holdings/Items, one having LC-type CN, and another Dewey-type CN, and then browse with Dewey browse option selected, both CNs from an instance will be shown in results

See example: Wrong_CN_types_in_search_result_Issue.mp4

Dmytro Melnyshyn - please review

Comment by Dmytro Melnyshyn [ 12/Jul/23 ]

Hi Pavlo Smahin - looks like the UI is sending the correct request, please take a look at Yauhen Viazau comment above.

Comment by Pavlo Smahin [ 12/Jul/23 ]

Yauhen Viazau, please create a bug for mod-search

Comment by Yauhen Viazau [ 12/Jul/23 ]

Pavlo Smahin - here is the bug - MSEARCH-557 Closed

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