Re: [OPEN-ILS-GENERAL] Deleting patrons(Obliterate) on 2.3.5 not working
Quoting Geoff Sams gs...@roanoketexas.com: I'm not even getting anything before the message I sent out. I get approximately 1 minute of frozen behavior(presumably working on obliterating) then the error message. This also occurs for non-staff users. Please report a bug on Launchpad: https://bugs.launchpad.net/evergreen Thanks, Geoff Sams Roanoke Public Library 817-491-2691 From: open-ils-general-boun...@list.georgialibraries.org [open-ils-general-boun...@list.georgialibraries.org] on behalf of Ben Shum [bs...@biblio.org] Sent: Wednesday, May 01, 2013 11:15 PM To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Deleting patrons(Obliterate) on 2.3.5 not working Hi Geoff, Hmm, so obliterating old staff accounts? On one of my systems, when I try to delete a staff account, it initiates a popup saying: The user you're attempting to delete has STAFF_LOGIN priviledges. Please enter the barcode for a destination user to receive the deleted user's miscellaneous staff artifacts (reports, etc.): And then if I input the user I want to meld all the staff data for, it begins trying to delete the patron, presumably. And then after awhile, it came up with a Javascript warning about a script running too long, which I clicked okay for, and then it popped up with a similar network/server failure as the one you saw. The staff account was not deleted; overall elapsed time was around 1 minute. My guess is there's some sort of timeout affecting things and the database is rolling things back instead of carrying through the purge process and shifting of data pieces. My system is running master as of 3/25/13, but if you're seeing it in your 2.3.5, then it might be broken in other branches too. I'd like to suggest reporting this as a bug to the Evergreen bug tracker: https://launchpad.net/evergreen Perhaps others can test this behavior as well and see if they get similar failures to confirm this to be a bug. -- Ben PS: Side note, the warning message has a misspelling for priviledges which should be privileges. Bite-size fix to the string later I guess. On 05/01/2013 07:34 PM, Geoff Sams wrote: Hello all, We have a few libraries in our consortium hoping to purge old staff records and deceased patrons and we are running into this error message when we try to make this happen: Network or server failure. Please check your Internet connection to roanoke.northtexaslibraries.org and choose Retry Network. If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogs. If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information: method=open-ils.actor.user.delete params=[077832adf0517284cfc5727fd583743c,289547] THROWN: null STATUS: I don’t believe this is a permissions issue, as our global admin account can’t even get this to work. I’m not sure what this could be otherwise, so I was hoping someone out there might be able to shine some light for me to point me in the right direction. Any help would be greatly appreciated. Thanks, Geoff Sams Roanoke Public Library 817-491-2691 -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113 -- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium
[OPEN-ILS-GENERAL] Disturbing FUD, more disturbing source
As you might imagine, the folks at ESI talk to a lot of Evergreen users, vendors and advocates in our work lives. Many or most are librarians, some customers of ours, some are orthogonal vendors, and some could be called competitors -- though I'd find it hard to think of another ecosystem of competitors where the buzz-word coopetition is more fitting. Over the last couple weeks several people have shared with us a strange bit of FUD. (For those not familiar with the term, FUD stands for “Fear, Uncertainty, and Doubt.” It's the practice of disseminating negative, and often vague or intentionally misleading information.) The people from whom we have heard say that they were told Evergreen cannot handle libraries of their size -- the library is just too big and complicated for Evergreen -- and they should just look elsewhere. The thing is, we're not talking about a 20-campus, 30-million item ARL with 15,000 serials subscriptions and 100,000-item/year EDI ACQ requirements. This was a medium sized library, with just a few branches and under 300,000 bibs, some light serials and ACQ requirements, and processes in the range of one million circs per year. Now, I bet many of you, like me, have heard things just like that before from, in particular, vendors of proprietary ILS'. As the success of Evergreen in libraries both large and small has continued, despite their best efforts to the contrary, that drum beat has, of course, died down a bit. The problem is, the claims we're hearing are being made by a vendor that purports to provide support, implementation, hosting, migration, training and development services surrounding Evergreen. The statements being related to us are patently false, and are being made to libraries that are either interested in using, or actively attempting to use Evergreen. When I heard this I was incredulous. Why would a group that claims to provide services surrounding Evergreen tell their prospective customers such provably false things to people who came to them for advice and direction? How could they be so wrong about the functionality and scaling capability of Evergreen? Why would they provide such factually incorrect advice and direction, instead of connecting the people with questions to folks that have answers? And, yes, they know where to find data, evidence and answers. I suppose, though, that it doesn't matter why. In the end, the only way to fight FUD is with the light of truth and evidence. So I ask that you all please join me personally and everyone else here at Equinox in actively pushing back against this sort of misinformation. Whether meant maliciously or not, the spread of misleading or downright false information hurts our entire community. Letting such things stand by not addressing them with facts will only allow those false statements to gain some amount of legitimacy through inertia. I don't want this email to be seen as a battle cry. While I have in the past and still do encourage everyone to write publicly, honestly and analytically about their successes -- and failures -- using Evergreen, to help us all collectively learn from each individual group's experiences, I'm not looking for that sort commitment or investment. I have three objectives today: to raise awareness of this specific issue, because it is so disturbing to me personally and harms us all in the end; to remind everyone on this mailing list that each of us has the opportunity to help spread the empirical, evidence-based information about Evergreen; and to request that those here in the community that feel they have a representative story with Evergreen to make themselves available for questions and clarifications. While I and my coworkers at ESI have the opportunity to talk privately to more community members that many others do, we are certainly not in an entirely unique position. If you hear of vague or misleading information being promulgated, please take a moment to politely address it. Or, if you don't feel comfortable or qualified to speak with specific evidence, you can always direct someone with inaccurate information to the community as a whole. We're a pretty accepting group, and we can answer pretty much any question if we know it's being asked. If it doesn't seem like a situation where a mailing list is appropriate, I am always happy to privately help clarify any misconceptions regarding Evergreen. I know there are others out there that also do this all the time, publicly and privately. If you're one of those people, and you are willing to risk being asked to spend even more time helping clarify and correct misconceptions, please let the rest of us know. So, I guess that is sort of a battle cry. I think, though, that this is a proper battle to pick. Thanks, all, -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web:
[OPEN-ILS-GENERAL] Barcode Scanning Problems
We are at 2.1 and are experiencing some issues with barcode scanning. Sometimes characters are dropped usually at the beginning or end of a barcode. This has been reported at several of the libraries in our consortia. They all use different barcode scanners of various vintage. In my own testing, I could detect no pattern to the scan problem. I did verify that, during testing, the scanner works perfectly when scanning barcodes into another application like MS word which rules out a problem with the scanner. Is this a problem that is isolated to our installation? Is it a known issue with 2.1? Any insights would be appreciated. Thank you. Scott Thomas Board of Directors PaILS (570) 207-2379 [cid:image001.jpg@01CE47F5.4E7393C0]http://www.palibrary.org/pails/ Pennsylvania's Statewide Library System inline: image001.jpg
Re: [OPEN-ILS-GENERAL] Deleting patrons(Obliterate) on 2.3.5 not working
Done deal! Thanks, Geoff Sams Roanoke Public Library 817-491-2691 -Original Message- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Jason Stephenson Sent: Friday, May 03, 2013 7:32 AM To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Deleting patrons(Obliterate) on 2.3.5 not working Quoting Geoff Sams gs...@roanoketexas.com: I'm not even getting anything before the message I sent out. I get approximately 1 minute of frozen behavior(presumably working on obliterating) then the error message. This also occurs for non-staff users. Please report a bug on Launchpad: https://bugs.launchpad.net/evergreen Thanks, Geoff Sams Roanoke Public Library 817-491-2691 From: open-ils-general-boun...@list.georgialibraries.org [open-ils-general-boun...@list.georgialibraries.org] on behalf of Ben Shum [bs...@biblio.org] Sent: Wednesday, May 01, 2013 11:15 PM To: open-ils-general@list.georgialibraries.org Subject: Re: [OPEN-ILS-GENERAL] Deleting patrons(Obliterate) on 2.3.5 not working Hi Geoff, Hmm, so obliterating old staff accounts? On one of my systems, when I try to delete a staff account, it initiates a popup saying: The user you're attempting to delete has STAFF_LOGIN priviledges. Please enter the barcode for a destination user to receive the deleted user's miscellaneous staff artifacts (reports, etc.): And then if I input the user I want to meld all the staff data for, it begins trying to delete the patron, presumably. And then after awhile, it came up with a Javascript warning about a script running too long, which I clicked okay for, and then it popped up with a similar network/server failure as the one you saw. The staff account was not deleted; overall elapsed time was around 1 minute. My guess is there's some sort of timeout affecting things and the database is rolling things back instead of carrying through the purge process and shifting of data pieces. My system is running master as of 3/25/13, but if you're seeing it in your 2.3.5, then it might be broken in other branches too. I'd like to suggest reporting this as a bug to the Evergreen bug tracker: https://launchpad.net/evergreen Perhaps others can test this behavior as well and see if they get similar failures to confirm this to be a bug. -- Ben PS: Side note, the warning message has a misspelling for priviledges which should be privileges. Bite-size fix to the string later I guess. On 05/01/2013 07:34 PM, Geoff Sams wrote: Hello all, We have a few libraries in our consortium hoping to purge old staff records and deceased patrons and we are running into this error message when we try to make this happen: Network or server failure. Please check your Internet connection to roanoke.northtexaslibraries.org and choose Retry Network. If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogs. If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information: method=open-ils.actor.user.delete params=[077832adf0517284cfc5727fd583743c,289547] THROWN: null STATUS: I don’t believe this is a permissions issue, as our global admin account can’t even get this to work. I’m not sure what this could be otherwise, so I was hoping someone out there might be able to shine some light for me to point me in the right direction. Any help would be greatly appreciated. Thanks, Geoff Sams Roanoke Public Library 817-491-2691 -- Benjamin Shum Open Source Software Coordinator Bibliomation, Inc. 32 Crest Road Middlebury, CT 06762 203-577-4070, ext. 113 -- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium
Re: [OPEN-ILS-GENERAL] Barcode Scanning Problems
Hello Scott, C/W MARS libraries also experience mis-scans. We are on 2.3 but experienced the problem in 2.1 and 2.2 too. Our libraries have a large variety of scanners so the problem is not scanner specific. We do know that the first scan in check in or in item status will drop the first character because the initial scan is bringing focus to the search box. I don't have answer but thought you would like to know the problem exists here too. Joan Joan Kranich C/W MARS Member Services jkran...@cwmars.org 508-755-3323 ext. 21 From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Scott Thomas Sent: Friday, May 03, 2013 11:57 AM To: 'open-ils-general@list.georgialibraries.org' Subject: [OPEN-ILS-GENERAL] Barcode Scanning Problems We are at 2.1 and are experiencing some issues with barcode scanning. Sometimes characters are dropped usually at the beginning or end of a barcode. This has been reported at several of the libraries in our consortia. They all use different barcode scanners of various vintage. In my own testing, I could detect no pattern to the scan problem. I did verify that, during testing, the scanner works perfectly when scanning barcodes into another application like MS word which rules out a problem with the scanner. Is this a problem that is isolated to our installation? Is it a known issue with 2.1? Any insights would be appreciated. Thank you. Scott Thomas Board of Directors PaILS (570) 207-2379 [Description: Description: Training | SPARK - Pennsylvania's Statewide Library System]http://www.palibrary.org/pails/ Pennsylvania's Statewide Library System inline: image001.jpg
Re: [OPEN-ILS-GENERAL] Barcode Scanning Problems
This may or may not be helpful, but here at MVLC we've had issues with barcode mis-scans for as long as I have been here, 10 years now. We had them on our previous ILS, and we still have them with Evergreen. The main difference that I see between the two systems, is that Evergreen will offer to make an precataloged copy with the mis-scanned barcode whereas the previous ILS made it more clear that there was a problem or more difficult to make the uncatalogued copy. Our members are very busy at the circulation desk, and I don't think most staff take the time to read and understand the box that comes up when they have a mis-scanned barcode. They seem to just hit whichever button makes the dialog disappear and the circulation happen the quickest. In the case of the mis-scan, this is the wrong button, since it creates the precataloged copy. No judgment is implied here. It's just my observation of what seems to be going on. -- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium -- Jason Stephenson Assistant Director for Technology Services Merrimack Valley Library Consortium
