Search News


Browse Archives

News

Open Minds, Open Books, Open Source

February 19, 2008

Share This Story

FREE Daily News Alerts

Advertisement

As card catalogs once gave way to computers, it might be time for another paradigm shift at libraries.

Last month, a survey by Marshall Breeding, director for innovative technologies and research at Vanderbilt University's library, revealed a measure of discord over the options available to librarians for automating their electronic catalogs and databases, software called integrated library systems. Most libraries use solutions from third-party commercial vendors, paying up-front fees and yearly maintenance charges. "Dissatisfaction and concern prevail," Breeding wrote, "yet some companies maintain exceptional levels of satisfaction from the libraries that use their products."

So librarians aren't exactly reaching for their torches and pitchforks. Still, some libraries, fed up with software that doesn't fully meet their needs, have decided to take matters, figuratively, into their own hands. With a bit of grant money and some eager developers, institutions have begun creating their own open-source solutions that are fully customizable, free for others to use and compatible with existing systems. The result has been a whole crop of projects that, when combined, could serve as a fully integrated, end-to-end open-source solution for academic libraries, covering the interface, search mechanism, database system, citations and even course management.

Meanwhile, the increasing availability of open-source software has nudged some libraries to reconsider the role of their in-house technology gurus, and to wonder whether it would make more long-term financial sense to hire more developers than to continue paying for products over which they have limited control.

"If we truly want to remain relevant, it’s what we have to do,” said Susan Gibbons, an associate dean in the University of Rochester library system.

The code4lib conference, for example, has seen its popularity grow from some 75 attendees in 2006 to a cap of 200 this year, according to Andrew Nagy, who is on the technology management staff at Villanova University's library.

Along with developing their own tools, academic libraries are rethinking which tools they really need.

At Rochester, for example, a $750,000 grant from the Andrew W. Mellon Foundation is helping to fund the eXtensible Catalog (XC) project, a Web 2.0-oriented library catalog interface that is still in development. The software, according to its Web site, will "provide more intuitive access to resources, a customizable interface to include Web 2.0 functionality, and seamless connections to other web applications, such as learning management systems, that a library may already be using." The partnership extends to other universities, each working on a different piece of what they hope will become a full open-source alternative.

Another project that's currently in beta is VuFind, a project that originated at Villanova with Nagy as the lead developer. "We just weren’t happy with our library catalog, the Web component, and we wanted to be able to have our own library catalog that we could customize, change around ... without having to deal with a vendor," he said.

Villanova's library director previously worked as a systems administrator, so Nagy received the green light for his project (without an external grant). It wasn't until six months into the project that his team decided to take it open source, he said -- a decision that allowed the university to work with developers at other institutions and test the software on different platforms. At the moment, the university continues to operate the third-party Voyager system while funding the VuFind Web catalog. But eventually, Nagy said, the hope is to move to an all-open-source solution and invest more in in-house developers, a shift that could serve to save costs in the long run.

Open-source Web catalogs like VuFind tend to look a lot like search engines that people who work online are already used to. VuFind (and, eventually, XC) adds Web 2.0 functionality on top of the traditional interface, allowing users to e-mail search results and save results to their favorites. One feature Nagy said was a high priority for library developers is "faceted navigation," which allows users to drill down and refine searches by, for example, author, topic or format. The VuFind interface is also completely compatible with the open-source citation management tool Zotero, a plugin for the Firefox browser.

Another piece of the puzzle is federated search: an engine that sifts through numerous different databases for each user query. One tool being developed at Oregon State University, LibraryFind, combines federated search with a simple, Google-like interface that lets users sort by relevance, save items, refine searches and view electronic documents.

“The more we could simplify the experience, the better people reacted to it," said Jeremy Frumkin, the Gray Family Chair for Innovative Library Services. He said the challenge was often to refine the interface to make it more user-friendly, and to aid as much as possible in the "discovery" portion of the research process.

There's a “growing disconnect in what we’re being provided from commercial companies ... and what libraries are starting to realize they need,” he said, but libraries aren't blameless either: He believes they need to communicate more effectively the features and functionality they require. And just because it's open source doesn't mean it's better. Soon enough, Gibbons suggested, open source innovations might spur competition and eventually result in more and better choices in the consumer market.

See all postings »
Advertisement
Advertisement

Matching Jobs

Comments on Open Minds, Open Books, Open Source

  • Posted by David Dorman on February 19, 2008 at 11:40am EST
  • Nice article, Andy, but you neglected to mention the most feature rich, mature and widely deployed LMS and federated search open source software.

    Evergreen, Koha and OPALS-NA are three open source library management systems. Together they are used by many hundreds if not thousands of libraries.

    Lucene and Zebra are two very robust and sophisticated open source indexing engines that are both widely used within proprietary as well as open source library management systems.

    Pazpar2 is open source federated search software that is currently in use by the Library of Congress as well as a few state agencies and University libraries, and is being tested and deployed in many other libraries around the world.

  • Blacklight
  • Posted by Leslie Johnston on February 19, 2008 at 12:30pm EST
  • The University of Virginia Library has just released the code for their Blacklight catalog interface using Lucene/Solr: http://rubyforge.org/projects/blacklight/

  • Posted by Tom McNulty on February 19, 2008 at 1:00pm EST
  • Nice article but it does fail to make mention of what these libraries are doing for in-house processing. Having an opensource, web 2.0 OPAC is a good place to start but if the library is going to fully break their dependence on proprietary vendor owned software robust systems have to be in place for circulation, acquisitions, and cataloging as well.

  • How About Greenstone
  • Posted by MIchael Dean on February 19, 2008 at 5:40pm EST
  • Open Source is worldwide, and so are the concerns of libraries. Don't forget the greenstone project. It is mature open source for libraries.

  • Greenstone
  • Posted by David Dorman on February 19, 2008 at 9:20pm EST
  • Michael, let's be careful not to mix apples and oranges. The article was about open source library management systems and also mentioned federated searching.

    Greenstone is a content management system, which is its own unique type of software. Open Source CMS software trends could be an article by itself.

  • Open Source library source systems
  • Posted by Marilyn Quinn , Bibliographic Control Librarian on February 20, 2008 at 6:15pm EST
  • I think it's great that so many libraries are designing their own open source systems. I would like to remind everyone, however, that many small institutions are also not happy with the pace of change in our commercial ILS. But we do not have the advantage of a large staff with the time and permission to design or customize what is available, including currently available Open Source systems. I am looking at Open Source systems, but if we go with one, we will have to find one that doesn't need too many technical modifications and which provides some support for our questions and special needs.

  • open source for smaller libraries
  • Posted by Alison on February 20, 2008 at 7:50pm EST
  • I attended a koha demonstration and they provide any level of support you require (for a fee of course but nothing like a traditional ILS) and seem that they are a great resource for smaller libraries.

  • Koha
  • Posted by Rachael , Ms at Australian Catholic University on February 21, 2008 at 12:30am EST
  • My colleagues at Philanthropy Australia use Koha for their catalogue (http://library.philanthropy.org.au/cgi-bin/koha/opac-search.pl) and they are a one-person library. I'm told the Koha people are very supportive.

  • Development Direction
  • Posted by Roman Panchyshyn , Librarian on February 21, 2008 at 9:50am EST
  • Many of the discussions around open source deal with libraries breaking their relationships with traditional ILS vendors. Let's push that a step further with other vendors such as publishers and bibliographic databases such as OCLC. The entire bibliographic process, from discovery to access, still depends on the presence of a bibliographic "record" of some kind. OCLC's WorldCat at this time is the closest we have to a global database of bibliographic records. While limited access to the database is free through WorldCat.org, libraries are still charged for various services that make their collections "visible", such as the ability to set/delete holdings or the ability to click through via URL resolvers to access the requested materials at libraries. A true open source model would need access to an open, global source of bibliographic records or provide access to a global bibliographic database. WorldCat may evolve into the database of choice, but there is always the possibility that an alternative may evolve, such as a global "Amazon", since it is advantageous to the publishers to provide metadata to allow us to find (and buy) their products. My guess is that entities with adequate funding may have a not so subtle impact on the direction of the open source model.

    Another question that I would ask is this. If WorldCat, or something else, develops into the global source of bibliographic data, why bother to even develop local cataloging modules for your open source ILS? Patrons can use the global catalog for discovery, all your local catalog would need to do is to handle circulation (access), patron data, and acquisitions.

  • Posted by Glen Newton , Experimental Interfaces: Project Ungava on February 24, 2008 at 8:10am EST
  • We are using Lucene as the basis of experimental library catalogue indexes that include new ways of searching and doing search refinement. Project Ungava (http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/Ungava) integrates both library metadata and article full-text. It also includes new ways of refining search including drill clouds (http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/Drill_Clouds#Drill_Clouds) and faceted search using Simile Exhibit.

  • Drupal Library Sites + OPAC
  • Posted by Alejandro Garza , Director, Library Tech & Innovation at Monterrey Tech on February 27, 2008 at 11:20am EST
  • Some sites have successfully incorporated Drupal (an open source CMS) as their Library website solution, and in some cases, to serve as the main OPAC. The main example is http://aadl.org which operates Millennium, but is using Drupal as the frontend to users instead of the Millennium Web Opac module.

    We are currently testing Drupal as an OPAC, interoperating with our Millennium system.

    You can add most any function to Drupal either from available modules or ones you cook up yourself. This means we will have an extensible framework, so we can add (at a whim) things like faceted searching, Amazon linking, Google CSE, Wiki-like pages, reviews, votes, comments, polls, RSS feeds (outgoing AND incoming), theming, localization, internationalization... and tons more. You can check out our demo Drupal OPAC at http://enlinea.mty.itesm.mx/

    For more libraries using Drupal, check out:
    http://drupalib.interoperating.info/

  • Koha
  • Posted by Chadwick Seagraves , Library Systems Analyst at Private Academic Library Network of Indiana (PALNI) on February 29, 2008 at 10:55am EST
  • The Indiana Cooperative Library Services Authority (INCOLSA) is migrating 30 member libraries composing the Indiana Shared Library Catalog (ISLC) to Koha Zoom. Excited to see this happening.

  • What about the Indiana Evergreen project? Is that related?
  • Posted by John McCormick on March 2, 2008 at 12:00pm EST
  • Chadwick (et al):

    Can someone clarify for me the difference between the INCOLSA Koha project and the Indiana State Library's Evergreen project?

    http://www.in.gov/library/5405.htm