Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
Jeff, a multibranch system with a Linux thin client setup We have heard of *many* problems with library systems that attempted running Evergreen in thin clients. They persisted to the point of most sites reverting back to bare-metal setups, and since then, we haven't heard much about it. Hope that's helpful! Chris -- Chris Sharp PINES System Administrator Georgia Public Library Service 1800 Century Place, Suite 150 Atlanta, Georgia 30345 (404) 235-7147
[OPEN-ILS-GENERAL] Reminder: web client hacking day tomorrow
Hi all, I'm sending along a reminder that tomorrow is the 2nd of two web client hacking days. The day was scheduled to give the community time to focus on activities to help get the web client ready for the trial production use in 2.12. This help can come in the form of working to resolve outstanding web client bugs, testing and signing off on bug fixes that have been submitted for review, and working on web client documentation. If there is anyone interested in testing and signing off on web client fixes, a list of patched available on mlnc1 are listed at the bottom of this e-mail(1). You can test them by pointing your browser to: https://mlnc3.noblenet.org/eg/staff/ Admin login: admin / evergreen123 The concerto dataset is loaded on the VM. https://wiki.evergreen-ils.org/doku.php?id=qa:concerto_logins You can follow the Bug Squashing Day procedures for testing and signing off at https://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing. If you're looking for a bug to fix and don't know where to start, further down in the e-mail(2) are previously-highlighted bugs that do not yet have code and require attention. Feel free to let me know if you have any questions! Kathy 1- Web client bug fixes ready for testing on mlnc3: Webstaff: Can't remove registered workstation at root of user's org/permission tree https://bugs.launchpad.net/evergreen/+bug/1648918 Web Client: Shared Copy Bucket Owner No Longer Displays https://bugs.launchpad.net/evergreen/+bug/1537223 webclient: Precat checkouts force a circ modifier https://bugs.launchpad.net/evergreen/+bug/1537217 Web Client: Patron Message Center Link Missing https://bugs.launchpad.net/evergreen/+bug/1534787 Paging controls needed at the bottom of the web client patron search https://bugs.launchpad.net/evergreen/+bug/1461739 2-Bugs without patches that need attention - Untranslated parts of web staff client - https://bugs.launchpad.net/evergreen/+bug/1629078 - Addressing this bug is critical to ensuring the web client can be rolled out (and tested) in countries where English is not the primary language. - Magical statuses not so magical - https://bugs.launchpad.net/evergreen/+bug/1616980 - Although this bug addresses some issues in the XUL client, the bug for the web client is a larger problem. In the copy editor, users can move copies in and out of statuses like Checked Out, In Transit, etc. These options were previously disabled in the XUL client. - Web client check-in "effective date" and check-out "specific due date" should also include times - https://bugs.launchpad.net/evergreen/+bug/1552778 - In addition, when using Edit Due date from the patron record, a time picker is available, but does not apply the selected time to the due date. Checkout auto renew age OU setting is not honored - https://bugs.launchpad.net/evergreen/+bug/1526163 Error when trying to pay by credit card - https://bugs.launchpad.net/evergreen/+bug/1622696 Marking item damaged does not trigger prompt for billing details - https://bugs.launchpad.net/evergreen/+bug/1659181 Alert Message field in the patron editor does not display in the web client patron summary - https://bugs.launchpad.net/evergreen/+bug/1659588 -- Kathy Lussier Project Coordinator Massachusetts Library Network Cooperative (508) 343-0128 kluss...@masslnc.org Twitter: http://www.twitter.com/kmlussier
Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
Josh, that's very interesting. One of our affected libraries makes heavy use of patron search for retrieving patrons. I found a bug report in Launchpad about patron search using up RAM: https://bugs.launchpad.net/evergreen/+bug/1110817 I did a quick test that seemed to confirm the issue; my findings have been added to the bug report. I'll need to do more testing and follow up with our other affected libraries to see if they use patron search regularly. Jeff On 2017-02-01 02:19 PM, Josh Stompro wrote: I've seen issues with using the patron search vs checkout. Patron search seems to leak memory. So I've seen issues where staff always go to patron search, even if they have a patron barcode, after a while the client will get unresponsive. Josh Stompro - LARL IT Director -Original Message- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jeff Davis Sent: Wednesday, February 01, 2017 3:43 PM To: open-ils-general@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client Our consortium has a few libraries where the Evergreen staff client periodically becomes unusably slow or freezes up altogether. I'm curious about other libraries' experiences with this problem. 1. Does the staff client slow down or freeze up regularly at your library? How often does it happen? Are there any noticeable patterns (e.g. are only circ stations affected, not cataloguing)? 2. How do you deal with the problem? We usually recommend limiting the number of open tabs, restarting the client periodically throughout the day, and increasing RAM. 3. If you use the web client, have you noticed an improvement? We suspect that the root of the problem is the ancient version of XULrunner used by the old staff client, but we haven't had the opportunity to compare the web client in production. -- Jeff Davis BC Libraries Cooperative
Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
I know of two sites on Windows 7 and a multibranch system with a Linux thin client setup. There may be a couple of others on one or another version of Windows. Jeff On 2017-02-02 07:14 AM, Mike Rylander wrote: Jeff, Is there an OS version that this happens on more often? I'm looking at you, Windows 10. Thanks, -- Mike Rylander | President | Equinox Open Library Initiative | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@equinoxinitiative.com | web: http://equinoxinitiative.org On Wed, Feb 1, 2017 at 4:43 PM, Jeff Daviswrote: Our consortium has a few libraries where the Evergreen staff client periodically becomes unusably slow or freezes up altogether. I'm curious about other libraries' experiences with this problem. 1. Does the staff client slow down or freeze up regularly at your library? How often does it happen? Are there any noticeable patterns (e.g. are only circ stations affected, not cataloguing)? 2. How do you deal with the problem? We usually recommend limiting the number of open tabs, restarting the client periodically throughout the day, and increasing RAM. 3. If you use the web client, have you noticed an improvement? We suspect that the root of the problem is the ancient version of XULrunner used by the old staff client, but we haven't had the opportunity to compare the web client in production. -- Jeff Davis BC Libraries Cooperative
Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
Having dealt with this same issue over the course of many migrations (but only a few weeks and only at the new site...) the OS doesn't matter. -- Jason Boyer MIS Supervisor Indiana State Library http://library.in.gov/ > -Original Message- > From: Open-ils-general [mailto:open-ils-general- > boun...@list.georgialibraries.org] On Behalf Of Mike Rylander > Sent: Thursday, February 02, 2017 10:14 AM > To: Evergreen Discussion Group> Subject: Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client > > This is an EXTERNAL email. Exercise caution. DO NOT open attachments or > click links from unknown senders or unexpected email. > > > Jeff, > > Is there an OS version that this happens on more often? I'm looking > at you, Windows 10. > > Thanks, > > -- > Mike Rylander > | President > | Equinox Open Library Initiative > | phone: 1-877-OPEN-ILS (673-6457) > | email: mi...@equinoxinitiative.com > | web: http://equinoxinitiative.org > > > On Wed, Feb 1, 2017 at 4:43 PM, Jeff Davis > wrote: > > Our consortium has a few libraries where the Evergreen staff client > > periodically becomes unusably slow or freezes up altogether. I'm curious > > about other libraries' experiences with this problem. > > > > 1. Does the staff client slow down or freeze up regularly at your library? > > How often does it happen? Are there any noticeable patterns (e.g. are only > > circ stations affected, not cataloguing)? > > > > 2. How do you deal with the problem? We usually recommend limiting the > > number of open tabs, restarting the client periodically throughout the day, > > and increasing RAM. > > > > 3. If you use the web client, have you noticed an improvement? We suspect > > that the root of the problem is the ancient version of XULrunner used by the > > old staff client, but we haven't had the opportunity to compare the web > > client in production. > > -- > > Jeff Davis > > BC Libraries Cooperative
Re: [OPEN-ILS-GENERAL] Limiting search options for a consortium?
I think that a quick extra note should be thrown out: As I understand it the configuration described below will apply to patrons at home as well as those in the library. If you just want to restrict in-library machines you may need a different solution. Thomas Berezansky Assistant Network Administrator Merrimack Valley Library Consortium 4 High ST, Suite 175 North Andover, MA 01845 Phone: 978-557-8161 -Original Message- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jeff Davis Sent: Wednesday, February 01, 2017 17:26 To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Limiting search options for a consortium? Hi Jesse, I believe there are two steps you need to take: (1) Set the physical_loc environment variable in the Apache config for each of your subdomains, using a directive like this: SetEnv physical_loc 4 (2) In your library settings, set "Org Unit Hiding Depth" to the appropriate value for each library. Here's the description for that setting: This will hide certain org units in the public OPAC if the Physical Location (url param "physical_loc") for the OPAC inherits this setting. This setting specifies an org unit depth, that together with the OPAC Physical Location determines which section of the Org Hierarchy should be visible in the OPAC. For example, a stock Evergreen installation will have a 3-tier hierarchy (Consortium/System/Branch), where System has a depth of 1 and Branch has a depth of 2. If this setting contains a depth of 1 in such an installation, then every library in the System in which the Physical Location belongs will be visible, and everything else will be hidden. A depth of 0 will effectively make every org visible. The embedded OPAC in the staff client ignores this setting. Hope that helps! Jeff On 2017-02-01 09:24 AM, Jesse McCarty wrote: > Hello Everyone, > > > > I was wondering if there are any configurations to restrict searches to > a single library in a consortium setup? We have four libraries in our > Evergreen system, all setup for access in sub-domains > (Burlington.skagitcat.org, laconner.skagitcat.org etc...). Occasionally > the search drop down gets switched/changed to search all the libraries > instead of the local library, which causes some confusion for patrons > looking for a book in our library when they don't realize the search > result is showing them a book in a different library. There any > configuration to eliminate the other options from the drop down box in > the web OPAC? Screenshot for reference attached, we would like to keep > the searches on the Burlington Public Library, but sometimes the box > gets set to Skagit Evergreen Libraries. > > > > Thanks in advance > > > > Jesse McCarty > > City of Burlington > > IT Technical Assistant > > >
Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
Jeff, Is there an OS version that this happens on more often? I'm looking at you, Windows 10. Thanks, -- Mike Rylander | President | Equinox Open Library Initiative | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@equinoxinitiative.com | web: http://equinoxinitiative.org On Wed, Feb 1, 2017 at 4:43 PM, Jeff Daviswrote: > Our consortium has a few libraries where the Evergreen staff client > periodically becomes unusably slow or freezes up altogether. I'm curious > about other libraries' experiences with this problem. > > 1. Does the staff client slow down or freeze up regularly at your library? > How often does it happen? Are there any noticeable patterns (e.g. are only > circ stations affected, not cataloguing)? > > 2. How do you deal with the problem? We usually recommend limiting the > number of open tabs, restarting the client periodically throughout the day, > and increasing RAM. > > 3. If you use the web client, have you noticed an improvement? We suspect > that the root of the problem is the ancient version of XULrunner used by the > old staff client, but we haven't had the opportunity to compare the web > client in production. > -- > Jeff Davis > BC Libraries Cooperative
Re: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client
We are noticing a similar and vexing problem at one of our newly migrated libraries. The staff client slows and throws a series of "Network not found," "String is not a function," and other random errors. We have verified that is not a latency problem caused by insufficient bandwidth. They have plenty. The PCs are new. No other libraries in our consortium are affected. Any insights would be appreciated. Thank you, Scott Scott Thomas Executive Director PaILS / SPARK (717) 873-9461 scott.tho...@sparkpa.org -Original Message- From: Open-ils-general [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jeff Davis Sent: Wednesday, February 01, 2017 4:43 PM To: open-ils-general@list.georgialibraries.org Subject: [OPEN-ILS-GENERAL] Slowness/freezing with XUL staff client Our consortium has a few libraries where the Evergreen staff client periodically becomes unusably slow or freezes up altogether. I'm curious about other libraries' experiences with this problem. 1. Does the staff client slow down or freeze up regularly at your library? How often does it happen? Are there any noticeable patterns (e.g. are only circ stations affected, not cataloguing)? 2. How do you deal with the problem? We usually recommend limiting the number of open tabs, restarting the client periodically throughout the day, and increasing RAM. 3. If you use the web client, have you noticed an improvement? We suspect that the root of the problem is the ancient version of XULrunner used by the old staff client, but we haven't had the opportunity to compare the web client in production. -- Jeff Davis BC Libraries Cooperative