Staff-forced Hold cancelation leaves no trace of staff who did it

[Chris Sharp]

Upon attempting to track down which staff are canceling holds, PINES staff discovered that this information is pretty much unavailable except through searching through system logs. One solution to this would be to record the staff member's username and the workstation name in the cancel_note field of action.hold_request. We should also be recording hold cancelation events in the Work Log (Administration -> Local Administration -> Work Log) at the workstation level.

Evergreen 3.8

[Mike Rylander (mrylander)]

Hi Chris,

How about a couple nullable foreign key fields, say, canceled_by and canceling_workstation, rather than adding text to the cancel_note field? That makes it reportable, and much easier for the software to do more useful things with.

[Terran McCanna (tmccanna)]

+1 to those two new fields

[Michele Morgan (mmorgan)]

This is a duplicate of bug 1501790 which proposed:

"two additional fields in action.hold_request, one storing the id of the user that performed the cancellation and one storing the workstation where it was performed.

These fields should be included as column choices in Holds grids."

I think it's fine to continue discussion here, so I'll mark 1501790 as a duplicate of this one. Just also want to note that the original was opened in 2015, so this is a long standing issue.

[Jennifer Pringle (jpringle-u)]

This comes up for us every now and then. The proposed additional columns would be very helpful.

[StephenGWills (swills)]

+1 to those two new fields

[Ruth Frasur Davis (redavis)]

Also big +infinity

[Chris Sharp (chrissharp123)]

I have an incomplete working branch here:

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/csharp/lp1963541_canceled_by_columns_ahr

It adds the columns to the table and the fieldmapper, but I got bogged down in the display in the AngJS/Angular interfaces. I'll hand this off to someone more skilled in those areas.

[Andrea Neiman (aneiman)]

Evergreen Indiana has contacted with Equinox to produce a fix for this bug.

[Jason Etheridge (phasefx)]

I've created an omnibus bug for this and other improvements at
https://bugs.launchpad.net/evergreen/+bug/2061136