Anyone else have problems printing receipts when patrons reach a total of 10 items out?
From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Ryan Eby Sent: Wednesday, February 19, 2020 2:51 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Self Check login It hasn't caused any issues with at least Chrome. The session cookie seems fairly sticky, not surprisingly since Chrome cache seems to like to keep everything it can. That said 302 would have probably been the better choice. Ryan Eby ________________________________ From: "Daniel Wells" <dbwe...@gmail.com> To: "Evergreen Discussion Group" <open-ils-general@list.georgialibraries.org> Sent: Wednesday, February 19, 2020 5:35:38 PM Subject: Re: [OPEN-ILS-GENERAL] Self Check login These are pretty cool solutions, I think maybe it is time for us to stop logging them in every day :) Ryan, I have one question about your example config. Have you had issues using a 301 redirect rather than 302? It seems like that could potentially prevent the cookie from being set on reload, given that the browser may no longer hit the original link at all once it has received a 301 (until the cache clears). Sincerely, Dan On Wed, Feb 19, 2020 at 4:20 PM Ryan Eby <e...@aadl.org<mailto:e...@aadl.org>> wrote: Our solution is more technical and probably involved for 2 self-checks. The Windows script or URL options that were shared may be more useful but I thought I'd post just in case it is useful to someone. What we do is have the home/launch page of each self-check set to a URL like selfchecks.mylibrary.gov/station1<http://selfchecks.mylibrary.gov/station1>. This domain is hosted on an internal webserver with each URL location locked down to the IP or IP range of the self-checks. When the browser hits this URL it sets cookies for the username, password, and workstation and then redirects to the Evergreen self-check interface. Since this potentially allows anyone to login you'll want to make sure you lock down access to the URL and test. If it ever gets logged out for some reason then all is needed is a browser relaunch or home button click. Here is an example NGINX server config that has branch level URLs / ACLs: https://gist.github.com/eby/5dca1c51b2125a4ace822494fe59cd65 If you host Evergreen internally you should be able to do similar with the Apache2 used for your catalog. FWIW we have chrome kiosks and I'm not sure if Edge has any restrictions on cookies that would prevent this from working. We have the self-checks URL on the same root domain as the Evergreen catalog along with SSL which seems to be enough for Chrome for now. Ryan Eby Ann Arbor District Library ________________________________ From: "Millissa Macomber" <millis...@burlingtonwa.gov<mailto:millis...@burlingtonwa.gov>> To: "Evergreen Discussion Group" <open-ils-general@list.georgialibraries.org<mailto:open-ils-general@list.georgialibraries.org>> Sent: Thursday, February 13, 2020 7:52:03 PM Subject: [OPEN-ILS-GENERAL] Self Check login We are using the Evergreen self check. We have two touchscreen computers that we are running in kiosk mode with the Edge browser. They auto start and auto login to Windows. Unfortunately, they also still need us to type in the login and password for Evergreen. Does anyone know a way to eliminate the login screen? Or is there a way to have it auto login? My aim is to not need to have a keyboard/mouse with the computer. I tried to set the Workstation Required setting under Administration/Library setting to False but that didn't seem to change it. Thanks in advance for any suggestions. Millissa Macomber Technical Services Coordinator Burlington Public Library 820 E. Washington Ave., Burlington, WA 98233 millis...@burlingtonwa.gov<mailto:millis...@burlingtonwa.gov> 360-755-0760
