Month: June 2008

NASIG 2008: thoughts so far

When NASIG began over 20 years ago, the (then) small conference met on college campuses where (most) everyone stayed in dorm rooms, ate meals together, and socialized in the evenings after the sessions ended. Many of the long-time members missed the social aspects of the campus conferences when the organization outgrew that model and moved to hotel conference centers. This is our first year of meeting at a resort hotel, and so far I have heard mostly good things about the location, and many of them saying that it’s like being in the dorms again, albeit nicer dorms than any college campus I know of.

Sure, it’s more expensive to stay here, and in particular, to eat or drink here, and it’s not within walking distance of anywhere else, but on the other hand, there is a good mix of outdoor and indoor gathering spaces where serendipitous networking and conversations can occur. The weather has been cooperative, staying at a tolerable 90-100° F.

I think I’ve seen and talked to a wider variety of people this year than I have in the past several years. I’m not caught up in running around with my friends at every break. Attendees pass each other along the walkways, stop for a chat by the pool, and gather outside to warm up between sessions in the air conditioned rooms. The sense of community that I felt at my first NASIG conference on the William & Mary campus has been revived a little.

Oh, and it goes without saying that the sessions this year have been excellent.

NASIG 2008: KBart – Best Practices in Knowledge Base Data Transfer

Presenter: Peter McCracken

Librarians understand what OpenURL is and what it does, but not all publishers understand it that well. One of the main problems with OpenURL is making sure that the links work and take users to the content, not to mention making sure that all the links are there which should be.

One thing that libraries often miss is that their link resolvers should include information about their print holdings as well as the electronic ones. [Side note: The non-portability of data from our ILS as noted by Breeding earlier today is part of why that is the case — it’s often more work than we have time for to accurately pull our print holdings data into our link resolvers.]

In order to make the OpenURL process work, content providers need to do most of the work, which includes generating the correct links from sources and sharing the correct information about targets. The library’s responsibility is to ensure that the coverage and content in the knowledge base reflects the license agreement.

The core of the problems we face is metadata. Data provided by publishers, libraries, and vendors all can potentially be broken or incorrect. In a perfect world, all of the metadata would be perfect, but it’s not.

Glen Wiley & the folks at Cornell are doing something about fixing OpenURL syntax errors. Part of the problem with these errors comes from publishers not knowing or understanding what users will be doing with OpenURLs. And, there is often no way to provide feedback to publishers.

Knowledge Bases and Related Tools (KBART) is a UKSG and NISO collaborative project working to provide better data for everyone as well as ensuring the timely transfer of accurate data to ERMS and link resolvers. The core working group meets monthly and includes link resolver/ERMS suppliers, publishers, subscription agents, aggregators, libraries, and consortia. Several groups, including NASIG, are monitoring the process.

KBart seeks to provide best practice guidelines, educational opportunities, and the creation of an information hub for all players. The group has looked at the problems facing the supply chain, developed an initial list of terms that need to be clarified and defined, and started to build a report based around the problems and a supply chain flowchart. They’ve now broken into subgroups to address specific parts and the most relevant bits for each group.

The plan is to finish by this time next year and will present at UKSG, and hopefully NASIG as well. They might go on to create a standard, but will need to determine if it’s appropriate at that time.

Phase II will be focusing on non-textual content. Digital collection managers rejoice!

OpenURL syntax errors potentially can be easily fixed across the board, but a greater challenge is to evaluate and improve the accuracy of the data.

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.

nasig 2008

I am getting ready to fly out to Phoenix early (too early) tomorrow morning for the NASIG annual conference (and executive board meeting). The conference begins on Thursday, but my session blogging probably won’t start until Friday. Posts will be erratic and coming in several at once, most likely, because I won’t be able to upload them until I’m back in my room. We’d like to have free wifi in the conference area, but the Hilton charges more than it costs to fill your gas tank and then some, which is well beyond what this intimate conference can afford to provide.

If you’d like to see what others have to say about NASIG 2008, be sure to check out our nifty little Netvibes page. Kudos to Steve Lawson, who inspired me to put that together this year. If you are attending the conference and plan to blog or post photos on Flickr, be sure to use the nasig2008 tag!

css.php