Evergreen Consortium Setup

When You Need Evergreen

Choose Evergreen if you have:

• 10 or more library locations/branches
• Shared catalog and circulation (patron from Branch A can borrow at Branch B)
• Shared holdings and item management
• Complex billing and sharing agreements

Koha works for single libraries or small consortia (2-5 branches). Evergreen is built for larger consortia.

Key Differences from Koha

• Organization: Evergreen uses organizations/branches as core structure (not libraries)
• Circulation: Built-in interlibrary loan and system-wide circulation
• Holdings: All items in a shared pool with complex holds logic
• Administration: Centralized administration for the whole consortium
• Complexity: More complex setup, but powerful once configured

What You Need

• Central Linux server (8GB RAM minimum, 50GB disk for 1 million items)
• PostgreSQL database (Evergreen's native database)
• Network connecting all library locations
• System administrator (not optional for Evergreen)
• Libraries must have consistent practices (cataloging standards, circulation policies)

Architecture

Central Database Server
   |
   +--- Web Server (OPAC, Staff Interface)
   |
   +--- Holdings Server
   |
   +--- Branch A (circulation desk, self-checkout, etc.)
   +--- Branch B
   +--- Branch C
   (connected via network)

Installation (Simplified)

sudo apt-get update
sudo apt-get install postgresql-client postgresql

# Add Evergreen repository
sudo apt-add-repository ppa:evergreen-ils/release

# Install Evergreen
sudo apt-get install evergreen-oclc-ldp

# Configure PostgreSQL
sudo -u postgres createdb evergreen

# Start services
sudo service apache2 restart
sudo service opensrf start

This is simplified. See Evergreen documentation for full details.

Initial Configuration

1. Define Organizations

Administration > Organizations. Create parent organization (consortium) and child organizations (libraries/branches).

2. Set Circulation Policies

Define loan periods, holds rules, and sharing agreements between organizations.

3. Configure Holdings Pools

Define which organizations share item pools for borrowing.

4. Set Up Staff Accounts

Create staff accounts for each location with appropriate permissions.

Evergreen vs. Koha for Consortia

Real-World Evergreen Deployments

• Pines (Atlanta Public Library system)
• Metrowest Library Consortium (Boston area)
• Mid-Hudson Library System (NY)
• Chesapeake Regional Library (Virginia)

Challenges with Evergreen

• Steep learning curve: Evergreen is complex. Plan for 6 months setup time.
• Standardization required: All libraries must follow same cataloging standards and policies
• System administrator mandatory: You need dedicated staff who know Evergreen
• Customization costs: Consortium-specific features require development

Getting Help

• Evergreen Official Site - Documentation and community
• Evergreen Wiki - Community documentation
• Evergreen GitHub - Source code
• Our Methodology - How we evaluate library systems
• Consulting Services - Professional implementation

Questions Before Choosing Evergreen

1. How many libraries/branches do you need to support?
2. Do you need shared borrowing (patron borrowing across branches)?
3. Do you have dedicated system administration staff?
4. What's your implementation timeline (Evergreen takes 6+ months)?
5. What's your budget (implementation, training, ongoing support)?

If you answer "only 2-5 libraries" to question 1, consider Koha instead. If you answer "yes" to 10+ libraries and "no" to system admin, Evergreen might not be right for you.