Item sort order via API requirements

https://folio-org.atlassian.net/browse/UXPROD-5257

draft

Ability to define how items are sorted

• Currently, items are sorted in FOLIO based on barcode value; however, this is not always the desired sorting of items, especially on discovery layers for patrons and staff using the OPAC.

• The desired sort may be on free text values that are not sortable, such as chronology

• There may be hundreds of items and it is difficult to find known items and to identify gaps in the collection

Not reviewed

No deduplication/validation of defined sort order

• If the implementation follows the pattern of a numeric sort order field that libraries change, we do not need to make sure that users haven’t duplicated this numeric value

Not reviewed

Retain existing default sort order (for existing items), require manual re-sort

• When a configurable sort order is added, the current state sorting is based on the default. We need to retain this sort upon implementation.

Not reviewed

For newly created items, sort at the bottom of the order

Not reviewed

Add sort order to RTAC schema response

RTAC - Real Time Availability Checking What gets returned in edge-rtac response

Not reviewed

Do not need to update sort order on the UI

• This will be in scope of https://folio-org.atlassian.net/browse/UXPROD-1625

Not reviewed

When libraries migrate to FOLIO, retain sort order from previous system

• In other systems, there is a sort order field that contains a numeric value that is updated based on a manual sort via the UI. We need to retain how the items are sorted from the previous system when libraries migrate to FOLIO

Not reviewed