Evergreen ILS

Open Source Library Software

Downloads

Download files, Git repositories, installation instructions...

Downloads →

Documentation

Official documentation, community wiki, and other resources...

Documentation →

Get Involved

Events, mailing lists, IRC, and more. Join our community!

Community →

Evergreen 2.11.6 and 2.12.3 released

The Evergreen community is pleased to announce two maintenance releases of Evergreen: 2.11.6 and 2.12.3.

Evergreen 2.12.3 includes the following bugfixes:

  • Web staff client fixes
    • The receipt on payment checkbox now prints a receipt at time of payment.
    • The Items Out count in the patron screen now includes long overdue items.
    • A fix was added to prevent values from a previously-edited patron from appearing in the edit form of a subsequent patron.
    • User notification preferences now save correctly in the patron registration and edit forms.
    • The UPDATE_MARC permission is no longer requested when performing a search from the staff catalog.
    • Non-cataloged circulations now display in the Items Out screen without requiring a refresh.
    • Required statistical categories are now required to be entered in the copy editor. (A similar bug for the patron editor was fixed in the 2.12.1 release).
    • Voiding bills now requires confirmation.
    • Staff can no longer use the copy editor to put items into or out of the following statuses: checked out, lost, in transit, on holds shelf, long overdue, and canceled transit.
    • The contrast is improved for alert text showing the amount a patron owes in bills.
    • Circ modifiers now sort alphabetically in the copy editor.
  • Other bugfixes
    • Code to prevent a hold already on the Holds Shelf from being transferred to another title.
    • A fix to a bug that prevented users from scheduling reports with a relative month if the report template used a date that applied the Year
      Month transform with the On or After (>=) operator.
    • A fix to a bug where the max fines threshold was reached prematurely due to the presence of account adjustments.
    • A check that prevents a SMS message from attempting to sending when the SMS carrier is null.
    • For systems that provide search format as a filter on the advanced search page, a fix so that the format selected in the search bar when launching a new search from the results page overrides any previously-set formats.
    • The addition of an optional new Apache/mod_perl configuration variable for defining the port Apache listens on for HTTP traffic. This resolves an issue where added content lookups attempting HTTP requests on the local Apache instance on port 80 failed because Apache was using non-standard ports.
    • A fix to the public catalog’s My List page responsive design so that it now displays properly on mobile devices and allows users to place holds from My List.
    • A fix to a bug where the second (and subsequent) pages of search results in the public catalog (when group formats and editions is in effect) does not correctly generate links to hits that are not part of of a multi-bib metarecords.

Evergreen 2.11.6 includes the following fixes:

  • Code to prevent a hold already on the Holds Shelf from being transferred to another title.
  • A fix to a bug that prevented users from scheduling reports with a relative month if the report template used a date that applied the Year
    Month transform with the On or After (>=) operator.
  • A fix to a bug where the max fines threshold was reached prematurely due to the presence of account adjustments.
  • A check that prevents a SMS message from sending if the SMS carrier is null.

Please visit the downloads page to view the release notes and retrieve the server software and staff clients.

Evergreen 3.0 development update #10

Ducks and geese. Photo courtesy Andrea Neiman
Since the previous update, another 8 patches have been committed to the master branch.

As it happened, all of the patches in question are concerned with fixing various bugs with the web staff client. Evergreen 3.0 will round out the functionality available in the web staff client by adding support for serials and offline circulation, but a significant amount of the effort will also include dealing with bugs now that some libraries are starting to use the web staff client in limited production as of version 2.12.

Launchpad is, of course, used to keep track of the bugs, and I would like to highlight some of the tags used:

  • webstaffclient, which is a general catch-all tag for all bugs and feature requests related to the web staff client.
  • webstaffprodcirc, which is for bugs that significantly affect the use of the web staff client’s circulation module.
  • fixedinwebby, which is for bugs that are fixed in the web staff client but which have a XUL client side that will likely not be fixed. As a reminder, the plan is to deprecated the XUL staff client with the release of 3.0 and remove it entirely with the Fall 2018 release.

Duck trivia

Even ducks were not immune to the disco craze of the 70s.

Submissions

Updates on the progress to Evergreen 3.0 will be published every Friday until general release of 3.0.0. If you have material to contribute to the updates, please get them to Galen Charlton by Thursday morning.

Evergreen to Highlight Innovative Catalog Features at ALA

The Evergreen community will be highlighting some of the ways the Evergreen catalog helps users find the material that they need at the American Library Association Conference in Chicago later this month.

It’s a Popularity Contest — Innovation in the Evergreen Catalog is scheduled for 4:30 to 5:30 p.m. Saturday, June 24 in room W177 in McCormick Place. Elizabeth Thomsen of the North of Boston Library Exchange (NOBLE) will be facilitate the session.

If you’re attending ALA, please join us for this meetup. Even if you’re not attending ALA, please share this information with others in your Evergreen library / consortium so that they know of this opportunity to learn about these features and to meet with other Evergreen users and those who are interested in using Evergreen.

In this session, we’ll look at features that help users find the material they want. The use of popularity data to enhance the relevance of search results is just one new feature in the Evergreen library system catalog. In addition to recent circulations, relevancy in Evergreen can be enhanced by taking into account the number of copies held, the number of holds, or newness. The factors offer a range of possibilities that can be customized for each library’s needs and clientele, and are available in Evergreen’s current release.

Also in the most recent release, Evergreen has improved on its long-standing ability to group formats and editions. Wading through long pages of search results that are primarily different formats and editions of the same work can be tedious for users. With Evergreen, the catalog is able to help the user find the work they’re seeking in fewer screens before narrowing in on the specific edition they want. Even better, if they don’t care about an edition, Evergreen will allow them to place a hold across multiple editions of a work to make the process easier for them.

Evergreen has built upon this popular feature by adding quick links in the record to other formats and editions of the work.

Attendees are also encouraged to ask other questions about Evergreen or the open-source community that supports it.

We hope to see you there!