| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| conference:2015:proposals [2015/03/03 15:39] – [Oh! The Places Acquisitions Can Go!] csharp | conference:2015:proposals [2022/02/10 13:34] (current) – external edit 127.0.0.1 |
|---|
| | ====== 2015 Proposals ====== |
| | |
| The 2015 Evergreen International Conference is May 13-16, 2015 in Hood River, Oregon. The deadline for submitting proposals is Friday, Feburary 27, 2015. | The 2015 Evergreen International Conference is May 13-16, 2015 in Hood River, Oregon. The deadline for submitting proposals is Friday, Feburary 27, 2015. |
| |
| |
| >>>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.) | >>>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. | >>>--__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. | 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):** Grace Dunbar (grace@esilibrary.com), Vice President, Equinox Software | **Presenter(s):** Grace Dunbar (grace@esilibrary.com), Vice President, Equinox Software |
| |
| |
| ==== Evergreen and Design: From UX to UI ==== | ==== Evergreen and Design: From UX to UI ==== |
| |
| **Presenter(s):** Dan Wells (dbw2@calvin.edu), Library Programmer/Analyst, Hekman Library (Calvin College) | **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. |
| ==== 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 |
