1 <?xml version="1.0" encoding="utf-8"?>
2 <book version="5.0" xmlns="http://docbook.org/ns/docbook"
3 xmlns:xi="http://www.w3.org/2001/XInclude">
5 <title>The Book of Evergreen</title>
6 <author><personname><firstname>Dan</firstname><surname>Scott</surname></personname></author>
7 <copyright><year>2007</year><holder>Dan Scott</holder></copyright>
10 <part><title>Preface</title>
11 <chapter><title>Why read this book?</title></chapter>
12 <chapter><title>Conventions</title></chapter>
13 <chapter><title>Getting Evergreen</title></chapter>
14 <chapter><title>Requests for comments</title></chapter>
17 <part><title>Introduction</title>
18 <chapter><title>What is Evergreen?</title></chapter>
19 <chapter><title>A brief history of Evergreen</title></chapter>
20 <chapter><title>Is Evergreen right for your library?</title></chapter>
21 <chapter><title>Evergreen architecture</title></chapter>
22 <chapter><title>Evergreen concepts</title>
23 <section><title>Organizational units: consortiums, libraries, and locations</title></section>
24 <section><title>Items: bibliographic records, volumes, and copies</title></section>
26 <chapter><title>Scenarios: a tale of two Evergreen systems</title>
28 <title>Scenario 1: Le Grande University</title>
30 Le Grande University is a large academic institution that
31 features one main library and six libraries with specialized
32 collections distributed across campus. Circulation counts are
33 low, search sessions are low volume but lengthy and in-depth,
34 faculty and students make heavy use of shared resource lists
35 and RSS feeds for lists of new resources in areas of interest.
39 <title>Scenario 2: Metropolitan Public Library Consortium</title>
41 The Metropolitan Public Library Consortium consists of one large
42 central reference library, a set of 33 branch libraries in the
43 city core, and 25 branch libraries distributed throughout the five
44 recently amalgamated suburban areas that were once independent public
48 Circulation counts are extremely high. Search sessions are high
49 volume but typically short in duration and simple title / author
50 searches. Catalog interfaces must be available in many different
51 languages to support the diverse population of patrons. The staff
52 client interface must be available in both official federal
53 languages (French and English).
59 <part><title>Setting up an Evergreen system</title>
60 <chapter><title>Setting up the router</title></chapter>
61 <chapter><title>Setting up PostgreSQL database</title></chapter>
62 <chapter><title>Setting up the memcached servers</title></chapter>
63 <chapter><title>Configuring Evergreen</title>
64 <section><title>Defining basic connection information (opensrf_core.xml)</title></section>
65 <section><title>Defining Z39.50 sources (opensrf.xml)</title></section>
66 <section><title>Defining an added content service (opensrf.xml)</title></section>
67 <section><title>Setting default login timeouts (opensrf.xml)</title></section>
68 <section><title>Setting circulation policies (opensrf.xml / circ_groups.js)</title></section>
69 <section><title>Defining field mappings (fm_IDL.xml)</title></section>
71 <chapter><title>Setting up Apache Web server</title>
72 <section><title>Basic configuration (apache2.conf / httpd.conf)</title></section>
73 <section><title>Defining your virtual host</title></section>
75 <chapter><title>Installing the Evergreen staff client</title></chapter>
76 <chapter><title>Troubleshooting</title></chapter>
79 <part><title>Administering Evergreen</title>
80 <xi:include href="starting_stopping.xml" />
81 <chapter><title>Setting up organizational units</title></chapter>
82 <chapter><title>Generating reports</title></chapter>
83 <chapter><title>Preventing disaster</title></chapter>
86 <part><title>Core tasks</title>
87 <chapter><title>Cataloging</title></chapter>
88 <chapter><title>Circulation</title>
89 <section><title>Offline circulation</title></section>
91 <chapter><title>Course reserves</title></chapter>
92 <chapter><title>Acquisitions</title></chapter>
93 <chapter><title>Serials</title></chapter>
96 <part><title>Customizing Evergreen</title>
98 <title>About this section</title>
100 This section is intended to describe the tasks that Evergreen administrators
101 can perform to customize the look and feel of the system for their libraries.
102 All tasks described here will be able to be completed with a rudimentary
103 knowledge of XHTML, CSS, and JavaScript.
106 <chapter><title>Customizing the staff client</title>
107 <section><title>Changing the theme</title></section>
108 <section><title>Changing labels and messages</title></section>
109 <section><title>Changing key mappings</title></section>
111 <chapter><title>Customizing the catalog</title>
112 <section><title>Changing the theme</title></section>
113 <section><title>Changing labels and messages</title></section>
114 <section><title>Changing the hit list details</title></section>
115 <section><title>Changing the detailed view details</title></section>
119 <part><title>Technical reference</title>
121 <title>About this section</title>
123 This section will document the Evergreen application programming
124 interfaces (APIs), database schemas, communication protocols,
125 client and catalog design and implementation, and configuration
129 <chapter><title>Application Programming Interfaces</title>
130 <section><title>OpenSRF</title></section>
131 <section><title>Web services</title></section>
133 <chapter><title>Database schemas</title></chapter>
134 <chapter><title>Communication protocols (XMPP + JSON)</title></chapter>
135 <chapter><title>Configuration files</title></chapter>