Below are some successful proposals that have been submitted for past Evergreen conferences. Prospective presenters are encouraged to use them as models for writing proposals for the 2014 conference.
After the Trainer Leaves: Continuous Learning and the Evergreen ILS: Your staff has been trained to use the Evergreen ILS. Now what? In this session, we will answer that question by focusing on learning that takes place after formal training has ended. Specifically, we will discuss strategies for self-directed learning of the Evergreen ILS to build on the foundation of formal training. Self-directed learners are motivated to learn, can establish learning goals, can identify helpful resources, and will take responsibility for their learning. They can augment their formal knowledge of Evergreen through independent learning in informal, on-the-job contexts. You will leave this session with practical strategies to encourage this type of learning in your organization and to help your staff become successful learners.
Front Line Users and Administrators
10% Wrong, 90% Done: A Practical Approach to Bibliographic De-duplication: After the pilot libraries of SCLENDs merged their collections it became obvious that the initial bibliographic de-duplication algorithm was too strict for our needs. Manual cleanup was out of the question but we insisted upon higher quality. We decided to develop a new algorithm and take new risks. We also had to challenge the common wisdom that a few match points could not be generalizable to create a large number of accurate matches. This is what we did and how we’ve defined success.
Testing… Testing… Is This Thing On?: Installing an Evergreen ILS Test Server: A demonstration and Q & A session for those wanting to build an Evergreen test server and would like some guidance about how it’s done and how it might be used. Presenters Ben Shum from Bibliomation and Chris Sharp from Georgia PINES will walk participants through the installation process beginning with a base Linux OS installation through setting up the staff client to work with your new test server.