Wishlist: Reporter Source for Offline tables
Bug #2066974 reported by
Elizabeth Davis
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
As of 3.11.5, there is no Reporter source for the Offline tables. It would be helpful to staff client administrators to be able to report out use of the offline mode for troubleshooting.
To post a comment you must log in.
Copying Galen Charlton's additional info from the Evergreen-Reports mailing list on 5/23/2024:
There are two underlying database tables involved, offline.script (which has a row for each file loaded into an offline session) and offline.session (which has a row for each pending and completed session).
They're not the friendliest of tables to work with - in particular, their date/time fields are integer columns that store seconds since the Unix epoch rather than being true timestamp columns, and they don't have foreign key constraints. That said, with direct SQL access, they are enough to write reports on which libraries and staff members are using offline, when they processed transactions, and how many transactions were processed. The to_timestamp() SQL function can be used to deal with the date/time fields, e.g.,
SELECT to_timestamp( create_ time) FROM offline.session ORDER BY 1 DESC LIMIT 5;
They're also not set up as reporting sources, but there's no technical barrier to a small enhancement to make them accessible to the reporter (though converting those tables' date/time columns to the timestamp type would be a nice thing to do at the cost of some more work in the code that actually does offline processing).