Skip to:

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

Incorrect sorting of LC call numbers in browse

Description

Overview: Incorrect sorting of LC call numbers in browse
Steps to Reproduce:

  1. Add a Holdings to any Instance existing in the system

  2. Specify following call number values for added Holdings:

    1. Call number type: LC, call number: PN2 .A6 1999, suffix: CD

  3. Add Item to the Holdings (do not specify call number values in Item)

  4. Add a second Holdings to any Instance existing in the system (do not specify call number values in Holdings)

  5. Add Item to the second Holdings

  6. Specify following call number values for added Item in second Holdings:

    1. Call number type: LC, call number: PN2 .A6, volume: v. 3, enumeration: no. 2, chronology: 1999

  7. Select "Browse" in toggle

  8. Select "Library of Congress classification" browse option

  9. Fill browse input field with "PN2 .A6 v.3 no.2 1999"

  10. Click "Search" button

Expected Results:

  • Browse results are shown in second pane

  • Rows with following call numbers are shown in this order:

  •  

    • PN2 .A6 (highlighted in bold)

    • PN2 .A6 1999 CD

Actual Results:

  • Browse results are shown in second pane

  • Rows with following call numbers are shown in this order:

  •  

    • PN2 .A6 1999 CD

    • PN2 .A6  (highlighted in bold)

Additional Information:
See attached screencasts:

  •  

Interested parties:  

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

5

is required by

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Yauhen Viazau August 11, 2023 at 7:17 AM

Hey - I have reproduced the issue following the test case from the description. It is reproducible when first call number values set is specified in a Holdings, and the second call number values set is in an Item (which is in a different Holdings in the same or different Instance).
Updated the description to reflect this and to include only required steps.

See examples of how this is reproduced on both Snapshots:

Christine Schultz-Richert August 10, 2023 at 3:23 PM

Hey   - I can't seem to reproduce the actual results in snapshot. When I create items with the two call numbers:

  • Call number: PN2 .A6, volume: v. 3, enumeration: no. 2, chronology: 1999

  • Call number: PN2 .A6 1999, suffix: CD

Call number browse by LC type is showing the correct sort:

Pavlo Smahin August 10, 2023 at 9:27 AM

, we use for sorting external library marc4j, it provides the method that calculates shelving order that is used for sorting on the browse page. I mean that no development done in the scope of Folio to support any sorting rules for the LC call numbers.
If you would like to change something in the sorting requirements then we need a story for this with described requirements of all sorting rules for LC call numbers.

Yauhen Viazau July 12, 2023 at 3:36 PM

, I have updated the description and test case according to discussion here

Laura E Daniels July 12, 2023 at 1:57 PM

Yes, these results do look correct to me as well, other than the first two.

Won't Do

Details

Assignee

Reporter

Labels

Priority

Development Team

Spitfire

Release

Poppy (R2 2023)

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 12, 2023 at 8:08 AM
Updated August 11, 2023 at 2:40 PM
Resolved August 11, 2023 at 2:40 PM
TestRail: Cases
TestRail: Runs