Bug 38122 - Cannot sort holdings table by status
Summary: Cannot sort holdings table by status
Status: In Discussion
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 33568
Blocks:
  Show dependency treegraph
 
Reported: 2024-10-08 14:50 UTC by Lucas Gass (lukeg)
Modified: 2025-01-24 18:20 UTC (History)
16 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucas Gass (lukeg) 2024-10-08 14:50:02 UTC
Bug 37334 will bring filtering to the holdings table status column. This bug is for the sorting of the status column.
Comment 1 Kristi 2024-10-31 15:17:48 UTC
Our staff are anxious to have this restored! They use the sort on bibs that have more than 20 items, some that have over 100.
Comment 2 Nick Clemens (kidclamp) 2024-11-07 15:45:43 UTC Comment hidden (obsolete)
Comment 3 Jonathan Druart 2024-11-07 16:01:13 UTC
(In reply to Kristi from comment #1)
> Our staff are anxious to have this restored! They use the sort on bibs that
> have more than 20 items, some that have over 100.

Can you detail your use case please?
Comment 4 Kristi 2024-11-08 14:41:19 UTC
We have several use cases:

1.Branch staff sort by status to see if they can identify an available copy and the branch it’s located at.

2. Our acquisitions team uses it to see how many viable (not missing, lost, withdrawn) copies are left on something that has high holds. Popular titles can have over 100 items.

3. Technical services uses it when looking at items that need to be called in to see if they are checked out, marked missing, etc.

4. We have wi-fi hotspots that are very popular and have several hundred items on the bib for each model. A lot of them are marked damaged, others are long overdue (Lost), some are Missing. These different statuses can make it confusing to know what should be circulating, so our staff use the status sort to eye up what is damaged, missing, etc.
Comment 5 Jonathan Druart 2024-11-13 10:12:01 UTC
Don't you think bug 37334 would help in most of those situations?
Comment 6 Kristi 2024-11-13 13:58:47 UTC
For use cases 1 and 2 especially, the sort rather than the filter would be the preferred method.
Comment 7 SamSowanick 2024-11-25 18:21:23 UTC
Our staff would love this feature back too. They find it easier to quickly scan the items over filtering. But ideally there is room for both :). Upvoting.
Comment 8 Jonathan Druart 2024-11-26 08:36:47 UTC
I prefer to be honest with you, there is very little chance to see the sort implemented in a near future. It was an limitation of bug 33568 that has been announced since day 1.

I will do my best to provide alternative solutions that can potentially answer your needs however.

(In reply to SamSowanick from comment #7)
> They find it easier to quickly scan the items over filtering.

Can you detail what you mean here please?
Comment 9 SamSowanick 2024-11-26 18:49:02 UTC
The sort function is a way to group the items allowing scanning over all the items at one time, allowing seeing proportions of items status on one bib. Filtering accomplishes this but requires you to know what status you are looking for; while also hiding other items not in the searched status.

I also just realized that you can SHIFT + CLICK to sort two fields at the same time, so it is fully possible that I am missing an alternate something.

I will see if I can get more context from our staff.

Thank you for highlighting the context to the limitations for this bug.
Comment 10 Donna 2024-12-19 20:47:57 UTC
Sorry - I'm not fluent in all the tech stuff, so it might be something obvious.  But if all the other columns on the holdings table are sortable, why is status the only one that is not?
Comment 11 Jonathan Druart 2025-01-06 10:23:26 UTC
(In reply to Donna from comment #10)
> Sorry - I'm not fluent in all the tech stuff, so it might be something
> obvious.  But if all the other columns on the holdings table are sortable,
> why is status the only one that is not?

Because it's calculated, not stored in DB like other attributes.

If you want to sort by status you will need to calculate the status for all the items then display the 20 you want to display.
Comment 12 Lucas Gass (lukeg) 2025-01-13 21:38:53 UTC
(In reply to Jonathan Druart from comment #8)
> I prefer to be honest with you, there is very little chance to see the sort
> implemented in a near future. It was an limitation of bug 33568 that has
> been announced since day 1.


Unfortunately this is not an option. Before Bug 33568 one could sort by statuses, this is a regression and many libraries cannot live without it.
Comment 13 Lucas Gass (lukeg) 2025-01-13 21:39:43 UTC
I can work on this after we get Bug 37334 pushed.
Comment 14 Jonathan Druart 2025-01-14 05:04:47 UTC
(In reply to Lucas Gass (lukeg) from comment #13)
> I can work on this after we get Bug 37334 pushed.

What are you plans?
Comment 15 Marie-Luce Laflamme 2025-01-14 17:28:16 UTC
Please bring back the "sort by statuses" option.
Comment 16 mreid 2025-01-22 20:22:32 UTC
Please restore ability to sort the holdings table by status. This is particularly an issue for our bibs with large holdings (up to 150 items) across multiple branches. Staff appreciated being able to sort by status to quickly eyeball the list and determine which branch has available items; we also have use cases similar to those listed by Kristi on 11/8/24, particularly with our hotspots and laptops.
Comment 17 Lucas Gass (lukeg) 2025-01-22 20:58:13 UTC
(In reply to mreid from comment #16)
> Please restore ability to sort the holdings table by status. This is
> particularly an issue for our bibs with large holdings (up to 150 items)
> across multiple branches. Staff appreciated being able to sort by status to
> quickly eyeball the list and determine which branch has available items; we
> also have use cases similar to those listed by Kristi on 11/8/24,
> particularly with our hotspots and laptops.

Have a look at Bug 37334. Filtering by available and then sorting by branch may solve your problem.