Refine scenarios and verify sorting of items enumeration by number

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Overview: Prior to Orchid, items sorted by enumeration such that volumes displayed numerically (example v. 1, 2, 13, 20) instead by string (example v. 1, 12, 2, 20).  Sorting functionality should be re-introduced by enumeration.

Steps to Reproduce:
 # Log into the folio-snapshot environment.
 # Open Inventory and find the ABA Journal, inst000000000001.
 # Click on the Holdings record associated with the Main Library, hold000000000002.
 # Add a new item to the holdings record where the 'Enumeration' = v. 8 no. 1-6.
 # Click Save & Close.
 # Click the down-arrow next to hold000000000002 to display all items and sort by the 'Enumeration' column. 

Expected Results: The items list in either v. 8 no.1-6, v. 70 no. 1-6, v. 70 no. 7-12...... v. 73 no.1-6 OR v. 73 no. 1-6, v.72 no. 6-7,10-12, v. 72 no. 1-6......v.70 no. 1-6 order.  

Actual Results: The items list in v. 70 no. 1-6, v.70 no. 7-12......v.73 no.1-6, v.8 no. 1-6 OR v. 8 no. 1-6, v.73 no. 1-6, v. 72 no.6-7,10-12.....v. 70 no. 1-6 order.

Additional Information:  This functionality was originally implemented as part of UIIN-1412 and is discussed in the comments of .  Though  re-implemented item sorting, it did not return it to full previous functionality.  For any library with a large number of items attached to a holdings record, sorting by the enumeration is critical to workflow.  

Interested parties: University of Chicago 

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Lynne Fors January 13, 2025 at 4:09 PM

Discussed in Metadata Management SIG:

Charlotte Whitt January 10, 2025 at 11:42 AM

A similar issue is raised on FOLIO slack about the sorting of Volume -

Alissa Hafele June 25, 2024 at 5:01 PM

any word on this being considered for an earlier release than Ramsons? Stanford just went to Poppy csp3 and very interested in this being fixed.

Khalilah Gambrell April 17, 2024 at 12:11 PM

Hey this issue is tied to Failed Q test case https://foliotest.testrail.io/index.php?/tests/view/2444836 and has also been reported by Cornell as a P1

I believe this issue needs to be considered for Quesnelia.

cc:

Kateryna Senchenko February 21, 2024 at 11:59 AM

Converting this issue to a task, because no implementation is expected from the UI side. However, we need to make sure that scenarios described here end up in the test rails and the behavior is verified.

Details

Assignee

Reporter

Priority

Story Points

Development Team

Folijet

Release

Trillium (R2 2025)

Affected releases

Quesnelia (R1 2024)
Poppy (R2 2023)
Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 13, 2023 at 9:08 PM
Updated March 17, 2025 at 4:16 PM
TestRail: Cases
TestRail: Runs