User Tools

Site Tools


conference:2015:proposals

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
conference:2015:proposals [2015/03/03 22:07] – Last-minute submission from kmlussier klussierconference:2015:proposals [2022/02/10 13:34] (current) – external edit 127.0.0.1
Line 1: Line 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.
  
Line 164: Line 166:
 **Presenter(s):** Grace Dunbar (grace@esilibrary.com), Vice President, Equinox Software **Presenter(s):** Grace Dunbar (grace@esilibrary.com), Vice President, Equinox Software
  
-==== Getting what you want in your next development project ====+==== 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
  
-Hooray! You've finally raised the funds you need for the new enhancement you want to roll into EvergreenYou contract with a developerthe work is doneand, 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.+**Presenter(s):** Dan Wells (dbw2@calvin.edu)Library Programmer/AnalystHekman Library (Calvin College)
  
-**Technical Expertise:** None+==== Getting what you want in your next development project ====
  
-**Presenter:** Kathy Lussier (klussier@masslnc.org), Project Coordinator, Massachusetts Library Network Cooperative 
  
-==== Evergreen and Design: From UX to UI ==== +Hooray! You've finally raised the funds you need for the new enhancement you want to roll into Evergreen. You contract with 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.
-  +
-**Description:** A piece of software is only as good as its user interface (UI) With no UI, 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 designand 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 **Technical Expertise:** None
  
-**Presenter(s):** Dan Wells (dbw2@calvin.edu), Library Programmer/AnalystHekman Library (Calvin College)+**Presenter:** Kathy Lussier (klussier@masslnc.org), Project CoordinatorMassachusetts Library Network Cooperative
  
 =====Technical Track===== =====Technical Track=====
Line 209: Line 211:
 **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.
Line 220: Line 222:
 ==== 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
conference/2015/proposals.1425438453.txt.gz · Last modified: 2022/02/10 13:33 (external edit)

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki

© 2008-2022 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a U.S. 501(c)3 non-profit organization.