Closed (outdated)
Project:
Library
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Dec 2010 at 18:53 UTC
Updated:
25 Feb 2017 at 20:30 UTC
Jump to comment: Most recent
Comments
Comment #1
grahlAre you still experiencing this issue? I'm not able to see it on my end, the history tab seems to be sorted by date descending.
The function does have "ORDER BY lt.created DESC", so at least the db query is specifying it, not sure what is overriding it for you.
Comment #2
daengo commentedYes, I'm still having the issue. I see a couple of SQL calls like that in library.module. Which one are you referring to (what is the full query)?
At first glance it appears that my items are sorted correctly but as I scroll down the history tab I see 2011 to 2010 to 2009 and then back to 2011 to 2010 to 2009 leading me to think that it is going through each of my 10 copies of a specific item (our camcorders) and listed them by barcode, only the dang barcode isn't included in the query so I have no way to tell which copy is being referred to.
The table headers are just as below:
Date Transaction Notes Patron Due Date Actions
Without some sort of additional indicator in the table header the only that I can think of is to write a view, however, views support for this module is limited and doesn't allow specific barcode copies to show up (premise for one of my other posts). So, I see no way to tell that patron John Doe checked out camcorder #2 on such and such day and returned it on such and such day unless you create a new item and don't make use of the "Add an Item" feature which should be very handy. Do you have any suggestions or see a fix?
Comment #3
grahlWon't get fixed without a patch provided here.