John talks about living “open source” where key moments in his life have been marked by recurring themes of openness, sharing, trust, and cooperation. He draws upon transformative incidents as a student at Oberlin College, hitchhiking to Alaska, working with Alaskan fishermen, and most recently as a writer. The freedom to pursue all these activities, and to have free and equal access to information and tools, is essential to life and to a healthy democracy.
Zak describes various cycles of change. He gives examples from different domains including biology (The Devoinian era), agriculture (Fertile Crescent) and history/sociology (Rapa Nui) examples that illustrate cycles of change. Zak argues that change is inevitable and the rate of change has increased dramatically throughout history. He offers ideas on how libraries and open source projects, like Evergreen, can cope with inevitable change. Zak argues that we need to be aware of our needs and be able to communicate them, value diversity and learn about patterns of change in many domains so we can see patterns of change within libraries and the Evergreen community.
State of Egils
Evergreen is supported by a busy and vibrant community. Take a look at the work that has been accomplished over the past year and learn how you can contribute to the Evergreen community.
How to Translate Developer: A Live Translation Session
Have you ever wanted to understand what developers mean when they say things like “nominally complete”, “functionally equivalent”, or “prohibitively expensive in the database”? Join us for a session where we will observe two developers and perform live translations of their arcane terminology. This session will allow the Evergreen end user to get a glimpse into how to translate “developer” into “librarian”. We will learn the right things to ask (and the right way to ask them) in order to facilitate a productive conversation for all parties. The session will conclude with an open Q&A on best practices for communication between developers and non-developers.
Support and Training in a Consortial Environment
Training a consortium: What levels of training are required to manage a successful 100 library consortium?
* Formal training. Certain training classes are required of libraries joining the consortium (Basic circulation, basic cataloging, admin and reports). Our staff at the Indiana State Library offers all three of these required trainings onsite every month.
* Group discussions. We have 5 committees involved in the policy and training of the consortium and a bookmobile user group. They meet quarterly throughout the year and provide an opportunity to educate and communicate on policy and using the software.
* Individual training. EI Coordinator is always available through email or phone to answer on-demand questions about policy or using the software.
* Helpdesk. Members of the consortium also have access to the helpdesk in which they can learn about the system by making *mistakes* and interacting with the software experts.
* Training materials:The most effective training materials we have used include demonstrations, making a training server available and walking staff members through scenarios.
Additionally, there will be a discussion of tools, e.g. RT and DocBook,voip server for distributed call centre, go live model, suite of WBT and onsite training, webinars for all, co-op website.
Evergreen serials: Making it work for you
Dealing with serials ultimately means managing your workflow, but the solution is not the same for everyone. This session will walk through some common scenarios, and also demystify some specialized features and system quirks to help you tailor your setup to your specific needs.
So, you’ve installed Evergreen, and are now proud owner of a PostgreSQL server. Congratulations? Few libraries have the budget for a full-time or contract DBA to manage the databases which come with Evergreen. If you’re in this situation, never fear! The amount of stuff you actually need to know for the care and feeding of a PostgreSQL instance is not substantial. You can learn it with speed and go back to your real job. This presentation will cover the basic topics you need to know so that you know what to check and where to look it up, including:
* Updates & Upgrades
* Backups & Recovery
Attendees will be expected to have basic Linux/Unix/Mac server administration knowledge.
No description available.
In Search of Search
Staff librarians, Catalogers, and Material Selectors at KCLS miss some of the finely tuned browsing features of older-school ILS systems. KCLS recently contracted with Catalyst, an application developer out of Portland, to accelerate development of various browse and exact match searches in Evergreen, specifically targeted at improving Cataloging and Selection and Ordering staff efficiency. The implications and possible extensions of this work are wide-ranging. This program will try to consider and present a current overview of the various Community projects and strategies that are currently underway to address this functional hope for of more diversified searching options for Evergreen. Catalyst and KCLS will co-present.
Contributing Code to Evergreen is Easier Than You Think
I would like to give an outline of how library staff and other Evergreen users can make contributions to the Evergreen codebase at any of the following steps in the process that leads to being made an official Evergreen committer.
1) Report bugs – how to do it well and get the best outcome
2) Test patches – how you can get it done even if you don’t administrate your own Evergreen server
3) Produce code – Even if you don’t think you’re a programmer, some parts of Evergreen are easier to change than you think, such as the Template Toolkit OPAC
Each stage will be further illustrated by stories from prominent Evergreen contributors.
Upgrading Evergreen: A Case Study
In the summer of 2012, Sitka (a shared Evergreen instance used by over 60 library systems in BC and Manitoba) upgraded from Evergreen 2.0 to 2.2. This talk provides an overview of our upgrade process from beginning to end: project planning, testing, support, and the actual process of upgrading a production system, including the incorporation of local customizations. We’ll describe what worked, what didn’t work so well, and what we learned from the process.
Managing a Software Upgrade
Upgrading software is a best practice which takes into account the latest and most effective security settings, increased functionality, and the most current version of the system. Sometimes upgrades have very little effect on staff workflow and sometimes they change things completely! Getting community buy-in and support for upgrading is often half the battle. Providing support and training before and after the implementation is a good way to get staff members prepared for the changes to come. This presentation will discuss our upgrading experience in Evergreen Indiana and lessons we have learned the hard way. We will pull from our own experiences and give program coordination tips for other consortia.
Evergreen Tools at IISH
The International Institute of Social History (IISH) is the world’s largest documentation and research center in the field of social history. IISH started to use Evergreen in 2011 after a great deal of preparation for the migration from the old commercial library system to Evergreen. During migration a lot of great improvements in the quality of MARC records were done so at the moment IISH the Library team has a lot of experience with using Evergreen. The mission of IISG has been changed from January, 2013, so Evergreen library system will be used for the development of tools for data mining, the linking of texts and visual materials, building timelines and visualizing tools for collections and biographies. Data stored in the IISH will be used as training sets for development of tools for Named Entity Recognition (NER), language identification, text analysis, topic detection and other Natural Language Processing tools. This presentation will be an introduction of the development of tools and will show examples of Digital Humanities tools based on Evergreen open-source library system.
Thursday Lightning Talks
Envisioning Evergreen: Charting the Course to 2020
Evergreen turned 6 in September 2012 and over the past six years a growing international community of users have seen the software develop to meet its diverse needs. What’s next for Evergreen? Where do we need to target development to meet the needs of libraries and library users in 2020? How can the community work together to better identify common functionality needs? What more can we do to find the funds to meet our development needs? Let’s celebrate how far we’ve come and dream of where we’d like to go together!
A panel of library visionaries will kick off a lively group discussion.
Ol’ Time Acquisitions Rodeo and Variety Show
As more and more libraries begin using Evergreen Acquisitions features, a clearer picture emerges of how the software will be used in libraries and how features should operate. This helps us more clearly define areas of new development, including new features and improvements to existing interfaces. In this workshop, we will cover Admin set-up of the Acquisitions module and possible Acquisitions workflows in Evergreen. The session will also highlight new ACQ features developed for Evergreen 2.3 and beyond, including staff features and vendor interfacing enhancements. Workshop participants will have the opportunity to gain hands-on experience with the Acquisitions module. Participants will start with building orders and walk through order processing, and invoicing.
Searching with Solr
I suppose the audience would be anyone looking to learn more about a Solr bolt-on for Evergreen – a tool which I’m currently working on (called Sunshine). This could be developers, but is more likely to be those interested in searching and browsing their Evergreen data. I want to talk about how Solr works, why it’s awesome (indexing! facets!) and where it fails (not real-time) and how to resolve that. I’ll cover requirements and integration points as well (SQL vs API). I’ve used Solr on loads projects – it’s part of most Drupal installs I do (dozen or so) I’ve got it tied to my development Evergreen, it’s in some custom software I built/maintain and I’ve used the lower-level components (Lucene) a few times. I’m currently working with KCLS (WA) and Biblio.org (CT) and I’m bidding on a search project for MassLNC.
How to GITify Your Changes: The Easy Peasy Lemon Squeezy Way
Have you made all these great changes to your OPAC and staff client only to lose them when you upgrade versions? Have you written down all your cool changes and then spent hours redoing all your work for your upgrade? Or have you done things on the fly and then forgotten to record the changes and then upgraded? Join Melissa Lefebvre from Bibliomation as she explains GIT for the Windows user so that you no longer lose your super cool changes. She will walk you through setting up and using GIT on your Windows machine, including staging files, writing commit messages and pushing your changes to your site’s local GIT repository without ever needing to use a command line. She will also review how to submit your changes to the Evergreen community so that all can benefit from your awesome work.
Cataloging in Evergreen
An experienced cataloger and Evergreen user will give an overview of various workflows for cataloging in the Evergreen staff client. Included will be importing records (both individually and in batches), manipulating and editing MARC records, creating & editing items & volumes, batch edits & bucket functions (including deleting items), setting up item templates, and running basic reports. If time permits, I will also touch on the basics of RDA in Evergreen.
Consortial Circulation in Evergreen: 5 Quick Tips for Libraries New to Evergreen!
While Evergreen continues to grow and innovate, more and more libraries and library consortiums are moving to this amazing ILS system. However, for standalone libraries or newly formed consortiums, circulation within the system is a whole new game! From workflow to holds policies and those crazily-configured circulation rules, it takes both time and understanding to come to grips with the change. Given this, plan on taking this quick and enlightening tour of 5 themes you need to consider when implementing your library on an Evergreen consortium-level platform!
Microdata: Making Metadata Matter for Machines
WARNING: you may come away with ideas not only for enriching your library system, but for your web site and other web-based library applications as well!
Microdata enables search engines and other automated processes to make sense of the data on a web page — like identifying the title, author, and identification number of a book from all of the other content on a given page. Web pages enhanced with microdata contribute to the semantic web, and in turn are more likely to be incorporated into search engines and advanced web applications. If it sounds like we should publish microdata from Evergreen’s catalogue, you will be pleased to know that Evergreen was (naturally) the first library system to incorporate microdata in its default public catalogue with the 2.2.0 release in June 2012.
In this session, Dan Scott (the contributor of the schema.org microdata enhancement for Evergreen and a participant in the schemabibex effort to extend schema.org to better support bibliographic data) will discuss the origins of the microdata standards, explain how nominally machine-readable cataloguing data can fit into the machine-actionable semantic web, reflect on the impact that a microdata-enabled catalogue has had at Laurentian University to date, and offer some thoughts about the future of microdata – including the schema.org and RDFa Lite standards.
Data Quality in Evergreen
It’s been said that NextGen discovery systems are a great way to reveal all of the problems with your bibliographic data, and Evergreen is no exception. During this presentation, Galen Charlton will discuss some common data issues that affect Evergreen libraries and provide some tools and tips on how to deal with them. This session will focus on catalog data that directly affects usability of the OPAC for patrons.
Friday Lightning Talks
From Inspiration to Implementation
A panel discussion about implementing software development projects related to Evergreen. The panel would be myself, Grace Dunbar of Equinox, Ben Shum of Bibliomation, Dan Scott of Laurentian University and Kathy Lussier of MASSLNC.
The UBCIC Open Source Ecology
The Union of B.C. Indian Chiefs is an organization which works collectively amongst Indigenous Nations in BC and acts as an advocacy body to provide a cohesive voice in support of Indigenous Nations and communities, and to promote and protect each Nation’s exercise of Sovereignty within their traditional territories. The UBCIC Resource Centre is a specialized research library and archives which focuses on BC land rights research. The UBCIC RC has embraced an open source ecosystem as an economical and effective method for providing access to resources for researchers. Resource Centre director Alissa Cherry and technology consultant James Fournie will discuss the creation and growth of the UBCIC digital collections program over the years, which uses the Greenstone Digital Library Software and leverages cloud-based tools like Archive.org, all within a low budget. Hear about some other uses of open source software in the UBCICRC including Linux workstations and custom-built finding aids. Also hear why UBCIC chose Evergreen and how UBCIC migrated from an InMagic database to become one of the first libraries in Canada to use Evergreen in production. Also hear how it plans to use Evergreen in the future.
How to Choose the Right Hardware for PostgreSQL and Evergreen
KCLS staff will co-present with Joshua Drake, the CEO of “Command Prompt”, a firm who specializes in understanding and optimizing the PostgreSQL database system. KCLS is working with Command Prompt to optimize hardware and database configurations for best Evergreen performance.
There and Back Again, Again
Last year at Evergreen Indiana we had a very successful panel discussing networking issues with Evergreen, some horror stories, some best practices and one really bad token ring pun. This year we want to revisit that format, this time with Rogan Hamby of SCLENDS, Robin Johnson of SITKA and Galen Charlton of Equinox Software. Added to the mix will be some original research into networking impact of Evergreen and requirements by the participants.
The Good, the Bad and the Ugly: Handling Post Migration Issues
The presentation will focus on what kinds of things libraries and consortia need to think about post migration. This presentation will answer questions about what happens when your libraries go live and inevitably find something quirky about the new data or patrons that are having difficulty with a change to a new OPAC.
* How do you handle support under the new system and did you plan for a significant increase in support requests for immediate post migration issues?
* How do you manage staff, patrons and libraries that do not deal with change well?
* What marketing needs to be done to promote Evergreen?
* Is additional training needed?
* What do you do about data cleanup?
The two presenters are in different stages of moving to a Evergreen. Bibliomation is a consortium that has been on Evergreen for more than a year. C/W MARS is a large consortium that recently migrated to Evergreen.
The Evolution of an Enhancement: The Evergreen Development Idea Process
How does a library enhancement wish list item make its way to the Evergreen developer? Learn the best practices of two library consortia, Sitka and Bibliomation, as they explain the steps they took to see their Evergreen ideas through to the development process. By working directly with their member libraries in gathering wish list items, then working with the Evergreen community in developing partnerships, these two groups learned a lot along the way. For instance, what potential political hurdles should you be aware of and how do you get member libraries to actually vote? Discover the software tools available to simplify the enhancement voting process for your library community. Engage in a lively discussion about the practicality of creating an enhancement wish list environment for the entire Evergreen community.
Evergreen: 5 Years Later
The Innisfil Public Library (IPL) adopted Evergreen as their ILS almost 5 years ago, with the intention that this shift in direction would create a catalyst for organizational change. All staff had a role in implementing the change, working together and solving problems as a team, as many had roles completely outside their comfort zones. It was an opportunity to build staff skill levels, boost technological confidence levels and fuel team cohesiveness.
These key learnings set the stage for IPL to be able to pursue new partnerships, projects and services, such as: the recent implementation of IPL’s new local history database, Our Stories using the Islandora software developed by the University of Prince Edward Island, and a new program at IPL called “Check out a Skill” which encourages the public to bring their technology problems, such as issues with e-readers, to the IPL staff.
IPL staffs are continuously learning, collaborating and developing new abilities and expertise with each new initiative confronted and tackled. While not every new project is successful, our failures have been incredible learning opportunities. We invite you to hear how Evergreen helped a small public library to transform itself by making unconventional choices and taking unconventional risks.
Teach a Man to Fish; Or, how I stopped Worrying and Learned to Solve Problems with Open SRF
At the Evergreen Conference in 2012, Equinox committed itself to developing configuration-resource sharing service that could integrate with Evergreen. We will present this new service as a case study on how to leverage your existing knowledge of Evergreen’s workings to build new services on top of the software platform underlying Evergreen. OpenSRF and and other technologies will be demystified, and we will show how this platform you already make use of can be the bedrock of other innovative library software applications. Of course, it takes more than an awesome platform — you need a plan. We will also show how to leverage efficiencies provided by OpenSRF and other Evergreen technologies to reduce both the amount of development and project management effort necessary, and how to structure and manage an OpenSRF-based development project for success. This presentation will be geared toward systems librarians and developers, and the managers thereof, who want to understand better one of the platform options available to them.
Home Grown RFID for Evergreen
Nearly 3 years into their journey with Evergreen, and inspired by the success of the open-source ILS, the Grand Rapids Public Library decided to use their knowledge of the application to write a set of tools to interact with off the shelf RFID readers and tags. Two years later, they have a fully functional UHF RFID system, providing full check-out, check-in, material security, and item locating abilities with the flexibility of Evergreen.
Come hear about the challenges and experiences of starting from scratch to rethink library material handling and learn the in’s and out’s of RFID from a perspective outside of the library world.
Works with Evergreen: Practical Approaches to Integration
Evergreen implements a number of standard library protocols, as well as a complete API which supports all of the functions available in the staff client. Together, these points of integration allow Evergreen to interoperate with a growing number of tools and services. This talk will cover examples of these tools and services; outline the methods by which they communicate with Evergreen today; and provide recommended development strategies for creating new tools and services or modifying existing ones. We will address common pitfalls and challenges; look at Evergreen from a third party service provider viewpoint; examine ways in which Evergreen can be enhanced to facilitate easier integration with tools and services yet to come; and identify potential areas of collaboration with projects outside the Evergreen ecosystem, such as Koha.
Update from Oversight Committee
Evergreen: a good place to be
Evergreen can be a catalyst for real change in libraries. This panel will discuss why Evergreen is more than an ILS; it is a movement to work and think in new ways about our systems and data and do this within the context of community. We will discuss these ideas from the perspective of library education, public and academic libraries, and institutional decision makers.