Add Last Login attribute to Users subject area in Analytics
The current Staff Login Report in Alma Configuration is of limited use, in that it doesn't provide additional details about users beyond Primary ID and last login date. In Analytics, we can find full details about named users, but cannot determine which accounts are actively used without the "Last Login Date" field.
We would like to see the Last Login Date--i.e., the last date a user logged in to Alma to perform staff activity--added as an attribute to the Users subject area in Analytics. Having this date along with users roles and expiration dates will help our libraries better manage their named users without having to combine multiple excel reports to get the same information.
This will benefit institutions that need to closely monitor the number of named users to stay within contracted user limits.
-
Stacey van Groll commented
I agree with you that this would be a very useful enhancement. Until it's added as you suggest, there is potentially a workaround via the Events (being deprecated in Dec 2021) / System Events (replacement for Events) subject area. This has an Event type 9110 of Successful login, with a Creator of the Primary ID of the user. You could build this report first, and then use it to filter another report in the Users area by the Primary ID. Obviously more timeconsuming to set up than the Last Login simply being in the Users area, but at least it's something for right now. Be aware that the 1 hour timeout of Alma can trigger additional logins which you may not expect, depending on your authentication method ie you might find data of the same staff member repeatedly logging in throughout the day in a strangely consistent manner, but if you look at the Event Date and Time field, you are likely to set that it's in increments of the 1 hour timeout.