Some stakeholders in the Evergreen community have an immediate need for writers who can produce well-written documentation for acquisitions services in library automation software. Librarians and other library workers who use, configure, or manage library acquisitions systems are the audience for this documentation. This is freelance work to begin in September, 2008 and be completed no later than December, 2008. Rates are competitive. Contact Karen Schneider, Equinox Community Librarian with at least two relevant writing samples and a brief description of your experience with writing documentation.
Evergreen at two
On June 4, 2004, Lamar Veatch, State Librarian of Georgia committed the Georgia Public Library Service (GPLS) to a one year test of an open source initiative to develop a new kind of software: a consortial library system.
Georgia had for many years (at least since the 1940’s) pursued a fairly consistent policy—subject to the vagaries of politics and history—to join its smaller public libraries into resource-sharing regional library systems. As a part of an innovative Y2K project, it automated 26 of the regional library systems and smaller county systems into PINES, creating a union database of materials and patrons for a level of resource sharing that was unprecedented.
PINES was a success and was significantly expanded in 2001 but by 2004, for various reasons, the software running PINES was not able to deal with a large, geographically dispersed, system. As is well-known, the automated system reached previously unknown limits and had to be rebooted in the middle of the day to keep operating. Meanwhile, more libraries wanted to join. After an examination of the available software on the market, it was realized that there was nothing to meet the system requirements of the PINES libraries, let alone handle a growing network with evolving requirements. Would Georgia continue its visionary, resource-sharing network? Would it stop adding new libraries and allow the software to limit PINES’ capabilities? Or would it do something else?
On June 4, Georgia embarked on a new course in the library world: it would write the software itself, using the tools and practices of open source and thereby hoping to organize a community around the Evergreen project. There was much skepticism in the library world, of course.
The development process began with the results of feedback from hundreds of people who attended PINES focus groups in 2004. At these focus groups, the phrase “pretend it’s magic†helped break through many of the preconceptions that staff had about what technology could do. These focus groups helped define what Evergreen would do and how it would do it.
After two years of development and testing, Evergreen went live on September 5, 2006 as 44 public library systems in PINES migrated over the Labor Day weekend. There were 252 outlets (central libraries, branches, and bookmobiles) at the time.
It was a success.
Today, there are 50 public library systems in Georgia running Evergreen with 275 outlets. In addition, public libraries in five other states and one Canadian province are using Evergreen now. The Evergreen community currently has 61 public library systems and 292 outlets, with a combined annual circulation of over 20 million items.
In 2008, Evergreen added its first academic library, the University of Prince Edward Island.
This growth has been accompanied by hard work, dedication, and the contributions of many people, particularly the librarians and other library staff in Georgia and at the Georgia Public Library Service. Development continues as more functionality is added and more libraries and more large consortia have seen the value of resource sharing on a grand scale. Other vendors are also paying attention as they seek to add capabilities that Evergreen has had for two years. However, it took librarians and an open source initiative to blaze this trail.
Bob Molyneux
What’s in a name? (open-ils.org to evergreen-ils.org)
The Evergreen community has been discussing changing the domain for Evergreen’s project site from open-ils.org to evergreen-ils.org.
“Discussion” may be too strong a word… it’s more like consensus, at least from members of the Evergreen community who have been reading the list the last two weeks. The majority opinion seems to be that this has been a “round tuit” that just needing getting-around-to.
In case you’re wondering, evergreen-ils.org is in place and functioning right now… the name was reserved to prevent squatters, and it made sense to make it an alternate name no matter what.
open-ils will probably never disappear entirely. As the original name for the software that became Evergreen, open-ils is embedded in the code, used for the names of the Evergreen discussion lists, and also appears in the name of the Evergreen IRC channel.The blog and the documentation wiki convert to the new name rather nicely, but we’ll see open-ils in the wild for some time to come.
(And of course, open-ils.org will continue to respond to requests.)
Any last thoughts out there? A related question arose about creating a tagline for Evergreen, to retain the word “open” in its description — might be a nice touch, as well as a homage to the innovation and dedication that gave this project life and breath.
— Karen, Equinox Community Librarian