The Book of Evergreen
DanScott
2007Dan Scott
Preface
Why read this book?
Conventions
Getting Evergreen
Requests for comments
Introduction
What is Evergreen?
A brief history of Evergreen
Is Evergreen right for your library?
Evergreen architecture
Evergreen concepts
Organizational units: consortiums, libraries, and locations
Items: bibliographic records, volumes, and copies
Scenarios: a tale of two Evergreen systems
Scenario 1: Le Grande University
Le Grande University is a large academic institution that
features one main library and six libraries with specialized
collections distributed across campus. Circulation counts are
low, search sessions are low volume but lengthy and in-depth,
faculty and students make heavy use of shared resource lists
and RSS feeds for lists of new resources in areas of interest.
Scenario 2: Metropolitan Public Library Consortium
The Metropolitan Public Library Consortium consists of one large
central reference library, a set of 33 branch libraries in the
city core, and 25 branch libraries distributed throughout the five
recently amalgamated suburban areas that were once independent public
libraries.
Circulation counts are extremely high. Search sessions are high
volume but typically short in duration and simple title / author
searches. Catalog interfaces must be available in many different
languages to support the diverse population of patrons. The staff
client interface must be available in both official federal
languages (French and English).
Setting up an Evergreen system
Setting up the router
Setting up PostgreSQL database
Setting up the memcached servers
Configuring Evergreen
Defining basic connection information (opensrf_core.xml)
Defining Z39.50 sources (opensrf.xml)
Defining an added content service (opensrf.xml)
Setting default login timeouts (opensrf.xml)
Setting circulation policies (opensrf.xml / circ_groups.js)
Defining field mappings (fm_IDL.xml)
Setting up Apache Web server
Basic configuration (apache2.conf / httpd.conf)
Defining your virtual host
Installing the Evergreen staff client
Troubleshooting
Administering Evergreen
Starting and stopping Evergreen
Setting up organizational units
Generating reports
Preventing disaster
Core tasks
Cataloging
Circulation
Course reserves
Acquisitions
Serials
Customizing Evergreen
About this section
This section is intended to describe the tasks that Evergreen administrators
can perform to customize the look and feel of the system for their libraries.
All tasks described here will be able to be completed with a rudimentary
knowledge of XHTML, CSS, and JavaScript.
Customizing the staff client
Changing labels and messages
Customizing the catalog
Changing labels and messages
Changing the hit list details
Changing the detailed view details
Technical reference
About this section
This section will document the Evergreen application programming
interfaces (APIs), database schemas, communication protocols,
client and catalog design and implementation, and configuration
files.
Application Programming Interfaces
Database schemas
Communication protocols (XMPP + JSON)
Configuration files