Call number browse | Update order of call number components in fullCallNumber

Description

Overview: The original requirement was written so that the Suffix appeared at the end, following the enumeration data. The suffix needs to be moved to come right after the Call number.

Requirements:

  • Move Suffix field so that it appears after the Call number

  • Order of data in fullCallNumber should be: call number, suffix, volume, enumeration, chronology, copy number,

Environment

None

Potential Workaround

None

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Attachments

5

Checklist

hide

Activity

Show:

Valery_Pilko February 11, 2025 at 12:58 PM

- great news! Looks like now users will get exact match more often. Thank you for confirmation!

Christine Schultz-Richert February 11, 2025 at 12:47 PM

Hey - This is correct. We are not looking at the copy number for sorting because we are considering an exact match without looking at the copy/volume/enumeration data.

Valery_Pilko February 11, 2025 at 9:55 AM

Hey - could you please review our discussion above and confirm that requirement applied for sorting of call numbers is valid?

Pavlo Smahin February 11, 2025 at 9:45 AM

you are right.

Valery_Pilko February 11, 2025 at 9:20 AM
Edited

Thank you , one more question:
Am I right to say that now browse result list will be sorted only by “call number + suffix” fields (aka “fullCallNumber” field)?
And following fields will not be used for sorting: “volume, enumeration, chronology, copy number” because they are removed from “fullCallNumber” field?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Spitfire

Release

Sunflower (R1 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 22, 2025 at 3:06 PM
Updated February 11, 2025 at 12:58 PM
Resolved January 29, 2025 at 2:50 PM
TestRail: Cases
TestRail: Runs