Comprehensive Audit Trail for System Administration Changes
Implement a detailed and accessible audit log for all configuration changes made within the Polaris ILS System Administration (SA) and "adjacent" modules.
Description of the Problem
The Polaris ILS lacks a granular, searchable audit trail for System Administration changes. This makes it difficult to determine who made a specific change, when it occurred, and what the previous setting was. This ambiguity hinders troubleshooting when a configuration error occurs, complicates training, and reduces accountability.
Proposed Solution
A comprehensive, transaction-based audit log that automatically records the following data for every saved change in the SA module:
Timestamp: The precise date and time of the change.
User Account: The Polaris username of the staff member who made the change.
Workstation: The name of the workstation from which the change was initiated.
Configuration Area: The specific parameter modified (e.g., "Receipts - Fines," "Patron Services - Loan Period").
Previous Value: A record of the setting's value before the change.
New Value: The setting's value after the change.
This log should be presented in a searchable interface, allowing administrators to filter events by date, user, and configuration area.
Initial Focus for Implementation
For an initial release, prioritize the audit of settings that can be modified by general staff, not just system administrators. A key area is workstation-specific settings, such as receipt configurations. Because System Administration access is typically restricted to a few users, changes made in more broadly accessible areas are often more frequent and difficult to trace. Focusing development on these staff-level settings first would offer the most immediate value in improving accountability and simplifying troubleshooting.
Justification
While the storage and processing constraints of 1997 may have made detailed logging impractical at Polaris's inception, modern server infrastructure can easily handle this function. Implementing this feature would align Polaris with current enterprise software standards where robust auditing is critical for system integrity and security.
Benefits:
Rapid Troubleshooting: Quickly identify the source of problems caused by configuration errors.
Clear Accountability: Create a definitive record of all administrative actions.
Simplified Reversal: Know the exact previous value to accurately restore a setting.
Enhanced Security: Provide a crucial tool for security audits and investigations.
Use Case Example
If a library's hold pickup notices suddenly aren’t printing for one workstation, an administrator could use the audit tool to filter for recent changes to "Receipts." The log would immediately show which user modified the settings and when, displaying both the old and new settings. The administrator could then use the "Previous Value" information to instantly revert the setting.

-
Eric Young commented
This feature is critical for maintaining system integrity and accountability. Without a detailed, searchable audit trail, we’re left guessing when something breaks or changes unexpectedly. Requiring admins to enter a short comment when saving a setting, such as a ticket number or reason, would add essential context. These notes should be stored and searchable alongside the change log. This would significantly improve traceability, support workflows, and align Polaris with modern administrative standards.
-
Emma Olmstead-Rumsey commented
This is really important! Especially in a larger system or consortium where you have multiple sysadmins. I am currently training a new person and it's very difficult to gauge what he has and has not mastered since I can't trace changes back to any individual staff member in most cases.