Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
conference:2015:proposals [2015/02/26 21:19] – [Copyleft Your Contributions] roganh | conference:2015:proposals [2015/03/24 08:43] – [An Introduction to Automated Evergreen Configuration with Ansible:] jboyer |
---|
**Technical Expertise:** None | **Technical Expertise:** None |
| |
**Presenter(s):** Rogan Hamby (rogan.hamby@yclibrary.net), SCLENDS &York County Library System, Yamil Suarez, (ysuarez@berklee.edu), Berklee College of Music, Grace Dunbar (gdunbar@esilibrary.com), Equinox Software | **Presenter(s):** Rogan Hamby (rogan.hamby@yclibrary.net), SCLENDS &York County Library System, Yamil Suarez, (ysuarez@berklee.edu), Berklee College of Music, Grace Dunbar (gdunbar@esilibrary.com), Equinox Software, Andrea Buntz Neiman (aneiman@kent.lib.md.us), Kent County Public Library |
| |
==== To float or not to float: A consortium's play-by-play to implement floating groups ==== | ==== To float or not to float: A consortium's play-by-play to implement floating groups ==== |
| |
**Presenter(s):** Erica Rohlfs (erohlfs@esilibrary.com), Project Manager, Equinox Software, Inc. (ESI) | **Presenter(s):** Erica Rohlfs (erohlfs@esilibrary.com), Project Manager, Equinox Software, Inc. (ESI) |
| |
| ==== Introduction to the Staff Client ==== |
| |
| **Description:** Designed for brand-new users or those considering Evergreen, this session will go over the major aspects of the staff client including Circulation & Patron functions, Cataloging, and some basic Workstation Administration settings. Assuming a cooperative internet connection, this will be a live demo. Version will be the current stable release. |
| |
| **Technical Expertise:** Low |
| |
| **Presenter(s):** Andrea Buntz Neiman (aneiman@kent.lib.md.us), Librarian II, Head of Public Services, Kent County Public Library |
| |
| ==== Acquisitions Rodeo, Part 2: EDI Wrangling ==== |
| |
| **Description:** EDI allows users of the Evergreen Acquisitions module to seamlessly send purchase orders to vendors and receive order-related messages and invoices directly in the ILS. During this session we will cover the administrative staff client setup for EDI in Evergreen. Topics will include the configuration of Provider accounts and EDI accounts, as well as a discussion of the server level configuration needed to enable Evergreen to send and receive EDI messages. We will also cover a basic acquisitions workflow that illustrates the use of EDI, including copy overlay. |
| |
| **Technical Expertise:** Low to Moderate |
| |
| **Presenter(s):** Angela Kilsdonk (akilsdonk@esilibrary.com), Education Manager, Equinox Software |
| |
| ==== Authority Control in Evergreen: The Straight Dope (Back by request! Previously presented at 2014 Conference) ==== |
| |
| **Description:** Authorities are dope, yo. Used properly, they simplify cataloging and increase patron access to materials through improved discovery capabilities. During this session we will discuss exactly how authority control works in Evergreen and how best to make use of the advanced capabilities that Evergreen provides. We will cover browse integration, automatic record overlay, authority generation, bibliographic and inter-authority record linking, Control Sets and their configuration, and how to make use of local, extra-LoC data and expertise to leverage the full potential of Evergreen’s authority control feature set. We will also discuss possible “wish list” features to gauge the priorities of the community for future development. |
| |
| **Technical Expertise:** Low to Moderate |
| |
| **Presenter(s):** Mike Rylander (miker@esilibrary.com), President, Equinox Software and Angela Kilsdonk (akilsdonk@esilibrary.com, Education Manager, Equinox Software |
| |
| |
| |
**Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation, Erica Rohlfs (erohlfs@esilibrary.com), Project Manager, Equinox Software, Inc. (ESI), and TBD | **Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation, Erica Rohlfs (erohlfs@esilibrary.com), Project Manager, Equinox Software, Inc. (ESI), and TBD |
| |
| ====Oh! The Places Acquisitions Can Go!==== |
| |
| **Description:** |
| |
| >>>You have brains in your head. You have feet in your shoes. You can steer yourself in any direction you choose. You’re on your own. And you know what you know. And you are the guy who’ll decide where to go. You’ll get mixed up of course, as you already know. You’ll get mixed up with many strange birds as you go. So be sure when you step. Step with care and great tact and remember that life’s a great balancing act. And will you succeed? Yes! You will, indeed! (98 and ¾ percent guaranteed.) |
| >>>--__Oh the Places You’ll Go__, Dr. Seuss. |
| |
| Acquisitions users have long development wish lists. In this session, we will facilitate a discussion of Acquisitions users’ top ten development wishes and produce a collaborative, prioritized development list of five. We will also begin requirements and use case gathering toprepare a requirements document for the community to share and use while seeking development funding and to propel Acquisitions forward in a way that will benefit the entire community. |
| |
| **Presenter(s):** Leslie St. John, Georgia Public Library Service, PINES Acquisitions Consultant, lstjohn@georgialibraries.org; J. Elaine Hardy, Georgia Public Library Services, PINES & Collaborative Projects Manager, ehardy@georgialibraries.org |
| |
| **Technical Expertise:** Low to Moderate |
| |
==== Adding Data Sources to the Reporter ==== | ==== Adding Data Sources to the Reporter ==== |
**Presenter(s):** Jennifer Dale (daleji@forsyth.cc) and Jonathan Furr (furrjt@forsyth.cc), Technical Services, Forsyth County Public Library (NC Cardinal) | **Presenter(s):** Jennifer Dale (daleji@forsyth.cc) and Jonathan Furr (furrjt@forsyth.cc), Technical Services, Forsyth County Public Library (NC Cardinal) |
| |
| ==== Badges? We Don't Need No Stinking Badges! or How to Encourage Participation ==== |
| |
| **Description:** How can your organization get more people excited about the opportunities available to participate in the design, testing, documentation, governance, and general love of Evergreen? We will focus on ways to create a local environment that will foster and reward participation. We will explore all the wonderful ways in which the average Evergreen user can contribute to the improvement of the project and what organizations can do to support them. No SQL, Git, Perl, or IRC required. |
| |
| **Technical Expertise:** None |
| |
| **Presenter(s):** Grace Dunbar (grace@esilibrary.com), Vice President, Equinox Software |
| |
| ==== Evergreen and Design: From UX to UI ==== |
| |
| **Description:** A piece of software is only as good as its user interface (UI). With no UI, a program is useless, and a bad interface can make it even worse, taking it from worthless to destructive. But what are some elements of good UI design, and how can they lead to a better user experience (UX)? In this session we will introduce some fundamental design principles, explore specific recommendations from experts in human-computer interaction, and see how some of these ideas might be applied to both the nascent web staff client and future Evergreen interfaces. |
| |
| **Technical Expertise:** None |
| |
| **Presenter(s):** Dan Wells (dbw2@calvin.edu), Library Programmer/Analyst, Hekman Library (Calvin College) |
| |
| ==== Getting what you want in your next development project ==== |
| |
| |
| Hooray! You've finally raised the funds you need for the new enhancement you want to roll into Evergreen. You contract with a developer, the work is done, and, after taking a quick look at it, you approve the final project, looking forward to the day when you upgrade to a release where you can use the feature. When the time arrives, though, you discover that it doesn't work exactly the way you expected or contains bugs that weren't discovered in light testing. In this session, we'll look at ways to make sure you really get what you want out of your next development project by learning how to clearly communicate project requirements and how to thoroughly test the final code. |
| |
| **Technical Expertise:** None |
| |
| **Presenter:** Kathy Lussier (klussier@masslnc.org), Project Coordinator, Massachusetts Library Network Cooperative |
| |
=====Technical Track===== | =====Technical Track===== |
**Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation and Jason Stephenson (jstephenson@mvlc.org), Assistant Director for Technology Services, Merrimack Valley Library Consortium (MVLC) | **Presenter(s):** Benjamin Shum (bshum@biblio.org), Evergreen Systems Manager, Bibliomation and Jason Stephenson (jstephenson@mvlc.org), Assistant Director for Technology Services, Merrimack Valley Library Consortium (MVLC) |
| |
==== An Introduction to Automated Evergreen Configuration with Ansible: ==== | ==== An Introduction to Automated Evergreen Configuration with Ansible ==== |
| |
**Description:** Building a large Evergreen installation can involve installing various components on many servers. How do you do this consistently without making mistakes? Scripts are one way, but how do you make further changes to the system without keeping a large library of scripts that have to be run in just the right order? A configuration management system can automate everything from virtual machine provisioning to updating your opac templates, while being idempotent means that changes can be made at any time and the system will always end up in the expected state. This talk will focus on using the Ansible management system but most of the concepts apply to other popular systems such as Puppet, Chef, and Salt. | **Description:** Building a large Evergreen installation can involve installing various components on many servers. How do you do this consistently without making mistakes? Scripts are one way, but how do you make further changes to the system without keeping a large library of scripts that have to be run in just the right order? A configuration management system can automate everything from virtual machine provisioning to updating your opac templates, while being idempotent means that changes can be made at any time and the system will always end up in the expected state. This talk will focus on using the Ansible management system but most of the concepts apply to other popular systems such as Puppet, Chef, and Salt. |
**Technical Expertise:** Moderate to High | **Technical Expertise:** Moderate to High |
| |
**Presenter(s):** Jason Boyer (jboyer@library.in.gov), MIS Supervisor / Evergreen Indiana System Administrator, Indiana State Library / Evergreen Indiana | **Presenter:** Jason Boyer (jboyer@library.in.gov), MIS Supervisor / Evergreen Indiana System Administrator, Indiana State Library / Evergreen Indiana |
| |
| |
==== Catalog: What a mess! ==== | ==== Catalog: What a mess! ==== |
| |
**Description:** Do you suffer from large print syndrome? Do you experience 856 pains from the subfield z? Do you wake up and find that your DVD icons have decided to be phonograph? Have you noticed that search results look redundant? Then this is for you! I am sure we all struggle to keep items attached to the right things. This is a programmatic approach to solve the problem. We will speak in detail about how we solved this issue and created software to distill the information. We will show code and queries so bring your code parser and query planner TI-85. | **Description:** Do you suffer from large print syndrome? Do you experience 856 pains from the subfield z? Do you wake up and find that your DVD icons have decided to be phonograph? Have you noticed that search results look redundant? Then this is for you! I am sure we all struggle to keep items attached to the right things. This is a programmatic approach to solve the problem. We will speak in detail about how we solved this issue and created software to distill the information. We would like to share the employed algorithms that we used to turn perl and SQL into a catalog cleanup aid. We will show code and queries so bring your code parser and query planner TI-85. |
| |
**Technical Expertise:** Moderate to High | **Technical Expertise:** Moderate to High |
| |
**Presenters:** Bill Erickson (berickxx@gmail.com), Software Development Engineer, King County Library System; Mike Rylander (miker@esilibrary.com), President, Equinox Software; Galen Charlton (gmc@esilibrary.com), Infrastructure and Added Services Manager, Equinox Software | **Presenters:** Bill Erickson (berickxx@gmail.com), Software Development Engineer, King County Library System; Mike Rylander (miker@esilibrary.com), President, Equinox Software; Galen Charlton (gmc@esilibrary.com), Infrastructure and Added Services Manager, Equinox Software |
| |
| ==== Jane in the forest: starting to do Linked Data with Evergreen ==== |
| |
| **Description:** Linked Data has been on the radar of librarians for years, but unless |
| one is already working with RDF triple-stores and the like, it can be |
| a little hard to see how the Linked Data future will look like for |
| ILSs. Adapting some of the ideas of the original Jane-athon |
| [http://www.rdatoolkit.org/janeathon] session at ALA Midwinter 2015 in |
| Chicago, we will go through an exercise of putting together small sets |
| of RDA metadata as RDF... then seeing how that data can be used in the |
| Evergreen. By the end, attendees will have learned a bit not just |
| about the theory of Linked Data, but how working with it can work in |
| practice. |
| |
| **Technical Expertise:** Low to medium |
| |
| **Presenter:** Galen Charlton (gmc@esilibrary.com), Infrastructure and Added Services Manager, Equinox Software |
| |
| ==== Hiding deep in the woods: reader privacy and Evergreen ==== |
| |
| **Description:** Protecting the privacy of our patrons and their reading and |
| information seeking is a core library value -- but one that can be |
| achieved only through constant vigilance. We'll discuss techniques |
| for keeping an Evergreen system secure from leaks of patron data; |
| policies on how much personally identifying information to keep, and |
| for how long; and how to integrate Evergreen with other software |
| securely. |
| |
| //Note: this presentation could also be done with an emphasis suitable for the general track.// |
| |
| **Technical Expertise:** Low to medium |
| |
| **Presenter:** Galen Charlton (gmc@esilibrary.com), Infrastructure and Added Services Manager, Equinox Software |
| |
| ==== Evergreen Search Tune-up: Tips and tricks to taking the default search indexes and making them more awesome ==== |
| |
| Evergreen offers sites a lot of flexibility in adjusting the default indexes that are used for search. In this session, MassLNC Project Coordinator Kathy Lussier will offer a peak into the database to demonstrate how the default search indexes are configured, show where to go when determinig why a particular search didn't work as expected, and discuss the factors that make some records more relevant than others on the results page. She'll also demonstrate how to configure new indexes, either to accommodate a field not covered by the default index or to make specific MARC fields more relevant than others. |
| |
| **Technical Expertise:** Medium |
| |
| **Presenter** Kathy Lussier (klussier@masslnc.org), Project Coordinator, Massachusetts Library Network Cooperative |
| |