Bug 3208 - Inactivity "timeout" for OPAC - enhancement idea
Summary: Inactivity "timeout" for OPAC - enhancement idea
Status: CLOSED DUPLICATE of bug 4238
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: rel_3_0
Hardware: PC All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-08 05:15 UTC by Chris Cormack
Modified: 2012-10-26 00:41 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Cormack 2010-05-21 01:07:42 UTC


---- Reported by adrea@moablibrary.org 2009-05-08 17:15:14 ----

Notes below are copied from the KOHA mailing list...

From Adrea...
"We have computers in our library which are only used as OPACs - we would like to set up these OPAC computers to clear search history/login info/cart contents etc. after a certain period of inactivity (perhaps 2-3 minutes).  So that when you sit down at an OPAC in the library you are not already logged into someone else's account. Does anyone have a solution for how to set this up?

We have already experimented with the "timeout" admin system preference.  It does not do the trick, because we do not want staff to be logged out of our staff module after a period of inactivity, and we do not want folks accessing their account from home to get logged out of their account automatically.  We just need a solution for the OPAC computers in the library.  Thanks for your help!"

1st response...  from Owen Leonard
"I think it'd be a great idea to create an OPAC timeout feature, and I
suspect it would be fairly easy to implement.  I would think you could
embed a meta refresh tag on each page with the timeout set via a
system preference. When the timeout was reached, the page would
redirect to the logout script. Unfortunately, logging out of the OPAC
doesn't empty the cart. I consider that a bug. Maybe we can get both
fixed at the same time.

The system I'm thinking of would necessarily apply to all OPAC
sessions whether they were inside the library or out. Perhaps that
means we need to build in some kind of warning message ("You are about
to be logged out. Click OK to continue your session").

I'm not sure how you'd set up the feature so that it only timed out
specific workstations."

Adrea - see the KOHA list archives from May 2009 for more comments... my library understands that there are issues with being able to clear the search history, but our library would like to see the following... cart is cleared, account is logged out, and browser page is redirected to the catalog home page.  Thanks!



---- Additional Comments From mary.moules@liblime.com 2009-06-01 18:23:23 ----

This is an enhancement that is also wanted by the Oyster River School District, so that the student's searches and cart contents do not display after they leave the OPAC.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 01:07 UTC  ---

This bug was previously known as _bug_ 3208 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3208

Unknown operating system Windows 2000. Setting to default OS "All".
Actual time not defined. Setting to 0.0
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here: chris@bigballofwax.co.nz.
   Previous reporter was adrea@moablibrary.org.
CC member bchurch@ptfs.com does not have an account here
CC member mary.moules@liblime.com does not have an account here

Comment 1 Christopher Brannon 2010-05-28 22:18:05 UTC
We would also love to see this feature.  It is a big security risk for the patrons.

Don't know why we couldn't have all OPACs time out.  Though, we could have it default to timing out when logging in, and have a checkbox on the login screen to tell it not to time out.
Comment 2 Owen Leonard 2010-12-23 16:38:36 UTC

*** This bug has been marked as a duplicate of bug 4238 ***