Timeout should be configurable
Timeout should be configurable to allow for longer timeout than 60 min. This would be helpful for staff who work for example in areas like information services where you need to use Alma several times during the day but not continuously
-
Berthold Kreß (SuStB Augsburg) commented
Dear Mr Beladev,
many thanks for looking into this. 150 minutes would be a great improvement - but I wonder if one should not offer another, longer, option, e.g. 480 minutes.
Use case: a colleague is working on a tricky cataloguing problem at her desk. Then, she is learns that the colleague who had a 3-hours-shift at the issue desk has suddenly fallen ill and has to cover immediately, since there is already a queue. After the shift, and probably a lunch break, she wants to return to the problem. -
D.J. commented
Sometimes a session expires much faster than in 60 minutes which would be even quite long ... So the suggestions of ExLibris seem to be very promising. Let us see if the promise can be kept ...
-
Brady Cross commented
I would suggest going as far as 8 hours. Ideally, I would like to be able to select the timeout setting per user. Frontline student assistant staff may need shorter timeouts (15 to 30 minutes) whereas technical service staff would benefit from an extended timeout (8 hours). It would be OK if the timeout configurations were associated per role (manager has longer timeout than student assistant staff).
-
Jason Weisgerber commented
Definitely would like this useful, configurable capability.
-
E Sproat commented
We too very much need local configuration for timeout.
-
Troy Evans commented
+1
-
Anonymous commented
Yes, please allow timeout to be configurable.
-
Katie Utschig, SWITCH Library Consortium commented
Itai, can you explain the security issue?
-
G.W. Swicord commented
We should have the option to disable timeouts completely. I am in and out of Alma all the time and often need to work on queries across a period of days. I suspect I'm not the only user who doesn't log out of their Windows session during the work week.
-
Karen Benko commented
Manu Schwendener, There are not two settings. Unchangeable aspects of the software are not "settings." We want Alma to stay open longer.
Text from the first of the two links at the idea you linked to on 5 March at 3:08: "Answer
Session timeout is set to 60 minutes, at which time the session will expire and staff are required to sign in again. This is not configurable." -
Manu Schwendener commented
-
Manu Schwendener commented
-
Brady Cross commented
Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.
-
Brady Cross commented
Allow us (me) to configure how long Alma may be idle before timing out. The current setting is far too short. Sometimes I will be in the middle of working and have to step away to assist a team member and when I return to my desk, I've lost my search/progress or just plain have to start over.
-
Anonymous commented
I am agreed.
-
Mervi Löytynoja commented
Absolutely! I also vote for this!
-
Manu Schwendener commented
+1
-
Laurie Swartwout commented
Definitely in favor of the enhancement to make timeout configurable! There are many situations within a library where interruptions happen and starting over from scratch after having made significant progress on a task is a waste of time.
-
Ann Owen commented
I too vote for this enhancement. I'm new to Alma and this is absolutely a necessity.
-
Due to security needs we can't increase the timeout period.
It is possible to consider adding warning message enough time before expiration that will enable you to reset the timeout counting