Item Status List View Displays Incorrect Due Date

Bug #1754654 reported by Robert J Jackson
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Undecided
Unassigned

Bug Description

Web Client 3.0.5

If the item being displayed has multiple circs then the oldest circ is used to display the Due Date from.

The Legacy Staff Client uses the most recent circ for this data as desired.

In example screen shots shown there are 5 circs total - the date on web client is from the oldest circ. The date shown on legacy is the most recent (desired) circ.

Revision history for this message
Robert J Jackson (rjackson) wrote :
Revision history for this message
Robert J Jackson (rjackson) wrote :

Adding second screen shot of legacy staff client with correct due date displayed.

Revision history for this message
Terran McCanna (tmccanna) wrote :

There was a fix for this in 3.0.4:

https://bugs.launchpad.net/evergreen/+bug/1743819

Revision history for this message
Steve Callender (stevecallender) wrote :

I've also discovered this bug. The fix listed by Terran did correct a previous display issue with due dates, but this one appears to remain and both Robert (3.0.5) and I (3.0.4) are testing this on releases that contain that bug fix.

Just to add to Roberts initial findings, I don't believe it's actually the oldest circulation. It may at times be, but it doesn't look like that's consistent.

The due date it's pulling for the item status screen is basically the very first record the database spits out from the action.all_circulation_slim view.

So to test, just take your copy id and,

select * from action.all_circulation_slim where target_copy =XXXXXXX limit 1;

That appears to be the due_date that's going to be put on the screen.

That may of course be the oldest record, but not always depending on how the database decides to display things.

Revision history for this message
Steve Callender (stevecallender) wrote :

Apparantly it's not just the due date field, also seeing the exact problem with circulation library. I imagine just all the fields on this screen are coming from the very first record retrieved when doing a,

select * From action.all_circulation_slim where target_copy = XXXXXXX limit 1;

tags: added: webstaffcolumns
removed: webstaffclient
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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