User Tools

Site Tools


Evergreen Newsletter / June 2012

Evergreen 2.2 / by Suzannah Lipscomb, ESI

Evergreen is in full bloom with all of the new or enhanced functionality in the upcoming release of version 2.2! If you have downloaded version 2.2 to test, you have probably noticed many of these new features. Below, listed by module, are some of the highlights. You can learn more about much of this functionality by reviewing the end user documentation on Equinox Software’s website at: Additionally, Equinox provides a wide range of training options to suit a variety of needs and budgets.

It takes a village (or specifically the Evergreen Community in this case) to make any Evergreen release possible. Many individuals and organizations played an integral role in the creation of version 2.2, by assisting in numerous ways and/or sponsoring development efforts. A special thanks to the following parties for sponsoring development: Berklee College of Music, Bibliomation, Georgia Public Library Service, King County Library System, NC Cardinal, Pioneer Library System, and Unique Management Services, Inc. For your next Evergreen or Koha software development project, please consider the open source experts at Equinox Software.

Staff Client navigation: • Unlimited tabs • Line numbering

OPAC: • Integration of Tpac • Autosuggest • Recent Staff searches • My Lists • SMS text messaging for hold notifications & call numbers • Numeric search

Circulation: • Patron search: the wording has changed, but the functionality is still the same. Retrieve patron by record ID is now retrieve patron by database ID. • Ability to double click a patron record to retrieve it • New user settings including: o Collections exempt (to prevent patron accounts from going to collections) o Default hold pick up location o Default phone number o Hold notification format • New Check in modifiers including: o Clear Shelf-Expired Holds o Retarget Local Holds o Retarget All Statuses o Capture Local Holds as Transits • Ability to sort columns on the pull list in a variety of ways Cataloging: • Retrieve title by record ID is now retrieve title by database ID (Only the wording has changed, the functionality is still the same.) • New button allows return to search results from editing the MARC record of an item • Ability to hide fields in the copy editor • Authority control sets • New ways for Staff to request items including: o Recall hold o Force hold • Z39.50 enhancements including: o Mark local record as the overlay target o Restrict z39.50 sources by permission (thru server admin) • Batch import of MARC records including: o Record match sets help prevent duplication of records in the catalog o Quality metrics to ensure quality of incoming record o Additional batch import options, like copy to bucket

Acquisitions: • Ability to receive items directly from an invoice • Staff have the ability to enter patron requests • Vandelay integration with MARC batch upload (includes collision detection)

Serials: • Libraries can choose to display holdings by enumeration or chronology

Server Administration: • Custom org unit trees • MARC search /facets field • User activity types allows Staff to specify which activities to record in the database, like OPAC login • Actor & Asset STAT Cat SIP fields – custom fields for statistical categories which return information to third parties regarding either patrons or items • Circulation limit groups and circulation limit sets: Staff can use these in conjunction to limit by circ modifier the number of items patrons can checkout • Ability to configure SMS carriers • Org unit setting that is integrated with the hold targeter to allow items at closed locations onto the potentials list Local Administration: • Can set address alerts for specific addresses • Barcode completion for items or users • Stat cat editor o archive with circs – allows reporting on stat cats minus identifying information o show in patron record summary o allow free text • Copy location groups create custom locations that patrons can search in the OPAC

Workstation Administration: • Ability to create customized tool bars

Library Settings • Ability to filter org unit settings • Charge fines on overdue circulations when closed • Suppress various transits between org units • GUI: cap results in patron search • Patron user names can now be locked • Turn on text messaging

Development Updates

In an effort to keep the Evergreen community informed of what the developers are doing, Lebbeous Fogle-Weekley of Equinox has been providing updates each Friday. If you missed them on the lists, here they are again: May 18 - May 29 - June 1 - June 8 -

Evergreen Releases

At the 2012 Evergreen Conference in April, Galen Charlton announced the decision by the Evergreen developers that all current and future Evergreen releases will have release managers. In the future there will be time-based releases, with two major releases a year, at six months apart. Bug fix releases will also be on a periodic schedule. The release manager will regularly communicate the status of the release to the community and will work in conjunction with DIG and here, at the newsletter. There will also be release maintainers. They will do what release managers do, but for bugfix releases. Evergreen 2.3 – Release Manager Bill Erickson Evergreen 2.2.0 – Release Maintainer Lebbeous Fogle-Weekley Evergreen 2.1 – Release Maintainer Dan Scott

Google Summer of Code

The Evergreen Project was chosen again for the Google Summer of Code Project. Four students will work on individual Evergreen coding projects, each with their respective mentor from the Evergreen community. This is quite an honor as only 180 projects were chosen from a pool of 401 applicants. The four development projects are:

Student Daniel Rizea, mentor Dan Wells: Create android client(s) for Evergreen – offline list browsing, barcode scanning, calendar integration

Student Joseph Lewis, mentor Tom Berezansky: Upgrade Dojo to bring Evergreen to the modern web (all web browsers)

Student Pranjal Prabhash, mentor Lebbeous Fogle-Weekley: Create a PHP client code for OpenSRF and Evergreen

Student Swenyu Duan, mentor Mike Rylander: Optimize search and indexing structure of Evergreen – use C, which will speed things up

Evergreen Libraries Sprouting Up

The COOL (Consortium of Ohio Libraries) Consortium has brought up three of their eight founding members, with the last one to come up by early 2013. The most recent library to come was The Selover Public Library on June 5th. The consortium is administered and hosted by OHIONET. Check out their catalog at

C/W MARS and NOBLE Make Memorial Day Weekend Move to Evergreen By Kathy Lussier, MassLNC

Massachusetts became a little greener last month with the migration of two consortia, C/W MARS and NOBLE, to Evergreen. They joined a third MassLNC consortium, MVLC, which moved to the open-source system in May 2011.

Last month's migrations brought Evergreen to 183 library systems in the state of Massachusetts. Both consortia are running on Evergreen 2.2 and are using the template toolkit catalog. The C/W MARS catalog is available at and NOBLE's is available at

C/W MARS, NOBLE and MVLC formed the MassLNC project in 2009 when they decided to implement and jointly develop the same open-source integrated library system. The project is funded with a Library Services and Technology Act grant from the Massachusetts Board of Library Commissioners and by participating libraries.

C/W MARS is a multi-type network serving 155 library systems, NOBLE is a multi-type network serving 28 library systems, and MVLC is a public library network serving 35 library systems.

communications/newsletter/june-2012.txt · Last modified: 2012/06/14 14:51 by terlaga

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.