My Opac Sorting of circ,circ_history,holds,holds_history - move to DB

Bug #1615129 reported by Josh Stompro
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

EG 2.10.5

The method of sorting the My Opac: Current items checked out, Check Out History, Items On Hold and Holds History has caused me problems when there are larger numbers of items to sort. We have customers that have 1000-5000 items in their circ history.

When the sorting is enabled the back end sends a copy of the copy, call_number and Biblio.record_entry data to the Apache Template Toolkit processor, which then sorts the data and throws away most of it, only displaying 15 items by default.

I believe that the method is used to be able to sort the title taking non-filing characters into account, it has a really nice feature that de-emphasizes the non-filing characters to make it clear to the customer why the title sorts like it does.

I'm interested in moving the sorting for this feature to the database, so the limit and offset can be handled there, and larger numbers of items can be handled more efficiently.

I'm wondering if one method might be to extend the reporter.super_simple_record materialized view to include the non-filing characters info. I can see that info being useful for other projects, shelf reading inventory lists for example?

Ideas? Thoughts? Concerns?

Thanks
Josh

Tags: opac sorting
tags: added: opac
Revision history for this message
Michele Morgan (mmorgan) wrote :

The result of the current method of sorting is that patrons with large circ histories see an Internal Server Error when attempting to sort their checkout history. In our consortium, we currently have about 500 patrons with circ histories larger than 500 items.

If this appropach would fix the functionality for our most avid circ history users, I'm all for it. Marking Confirmed.

Changed in evergreen:
status: New → Confirmed
tags: added: sorting
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.