Go to:
Online Doc
Meeting Request
Robert Nunez's picture

Midwinter 2016 Meeting Notes

Sunday, 10 January 2016, 15:00-16:00


Current chair, Vicki Teal Lovely, was unable to attend

Approximately 15 attendees


Incoming chair: Robert Nunez from Kenosha Public Library in Wisconsin

Incoming vice chair:  Jake Ineichen from Madison Public Library



- The LITA Education Committee will be issuing a  CFP for webinars in the next few weeks

- There was a discussion of potential topics for webinars:

- Blacklight

- options for digital collections: e.g., Omeka, Hydra

- open source projects for public services tools

- Git (e.g., Git for non-programmers)

- Offer training at different levels. This can be handled by LITA Education Comm.

General action item for the IG

- Ideas for ALA Annual Programs

- WordPress vs. Drupal vs. CMS

- OS vs Closed Source Equivalent

- Koha vs. Evergreen

- more generally, project/product comparisons

Open discussion

Kuali OLE

  - three implementations: Lehigh, Chicago, U. London; Duke going live this summer

  - Penn "inching towards implementation"

  - discussion on number of programmers required

  - there is at least one company that may bid on hosting Kuali OLE (HTC Global)

  - doesn't have a front-end: most implementations using Vufind as front end/discovery interface

  - staff interface is web-based

  - Kuali spun off a commercial arm; OLE is discussing whether to move development there

  - changing license from ECL to AGPL3

  - project currently stripping out a lot of financial systems cruft out of acquisitions;

    didn't need the full Kuali financial system

  - authentication providers

Agile development

  - be careful about implementing Agile to the letter without taking team dynamics into


  - Agile practices that can work well in isolation: scrum, tests before code,

    use cases before code, sprints

  - considering Agile? read more than overview of it

  - discussion of what scrums are

  - WORKSHOP/PRECONFERENCE IDEA: Agile development in libraries

    - Beth Camden mentioned example of a workshop she recently attending on Agile: Martians visiting Earth for Vacation


Process of migrating to open source systems

  - flexibility

  - staff users can be closer to the developers

- asking Beth - frustration with OLE

  - harder than expected; takes time

  - OSS: very public; proprietary vendors can have same problems but sometimes hide it

- compromises

  - authority control in OLE; Linked Data visions not compatible with discussions with

    line catalogers

  - OLE decided not to do predictive serials checkin

- how does your library decide to adopt OSS?

  - can be easy to make decision: example of public library unable to afford Windows upgrades; quickly decided to move to Linux for public workstations

  - higher ed: perception that "official" support isn't available

  - can library afford the time/expense of staff climbing the learning curve?

  - difference between how digital repos and ILS are viewed w.r.t to open source: academic libraries are much more likely to adopt F/LOSS for digital repositories

  - question of name recognition: higher ed admins recognize "OCLC" and the like

  - POSSIBLE SESSION IDEA to discuss that "brand recognition" issue (What is OS? How do you get support/Customizations?)

- F/LOSS communities as user groups on steroids

  - less inhibition against sharing information