Bug 5594 - Option to configure default sort order for items on bib records
Summary: Option to configure default sort order for items on bib records
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P2 enhancement with 21 votes (vote)
Assignee: Bugs List
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-07 17:19 UTC by Nicole C. Engard
Modified: 2023-10-02 13:07 UTC (History)
14 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-01-07 17:19:00 UTC
It would be nice if there was a preference for the sort in which items are sorted in the OPAC. I know that there is a table sorter on that table, but the default is the order in which items are added and sometimes that can be a problem with serials and users don't always see the sorter - so letting the librarians say what order they want them to appear in would be a nice little feature.
Comment 1 Eric Phetteplace 2016-08-06 16:30:22 UTC
This is particularly a problem with serials with a large quantity of items attached to a single bib record: the default sort is by item type, which isn't too helpful, but also sorting on almost *any* column results in a pretty random listing. For instance, sorting on the issues column results in a lexical sort like this:

v. 1 1999
v. 10 2009
v. 11 2010

etc., the issue strings are ordered lexically. The more appropriate ordering would be to sort by volume number first and then the issue number. Or—as Nicole implied in her original comment—add an additional item record field for how it's to be sorted in the holdings table, so we could at least manually add an appropriate ordering.
Comment 2 Jana Doyle 2018-07-10 14:28:07 UTC
Agreed, Eric. Some of our serials have thousands of items, in multiple locations, and multiple copies.  It is time consuming for staff to find items, check in new issues and do maintenance (withdraw or relocate items) in this environment. This enhancement is of high importance to us.
Comment 3 Katrin Fischer 2018-07-14 12:01:28 UTC
For the default sort order there is: OPACHoldingsDefaultSortField

But I tihnk this is more about having a better sort for enumchron? 

This is sorted  alphabetically right now, anything else is hard for a free text field. If enumchron was created by serials, we could maybe use fields from serial to sort better, but that would not be an easy development I think.

Should we change the bug title to refer to enumchron specifically or move this to a separate bug maybe?
Comment 4 Katrin Fischer 2018-07-14 12:21:37 UTC
Ah, actually we got a bug already for sorting on volume information: bug 13420
Comment 5 Brian 2018-12-15 18:32:24 UTC
Any updates?

Carnegie team
Comment 6 Marjorie Barry-Vila 2019-03-01 19:51:05 UTC
+1
Comment 7 Fridolin Somers 2022-08-11 01:29:34 UTC
On of our librarian reported this also, for serials.
I have no clue how to create a good patch.
Comment 8 Katrin Fischer 2022-08-13 21:42:20 UTC
I think this bug isn't where it needs to be. 

It asks for being able to sort, but doesn't give enough specifics. We do have:

* System preference OPACHoldingsDefaultSortField
* Automatic sorting on the published date if the items are linked to a subscrpition

This needs to be clearer about what is missing in order to go further. The bug description is too general and would cover what the pref does.
Comment 9 Noémie Labine 2023-01-12 15:08:18 UTC
Hi,

A library asked for a way to sort the items table by call number so I believe it would be link to this bug ? Not only be able to sort by call number as we are able to do with the table sorter but instead being able to choose either one of the table columns to always sort the table.

So I believe the easiest way to have that would be to add options to OPACHoldingsDefaultSortField to have :

- First column
- Holding library
- Home library
- Call number
- barcode
- Shelving location
...
Comment 10 Catrina Berka 2023-02-16 19:03:49 UTC
In addition to setting the default sort order on the OPAC (holdingst), we should also have the ability to set the default sort order on the staff client (holdings_table). The ability to set the default sort order exists on some tables but it would be nice to extend this capability to both holdings tables as well. 

As noted by other comments here, the existing options (first column, home library, home library) in OPACHoldingsDefaultSortField are too limited, especially for Serials.
Comment 11 Katrin Fischer 2023-08-27 13:27:48 UTC
(In reply to Catrina Berka from comment #10)
> In addition to setting the default sort order on the OPAC (holdingst), we
> should also have the ability to set the default sort order on the staff
> client (holdings_table). The ability to set the default sort order exists on
> some tables but it would be nice to extend this capability to both holdings
> tables as well. 
> 
> As noted by other comments here, the existing options (first column, home
> library, home library) in OPACHoldingsDefaultSortField are too limited,
> especially for Serials.

Hi Catrina, I think configurable sorting for the staff interface would be good in a new, separate bug.
Comment 12 Irina 2023-09-25 11:31:10 UTC
Has the new, seperate bug been made?

The staff interface: It would be nice to be able to change which of the two columns, the holding branch (current library) or the home library, would be automatically in alphabetical order. Now it's the home library, but the holding branch would be more helpful in customer service.
Comment 13 Nicolas Legrand 2023-10-02 13:07:48 UTC
Some people at the BULAC library would like something like this also :).