http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3521
--- Comment #7 from Ian Walls <[email protected]> 2012-01-06 16:35:22 UTC --- Grouping by Branch is pretty solidly required. Whether that's home or holding branch is outside the scope of this fix. I'm not sure location and callnumber are appropriate for sorting; I see that more as incidental information, rather than 'scanning' information. When confronted with a long list of results (which usually happens if there are multiple volumes or other enumchron data), I would first scan for the volume/issue I want, then see where to go to get it (location and callnumber). I think that's the standard behaviour for patrons, but I could be mistaken. Nicole, I'm not seeing the problems you are, so I think this must be a data issue. Can you compare before and after this patch, and see if things are any worse for you? Because I'm getting a definite improvement on my test system, and if it's not causing any more of a problem, this may be a benign enough change to push (it's just a modification to the ORDER BY clause, after all) -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
