Beth’s Blog

I don’t yet have the details on what went wrong or what the specific fix was, but RPA seems to have been pummeled into submission and is now validating patrons throughout the iBorrow realm again.
The most complete explanation I’ve gotten so far is:  “..the cookie setting in RPA has to be at least ‘5’”.  I have no idea what that means.  Or how it got to be less than five.  But I’ll keep asking.

The other news involves iBorrow/URSA updates and the next build.  The target date for the next release is early December.  We’ll see if they can convince us that Matt and I don’t need to pre-test it over a weekend.  So far, we are still a mite skeptical. 

As was the case with the previous build, the next one will focus on stability and reliability rather than flashy new features, but there will be some nice new stuff.  We should get a list next week, and we will pass it on via Email and post it here on Beth’s Blog.

–Al Carlson

Just so we wouldn’t get complacent, iBorrow has decided to mess with us again.

If you try to log in as a patron from East Lake, Palm Harbor, Sunline, Lee County, or Hillsborough County, you’ll get the error message that says:
“Invalid username and/or password, please login again”
Or you may get some variation on that wording.  The bottom line is that you won’t get in.

(If you log in as a Pinellas Park user, or one from Citrus, Hernando, or Collier, you’re fine.  Go figure.)

This seems to be a problem with RPA.  Peter Fripp and Sandy Schlueter have been working on it since yesterday (November 12), and we hope—but cannot guarantee—that they’ll have it fixed today.

Stay tuned for updates.  Contact me if you have questions.

–Al Carlson