Internet Librarian 2010 is just around the corner

Monterey is awesome! #il2009
from Internet Librarian 2009

I’m heading off to Internet Librarian later this week, and let me tell you, I’m pretty excited about it! There will be lots of sharing of ideas, both in sessions and later over beers. I’ll also be giving a presentation on Wednesday morning on electronic resources workflow tips & tricks, along with my colleagues Emily McElroy and Bonnie Parks. I’m not sure if I want a large audience (yikes!) or a small audience (*sad panda*), as both come with their unique panic moments.

Here are the sessions I’m planning to attend, which will likely change while I’m there, and some are double-booked, so I’ll have to make an on-the-spot decision about which to attend:

Sunday

  • Gaming & Gadgets Petting Zoo

Monday

  • Adding Value to Your Community
  • Dashboards, Data, and Decisions
  • Managing Your Library’s Online Presence
  • Next Gen Discovery Systems OR Beyond 23 Things: For Staff & for Patrons

Tuesday

  • Adding Value: CIO Insights
  • Personal Content Management
  • Failcamp OR Applying User Experience (UX) Design
  • Augmented Reality & Libraries OR Patron-Driven Ebook Acquisition
  • Videocasting, Innovating, & Creating New Ideas
  • Rip Van Winkle’s Libraries in 2510

Wednesday

  • Planning & Designing for Attention
  • Tips, Tricks, & Workflows for Managing Digital Resources <– that’s mine
  • Best Free Web Stuff for Broke Libraries
  • Digital Librarianship: Open Access & Web 2.0
  • Adding Value Through Visualization

CIL 2009: CM Tools: Drupal, Joomla, & Rumba

Speaker: Ryan Deschamps

In the end, you will install and play with several different content management systems until you find the right one for your needs. A good CMS will facilitate the division of labor, support the overall development of the site, and ensure best practices/standards. It’s not about the content, it’s about the cockpit. You need something that will make your staff happy so that it’s easy to build the right site for your users.

Joomla was the #1 in market share with good community support when Halifax went with it. Ultimately, it wasn’t working, so they switched to MODx. Joomla, unfortunately, gets in the way of creative coding.

ModX, unlike Joomla, has fine-grain user access. Templates are plain HTML, so no need to learn code specific to the CMS. The community was smaller, but more engaged.

One feature that Deschamps is excited about is the ability to create a snippet with pre-set options that can be inserted in a page and changed as needed. An example of how this would be used is if you want to put specific CC licenses on pages or have certain images displayed.

The future: "application framework" rather than "content management system"

Speaker: John Blyberg

Drupal has been named open source CMS of the year for the past two years in part due to the community participation. It scales well, so it can go from being a small website to a large and complex one relatively easily. However, it has a steep learning curve. Joomla is kind of like Photoshop Elements, and Drupal is more like the full Photoshop suite.

Everything you put into Drupal is a node, not a page. It associates bits of information with that node to flesh out a full page. Content types can be classified in different ways, with as much diversity as you want. The taxonomies can be used to create the structure of your website.

[Blyberg showed some examples of things that he likes about Drupal, but the detail and significance are beyond me, so I did not record them here. You can probably find out more when/if he posts his presentation.]

NASIG 2008: Next Generation Library Automation – Its Impact on the Serials Community

Speaker: Marshall Breeding

Check & update your library’s record on lib-web-cats — Breeding uses this data to track the ILS and ERMS systems used by libraries world-wide.

The automation industry is consolidating, with several library products dropped or ceased to be supported. External financial investors are increasingly controlling the direction of the industry. And, the OPAC sucks. Libraries and users are continually frustrated with the products they are forced to use and are turning to open source solutions.

The innovation presented by automation companies falls below the expectations of libraries (not so sure about users). Conventional ILS need to be updated to incorporate the modern blend of digital and print collections.

We need to be more thoughtful in our incorporation of social tools into traditional library systems and infrastructures. Integrate those Web 2.0 tools into existing delivery options. The next NextGen automation tools should have collaborative features built into them.

Open source software isn’t free — it’s just a different model (pay for maintenance and setup v. pay for software). We need more robust open source software for libraries. Alternatively, systems need to open up so that data can be moved in and out easily. Systems need APIs that allow local coders to enhance systems to meet the needs of local users. Open source ERMS knowledge bases haven’t been seriously developed, although there is a need.

The drive towards open source solutions has often been motivated by disillusionment with current vendors. However, we need to be cautious, since open source isn’t necessarily the golden key that will unlock the door to paradise. (i.e. Koha still needs to add serials and acquisitions modules, as well as EDI capabilities).

The open source movement motivates the vendors to make their systems more open for us. This is a good thing. In the end, we’ll have a better set of options.

Open Source ILS options: Koha (commercial support from LibLime) used mostly by small to medium libraries, Evergreen (commercial support from Equinox Software) tested and proven for small to medium libraries in a consortia setting, and OPALS (commercial support from Media Flex) used mostly by k-12 schools.

In making the case for open source ILS, you need to compare the total cost of ownership, the features and functionality, and the technology platform and conceptual models. Are they next-generation systems or open source versions of legacy models?

Evaluate your RFPs for new systems. Are you asking for the things you really need or are you stuck in a rut of requiring technology that was developed in the 70s and may no longer be relevant?

Current open source ILS products lack serials and acquisitions modules. The initial wave of open source ILS commitments happened in the public library arena, but the recent activity has been in academic libraries (WALDO consortia going from Voyager to Koha, University of Prince Edward Island going from Unicorn to Evergreen in about a month). Do the current open source ILS products provide a new model of automation, or an open source version of what we already have?

Looking forward to the day when there is a standard XML for all ILS that will allow libraries to manipulated their data in any way they need to.

We are working towards a new model of library automation where monolithic legacy architectures are replaced by the fabric of service oriented architecture applications with comprehensive management.

The traditional ILS is diminishing in importance in libraries. Electronic content management is being done outside of core ILS functions. Library systems are becoming less integrated because the traditional ILS isn’t keeping up with our needs, so we find work-around products. Non-integrated automation is not sustainable.

ERMS — isn’t this what the acquisitions module is supposed to do? Instead of enhancing that to incorporate the needs of electronic resources, we had to get another module or work-around that may or may not be integrated with the rest of the ILS.

We are moving beyond metadata searching to searching the actual items themselves. Users want to be able to search across all products and packages. NextGen federated searching will harvest and index subscribed content so that it can be searched and retrieved more quickly and seamlessly.

Opportunities for serials specialists:

  • Be aware of the current trends
  • Be prepared for accelerated change cycles
  • Help build systems based on modern business process automation principles. What is your ideal serials system?
  • Provide input
  • Ensure that new systems provide better support than legacy systems
  • Help drive current vendors towards open systems

How will we deliver serials content through discovery layers?

Reference:

  • “It’s Time to Break the Mold of the Original ILS,” Computers in Libraries, Nov/Dec 2007.