Systems Update - February 17, 2017

Hello Libraries,

Here is you systems update a little earlier for the week of February 17th, 2017.


Floating Bugfix

Before, there were instances where an item could have its circulating library changed to an incorrect library: one outside of the floating group setup. This happened when a patron had checked out a floating item from a hold at another branch, went in to renew it, and the staff member would scan the barcode into the checkout box causing the prompt "Do you wish to checkin this item and then checkout?". In this workflow situation, the floating code would skip over some important checks and just change the circulating library to wherever this checkin/checkout happened. Annoying to be sure!

We are implementing the bugfix this weekend and it will be included in future versions of Evergreen:

Floating Collection Overview

For those who have not implemented it yet, floating collections basically work like this:

  • Items will change their circulating library depending on where they are checked in

This is setup -- in the case of Hood River and Baker -- for parts of the collections that libraries would like to have be checked in at a branch and stay there. The goal is to minimize transits and keeping collections more dynamic for branches within a system.


  • Item with Owning Library/Circulating Library = BCL/BCL


  1. Item gets put on hold for a patron at Baker Haines (BCL-HA)
  2. Item transits from BCL to BCL-HA to fulfill the hold
  3. Patron checks out the item at BCL-HA and then returns it to BCL-HA
  4. Instead of returning back to the original branch (BCL), the item stays at BCL-HA
    1. Its circulating library is changed to BCL-HA from BCL
  5. If the item is checked out by a BCL patron and returned to BCL, the item would have its circulating library changed back to BCL
    1. Basically, wherever the item is checked in within the system: there it will stay

There are a couple other ways floating can be configured, but its main use case it to have copies float to different branches within a system and stay there when they are checked in.

See: Official Documentation


Security fix to underlying system

Two important security fixes were released to the Evergreen community yesterday. See: Official blog mention.

The two fixes are relevant to Evergreen and the underlying communications system underpinning it (OpenSRF). The Evergreen security bits have already been updated and likely would not affect any of our current members at any rate (have to do with seeing credit card settings for libraries).

The underlying communications system will be upgraded this weekend in concert with the bugfix mentioned earlier. This will not change any configuration files of any type. There are some other important security features in this release that are important to get in as well.

Key Takeaways:

  1. There will be two upgrades this weekend
  2. These upgrades WILL NOT REQUIRE ANY STAFF INTERACTION with Evergreen
    1. No need to re-download the client or do anything on your end

Overview of "Welcome to the Library" email to patrons

Responding to comments from the Circulation Committee meeting earlier this week, I have modified the "Welcome to the Library" email for patrons. These are available to any library within Sage, but are currently disabled. The example below is modified specifically for UCSLD libraries, but can be changed to suit your library (although the less modifications the better smiley). If you wish to display an image in the email, the image has to publically accessible on the web. Example: Feel free to respond to with comments on the body text as well! I'm aware that not every library is a member of Library2Go, for example. But that would be removed for those libraries.

  • Patron signs up for account at library
  • Next day (around 4am) they receive a "Welcome to the Library!" email
  • The email (in its current iteration) will look like the following to a patron



Add new comment

Filtered HTML

  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <img>
  • Lines and paragraphs break automatically.

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.