conference:2014:proposals
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
conference:2014:proposals [2013/10/29 22:26] – klussier | conference:2014:proposals [2022/02/10 13:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | The deadline for submitting proposals for the 2014 conference is **October 31, 2013**. Modifications to these proposals can be made through October 31, 2013. At that time, the Conference Program Committee will be soliciting feedback from the community on the proposals. Please follow the guidelines at http:// | + | ====== |
- | Collaboration among presenters | + | The deadline for submitting proposals for the 2014 conference has passed. No modifications can be made to these proposals until the feedback period |
+ | |||
+ | The Evergreen Conference Program Committee | ||
+ | |||
+ | The feedback will not only be useful as we select programs, but will also give us an idea for which programs we should expect to see high attendance. | ||
+ | |||
+ | There is no limit to the number | ||
+ | |||
+ | * Would you be interested in attending the program? | ||
+ | * Do you think the program will provide useful information? | ||
+ | * Does the program provide new information that hasn't been covered before? | ||
+ | * Will the program provide some value to the Evergreen community? | ||
+ | |||
+ | The feedback will just be one factor used by the Program Committee when selecting programs. | ||
Standard presentations will be 45 minutes in length and allow for a broad spectrum of programming in one of the following tracks: | Standard presentations will be 45 minutes in length and allow for a broad spectrum of programming in one of the following tracks: | ||
Line 12: | Line 25: | ||
=====End User Track===== | =====End User Track===== | ||
+ | |||
+ | ====Academic Reserves with a Drizzle of Syrup==== | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Technical Expertise: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Session length:** Standard 45-minute session | ||
====Authority Control in Evergreen==== | ====Authority Control in Evergreen==== | ||
Line 38: | Line 61: | ||
Standard 45-minute Session | Standard 45-minute Session | ||
- | ====Everything | + | ====Hello Reports! Stumbling Towards the Data You Need==== |
- | **Description: | + | |
- | Demonstration of patron bills. How to bill a patron, how bills can be paid, how refunds are issued, how payment type does not affect the refund process, and how to void bills. | + | |
- | **Presenter:** | + | **Description:** Reports in Evergreen are quite powerful. Yet, developing a report is often like wandering through a maze of sources, fields, data types, etc., until you get the results you need. This session will be an introduction to the report module, covering the basics of report generation. We’ll cover topics such as managing folders, choosing sources, filtering results, and sharing reports with other users. |
- | Dawn Dale, PINES Helpdesk Manager, Georgia Public Library Service | + | |
- | **Sessions | + | **Presenters: |
- | Standard 45-minute | + | Chauncey Montgomery, Director/ |
+ | Jessica Venturo, Applications Support Specialist, Bibliomation, | ||
+ | |||
+ | **Session | ||
+ | |||
+ | ====The Import/ | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Session | ||
====Introduction to Evergreen: Staff Client and Local Administration==== | ====Introduction to Evergreen: Staff Client and Local Administration==== | ||
Line 93: | Line 124: | ||
**Presenter: | **Presenter: | ||
Erica Rohlfs, Education Specialist, Equinox Software, Inc | Erica Rohlfs, Education Specialist, Equinox Software, Inc | ||
+ | Dawn Dale, PINES Helpdesk Manager, Georgia Public Library Service | ||
**Sessions Length:** | **Sessions Length:** | ||
Line 121: | Line 153: | ||
**Session Length:** | **Session Length:** | ||
I can do this in the 45 minute or tutorial track. | I can do this in the 45 minute or tutorial track. | ||
+ | |||
+ | ====Taking the Ack Out of Acquisitions==== | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Note:** I am very interested in partnering with someone else using acquisitions for this tutorial. | ||
+ | |||
+ | **Session length:** Tutorial (2 1/2 hours) | ||
+ | |||
+ | **Presumed Technical Level:** Experience with basic Evergreen staff client functions (ie. searching the catalogue) | ||
+ | |||
+ | ====What’s New in Evergreen 2.X?==== | ||
+ | **Description: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Session length:** 45 minutes | ||
+ | |||
+ | **Additional note:** This session will cover new features in the most recent release of Evergreen. | ||
=====General Track===== | =====General Track===== | ||
+ | ====Assessment of Staff Needs and Satisfaction in an Evergreen environment==== | ||
+ | |||
+ | **Description: | ||
+ | Planning the future of Evergreen in your library or consortium? Are you listening to everyone? Gaining perspective and buy-in from all users is crucial to the successful implementation of your plan. This session focuses on the assessment of staff needs and satisfaction, | ||
+ | |||
+ | **Presenter: | ||
+ | David Green, State Library of North Carolina, NC Cardinal Data Specialist | ||
+ | |||
+ | **Session length:** | ||
+ | Standard 45-minute session | ||
+ | |||
+ | **Presumed technical level of audience:** | ||
+ | None | ||
+ | |||
+ | **Accessibility requirements: | ||
+ | None | ||
+ | |||
+ | |||
+ | ====Being the Cat-herder: Managing an Open Source Software Release== | ||
+ | **Description: | ||
+ | Evergreen 2.5 Release Manager Dan Wells (Library Programmer/ | ||
+ | |||
+ | **Presenters: | ||
+ | Galen Charlton, Manager of Implementation at Equinox\\ | ||
+ | Daniel Wells, Library Programmer/ | ||
+ | |||
+ | **Session Length:** Standard 45-minute session | ||
+ | |||
+ | |||
+ | |||
====Evergreen is not an island: sharing lessons from and with other projects==== | ====Evergreen is not an island: sharing lessons from and with other projects==== | ||
**Description: | **Description: | ||
Line 171: | Line 254: | ||
**Session Length:** | **Session Length:** | ||
Standard 45-minute session | Standard 45-minute session | ||
+ | |||
+ | ====Implementing and Supporting the Acquisitions Module in Sitka==== | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Session length:** Standard 45-minute session | ||
+ | |||
+ | **Presumed Technical Level:** None | ||
+ | |||
+ | ====Is Getting There Half the Fun? Leadership and Change Management from Top to Bottom in Migrating to Evergreen==== | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Technical Level of Intended Audience:** Layperson with management experience at any level or who anticipates management responsibilities | ||
+ | |||
+ | **Session length:** Standard 45-minute session | ||
+ | |||
====License to ILL: How Equinox Turned Evergreen 2.0 Into FulfILLment™, | ====License to ILL: How Equinox Turned Evergreen 2.0 Into FulfILLment™, | ||
Line 197: | Line 301: | ||
J. Elaine Hardy, PINES and Collaborative Projects Manager, Georgia Public Library Service/ | J. Elaine Hardy, PINES and Collaborative Projects Manager, Georgia Public Library Service/ | ||
Chris Sharp, PINES System Administrator, | Chris Sharp, PINES System Administrator, | ||
+ | |||
+ | **Track:** General or Technical | ||
**Session Length: | **Session Length: | ||
Line 204: | Line 310: | ||
====Consider the KPAC: Implement and Customize the Children' | ====Consider the KPAC: Implement and Customize the Children' | ||
- | **Description** | + | **Description:** |
Learn how Bibliomation, | Learn how Bibliomation, | ||
Line 212: | Line 318: | ||
Amy Terlaga, Assistant Director, User Services - Bibliomation, | Amy Terlaga, Assistant Director, User Services - Bibliomation, | ||
- | **Sessions | + | **Session |
Standard 45-minute session | Standard 45-minute session | ||
+ | |||
+ | ====Evergreen Availability Monitoring: An introduction to monitoring the availability of your Evergreen installation==== | ||
+ | **Description: | ||
+ | This workshop is for Evergreen system administrators who want to | ||
+ | decrease their reaction time to incidents within their Evergreen | ||
+ | systems, manage small incidents before they become critical, and get | ||
+ | more sleep at night knowing that everything is running smoothly. | ||
+ | Although the focus is on Nagios, the intention is to discuss principles | ||
+ | of monitoring, using Nagios as an example. | ||
+ | |||
+ | **Presenter: | ||
+ | Michael Tate, Equinox Software, Inc. | ||
+ | |||
+ | **Session length:** Standard 45-minute session | ||
====Exploring a Browser-Based Staff Client==== | ====Exploring a Browser-Based Staff Client==== | ||
Line 237: | Line 357: | ||
**Presenter: | **Presenter: | ||
+ | |||
+ | **Session Length:** Tutorial | ||
+ | |||
+ | ====Installing Evergreen: Long Version==== | ||
+ | |||
+ | **Description: | ||
+ | |||
+ | **Presenters: | ||
+ | Chris Sharp, PINES System Administrator, | ||
+ | Benjamin Shum, Evergreen Systems Manager, Bibliomation | ||
**Session Length:** Tutorial | **Session Length:** Tutorial | ||
Line 263: | Line 393: | ||
processes, and focuses particularly on continuous integration testing | processes, and focuses particularly on continuous integration testing | ||
and how to develop more such tests for Evergreen, which is essential | and how to develop more such tests for Evergreen, which is essential | ||
- | for us to gain any real advantage with that strategy. | + | for us to gain any real advantage with that strategy. In addition, |
+ | this presentation will cover the findings of the recent performance | ||
+ | audit of the Evergreen infrastructure that was done to identify bottlenecks | ||
+ | that were negatively impacting performance. | ||
**Presenter: | **Presenter: | ||
+ | |||
+ | **Additional Notes:** A second presenter to be determined will speak about the performance audit | ||
**Session Length:** Standard 45-minute session | **Session Length:** Standard 45-minute session | ||
+ | ====Structured library data: holdings, libraries, and beyond==== | ||
+ | **Description: | ||
+ | structured data from the TPAC by default, enabling search engines to | ||
+ | understand what bibliographic records are available at your libraries. | ||
+ | But important pieces, such as copy-level data, were missing. In this | ||
+ | session, learn what Dan Scott has done with Evergreen as part of the | ||
+ | W3C schema.org Bibliographic Extension community group efforts to | ||
+ | publish more complete structured library data on the web. We'll show | ||
+ | how the data that your library already manages in Evergreen--such as | ||
+ | holdings, hours of operation, and branch locations--can be expressed | ||
+ | in the schema.org vocabulary, and explore what that means for the | ||
+ | future of libraries. | ||
+ | |||
+ | **Audience level:** Intermediate | ||
+ | |||
+ | **Presenter: | ||
+ | |||
+ | **Session Length:** Standard 45-minute session |
conference/2014/proposals.1383099962.txt.gz · Last modified: 2022/02/10 13:33 (external edit)