Staff activity log
We occasionally have issues with staff abusing their ability to waive fines or deleting items inappropriately or accessing patron accounts outside of acceptable library operations. We would like to have a way to view these actions within a log file associated with each Sierra login (or filterable by login) so that these activities could be periodically audited by managerial staff and retroactively be reviewed when inappropriate system activities are believed to have taken place.
Robert Drake
shared this idea
-
Robert Drake
commented
The log files in the system currently have no way of tracking a given checkout to either a specific computer terminal OR to an individual sierra login. We occasionally have reason to need to confirm certain actions by staff members, but the log does not allow us to confirm what staff member performed a given circulation transaction except by stat code.
-
Lloyd Chittenden
commented
We have also had employees engage in malicious activity, like deleting items to implement their personal censorship. Logs of staff activity would have been invaluable.
-
Greg Smith
commented
This, along with a variety of other audit trail functions, would be a considerable benefit.
-
Kimberly Allen
commented
Audit trails protect both the user and the library. The downside is that they can devour disk space. You mentioned being able to retroactively review these. Is there a particular log retention period that would make sense to you?