NASIG 2009: Moving Mountains of Cost Data

Standards for ILS to ERMS to Vendors and Back

Presenter: Dani Roach

Acronyms you need to know for this presentation: National Information Standards Organization (NISO), Cost of Resource Exchange (CORE), and Draft Standard For Trial Use (DSFTU).

CORE was started by Ed Riding from SirsiDynix, Jeff Aipperspach from Serials Solutions, and Ted Koppel from Ex Libris (and now Auto-Graphics). The saw a need to be able to transfer acquisitions data between systems, so they began working on it. After talking with various related parties, they approached NISO in 2008. Once they realized the scope, it went from being just an ILS to ERMS transfer to also including data from your vendors, agents, consortia, etc, but without duplicating existing standards.

Library input is critical in defining the use cases and the data exchange scenarios. There was also a need for a data dictionary and XML schema in order to make sure everyone involved understood each other. The end result is the NISO CORE DSFTU Z39.95-200x.

CORE could be awesome, but in the mean time, we need a solution. Roach has a few suggestions for what we can do.

Your ILS has a pile of data fields. Your ERMS has a pile of data fields. They don’t exactly overlap. Roach focused on only eight of the elements: title, match point (code), record order number, vendor, fund, what paid for, amount paid, and something else she can’t remember right now.

She developed Access tables with output from her ILS and templates from her ERMS. She then ran a query to match them up and then upload the acquisitions data to her ERMS.

For the database record match, she chose the Serials Solutions three letter database code, which was then put into an unused variable MARC field. For the journals, she used the SSID from the MARC records Serials Solutions supplies to them.

Things that you need to decide in advance: How do you handle multiple payments in a single fiscal year (What are you doing currently? Do you need to continue doing it?)? What about resources that share costs? How will you handle one-time vs. ongoing purchase? How will you maintain the integrity of the match point you’ve chosen?

The main thing to keep in mind is that you need to document your decisions and processes, particularly for when systems change and CORE or some other standard becomes a reality.

NASIG 2009: Ensuring Perpetual Access to Online Subscriptions

Presenters: Judy Luther (moderator), Ken DiFiore, Nancy Gibbs (contributed, but not able to attend), Selden Lamorueux, Victoria Reich, Heather Ruland Staines, and Kim Steinle

Librarians have asked publishers to ensure that they will have perpetual access available to paid subscribers, which is a reverse of the previous arrangement with print, which required the librarians to preserve access to the physical copy in their buildings. It took publishers some time to address this, and it continues to evolve.

Libraries, and academic libraries in particular, have proven staying power. Librarians, working with publishers, are responsible for providing access to information.

There are two issues with online perpetual access: maintaining access to content when a subscription ends and maintaining access to content when a publisher ceases to exist. Libraries have the resources to be custodians of the content through digital preservation practices, both alone and in community.

How are librarians & publishers managing expectations for the financial impact of moving to online-only content? First, make sure that there is some sort of preservation guarantee. You will need to start shifting staff from managing stacks/materials to managing online, which will impact training needs. There are cost savings in space and opening up the building to other relevant uses. Peter McCracken suggests that we should emphasize the service and benefits of online content.

Libraries purchase the delivery mechanism, not the content. Owning a print archive does not mean that online is automatically free. And, it’s not just the content that you get with online. The user interface is an essential component, and it isn’t cheap to develop or maintain.

The most important thing that librarians need to do is read the license agreement. If it doesn’t specify what happens to content if a subscription is canceled or if the publisher ceases to exist, negotiate for that to be added. CYA, folks! If you pay for it, make sure you’re really going to get it.

NASIG 2009: Ambient Findability

Libraries, Serials, and the Internet of Things

Presenter: Peter Morville

He’s a librarian that fell in love with the web and moved into working with information architecture. When he first wrote the book Information Architecture, he and his co-author didn’t include a definition of information architecture. With the second edition, they had four definitions: the structural design of shared information environments; the combination of organization, labeling, search, and navigation systems in webs sites and intranet; the art and science of shaping information products and experiences to support usability and finadability; an emerging discipline and community of practice focused on bringing principles of designing and architecture to the digital landscape.

[at this point, my computer crashed, losing all the lovely notes I had taken so far]

Information systems need to use a combination of categories (paying attention to audience and taxonomy), in-text linking, and alphabetical indexes in order to make information findable. We need to start thinking about the information systems of the future. If we examine the trends through findability, we might have a different perspective. What are all the different ways someone might find ____? How do we describe it to make it more findable?

We are drowning in information. We are suffering from information anxiety. Nobel Laureate Economist Herbert Simon said, “A wealth of information creates a poverty of attention.”

Ambient devices are alternate interfaces that bring information to our attention, and Moreville thinks this is a direction that our information systems are moving towards. What can we now do when our devices know where we are? Now that we can do it, how do we want to use it, and in what contexts?

What are our high-value objects, and is it important to make them more findable? RFID can be used to track important but easily hidden physical items, such as wheelchairs in a hospital. What else can we do with it besides inventory books?

In a world where for every object there are thousands of similar objects, how do we describe the uniqueness of each one? Who’s going to do it? Not Microsoft, and not Donald Rumsfeld and his unknown unknown. It’s librarians, of course. Nowadays, metadata is everywhere, turning everyone who creates it into librarians and information architects of sorts.

One of the challenges we have is determine what aspects of our information systems can evolve quickly and what aspects need more time.

In five to ten years from now, we’ll still be starting by entering a keyword or two into a box and hitting “go.” This model is ubiquitous and it works because it acknowledges human psychology of just wanting to get started. Search is not just about the software. It’s a complex, adaptive system that requires us to understand our users so that they not only get started, but also know how to take the next step once they get there.

Some example of best and worse practices for search are on his Flickr. Some user-suggested improvements to search are auto-compete search terms, suggested links or best bets, and for libraries, federated search helps users know where to begin. Faceted navigation goes hand in hand with federated search, which allows users to formulate what in the past would have been very sophisticated Boolean queries. It also helps them to understand the information space they are in by presenting a visual representation of the subset of information.

Morville referenced last year’s presentation by Mike Kuniavsky regarding ubiquitous computing, and he hoped that his presentation has complemented what Kuniavsky had to say.

Libraries are more than just warehouses of materials — they are cathedrals of information that inspire us.

PDF of his slides

a response to rewarding conference speakers

As I was sitting in a CIL2009 session that was essentially something that could have easily been a blog post with a bunch of annotated links, I wondered to myself why this was chosen to be a session over something else, and why I had chosen to attend it rather than something else. I concluded that sometimes I need to have something whack me upside the head to “get it,” and a good presentation is often the best tool to do it.

Kathryn Greenhill writes, “I suspect it’s not that I *know* it all, but that I know how to find out at point of need and that I am more likely to use my human networks than to look back at conference notes or handouts to find out.” I rely heavily on my human networks, both in person and online, to keep me informed of the things I need to know — much more so than professional literature and formal presentations. However, sometimes even those things can spark an idea or clarify something that was previously muddy in my mind. I’m happy to reap the benefits of shared information, regardless of what format is used to deliver it.

That’s all fine and good for me, someone who is only moderately on the side of information creator and more on the side of information consumer, but what about those “shovers and makers” out there who are generating new ideas and, well, shoving and making in libraryland? Greenhill notes that she has “found much, much more value hanging about talking to other presenters than in attending the formal sessions,” and she suggests that rather than cheesy speakers’ gifts, they could instead be given “something to stimulate the presenters’ brains and challenge them.”

I like the idea of this, but I also worry that it has the potential to widen the gap between creators and consumers. I benefit greatly from being able to listen in on the discussions between the speakers in LobbyCon/CarpetCon settings. And, even when I am in sessions that challenge my skill set, I am motivated to expand that skill set, or at the very least, I know more about what I don’t know. I’d rather have that than continue in ignorance.

Greenhill, along with Cindi Trainor and John Blyberg, spent many hours during Computers in Libraries secluded away while crafting The Darien Statements on the Library and Librarians manifesto. The end result is available to us, but I wonder how much more we consumers would have learned by being able to listen in on the process of its creation? Isn’t that part of what the unconference movement is about?

CIL 2009: ERM… What Do You Do With All That Data, Anyway?

This is the session that I co-presented with Cindi Trainor (Eastern Kentucky University). The slides don’t convey all of the points we were trying to make, so I’ve also included a cleaned-up version of those notes.

  1. Title
  2. In 2004, the Digital Library Federation (DLF) Electronic Resources Management Initiative (ERMI) published their report on the electronic resource management needs of libraries, and provided some guidelines for what data needed to be collected in future systems and how that data might be organized. The report identifies over 340 data elements, ranging from acquisitions to access to assessment.

    Libraries that have implemented commercial electronic resource management systems (ERMS) have spent many staff hours entering data from old storage systems, or recording those data for the first time, and few, if any, have filled out each data element listed in the report. But that is reasonable, since not every resource will have relevant data attached to it that would need to be captured in an ERMS.

    However, since most libraries do not have an infinite number of staff to focus on this level of data entry, the emphasis should instead be placed upon capturing data that is neccessary for managing the resources as well as information that will enhance the user experience.

  3. On the staff side, ERM data is useful for: upcoming renewal notifications, generating collection development reports that explain cost-per-use, based on publisher-provided use statistics and library-maintained, acquisitions data, managing trials, noting Electronic ILL & Reserves rights, and tracking the uptime & downtime of resources.
  4. Most libraries already have access management systems (link resolvers, A-Z lists, Marc records).
  5. User issues have shifted from the multiple copy problem to a “which copy?” problem. Users have multiple points of access, including: journal packages (JSTOR, Muse); A&I databases, with and without FT (which constitute e-resources in themselves); Library website (particularly “Electronic Resources” or “Databases” lists); OPAC; A-Z List (typically populated by an OpenURL link resolver); Google/gScholar; article/paper references/footnotes; course reserves; course management systems (Blackboard, Moodle, WebCT, Angel,Sakai); citation management software (RefWorks, EndNote, Zotero); LibGuides / course guides; bookmarks
  6. Users want…
  7. Google
  8. Worlds collide! What elements from the DLF ERM spec could enhance the user experience, and how? Information inside an ERMS can enhance access management systems or discovery: subject categorization within the ERM that would group similar resources and allow them to be presented alongside the resource that someone is using; using statuses to group & display items, such as a trialset within the ERM to automatically populate a page of new resources or an RSS feed to make it easy for the library to group and publicize even 30 day trial. ERMS’s need to do a better job of helping to manage the resource lifecycle by being built to track resources through that lifecycle so that discovery is updated by extension because resources are managed well, increasing uptime and availability and decreasing the time from identification above potential new resource to accessibility of that resource to our users
  9. How about turning ERM data into a discovery tool? Information about accessibility of resources to reference management systems like Endnote, RefWorks, or Zotero, and key pieces of information related to using those individual resources with same, could at least enable more sophisticated use of those resources if not increased discovery.

    (You’ve got your ERM in my discovery interface! No, you got your discovery interface in my ERM! Er… guess that doesn’t quite translate.)

  10. Flickr Mosaic: Phyllotaxy (cc:by-nc-sa); Librarians-Haunted-Love (cc:by-nc-sa); Square Peg (cc:by-nc-sa); The Burden of Thought (cc:by-nc)

CIL 2009: What’s Hot in RSS

Speaker: Steven M. Cohen

  • Zoho – somewhat more popular than Google Docs
  • YouTube RSS search – only the top 10 of any search, however, if you use youtube/rss/search/<search term>.rss, you will get it all
  • X – nothing
  • WwwhatsNew – Spanish language cool tools
  • Votes Database – Washington Post hosted profiles of congressional members including RSS feed of current voting record
  • JD Supra (it has a U in it) – documents that lawyers are putting up online to be shared by anyone (marketing/social tool)
  • Tic Tocs – table of contents RSS for any journal that has it, aggregated in one location
  • Scribd – YouTube for documents
  • Ravelry – social networking for knitters
  • QuestionPoint
  • Page2RSS – creates a feed of daily changes to web pages
  • Open Congress – feeds of congressional action about people, committees, issues, bills, etc.
  • N – nothing
  • Mashable – top tech trends in social networking
  • LibraryThing – "the future of what catalogs will look like"
  • KillerStartups – description and evaluation of new websites & applications
  • Justia Dockets – Federal District Court Filings & Documents, RSS feeds for search results
  • I Want To – …missed this one…
  • Hunch – new site, hasn’t been launched yet, created by the Flickr woman
  • Google Reader – taking over Bloglines; can share items with comments, but the comments are private (I think) instead of the notes, which still exist
  • Facebook – yeah
  • E-Hub – not sure what makes this cool, but he listed it
  • Deepest Sender – Firefox extension for blogging links
  • Compfight – CC/Flickr image search (can limit to CC only)
  • Backup URL – creates a backup of any URL in case it goes down — great for presentations
  • Awesome Highlighter – highlight text on web pages and then get a link to it

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.]

CIL 2009: Open Access: Green and Gold

Presenter: Shane Beers

Green open access (OA) is the practice of depositing and making available a document on the web. Most frequently, these are peer reviewed research and conference articles. This is not self-publishing! OA repositories allow institutions to store and showcase the research output of institutions, thus increasing their visibility within the academic community.

Institutional repositories are usually managed by either DSpace, Fedora, or EPrints, and there are third-party external options using these systems. There are also a few subject-specific repositories not affiliated with any particular institution.

The "serials crisis" results in most libraries not subscribing to every journal out there that their researchers need. OA eliminates this problem by making relevant research available to anyone who needs it, regardless of their economic barriers.

A 2008 study showed that less than 20% of all scientific articles published were made available in a green or gold OA repository. Self-archiving is at a low 15%, and incentives to do so increase it only by 30%. Researchers and their work habits are the greatest barriers that OA repository managers encounter. The only way to guarantee 100% self-archiving is with an institutional mandate.

Copyright complications are also barriers to adoption. Post-print archiving is the most problematic, particularly as publishers continue to resist OA and prohibit it in author contracts.

OA repositories are not self-sustaining. They require top-down dedication and support, not only for the project as a whole, but also the equipment/service and staff costs. A single "repository rat" model is rarely successful.

The future? More mandates, peer-reviewed green OA repositories, expanding repositories to encompass services, and integration of OA repositories into the workflow of researchers.

Presenter: Amy Buckland

Gold open access is about not having price or permission barriers. No embargos with immediate post-print archiving.

The Public Knowledge Project is an easy tool for creating an open journal that includes all the capabilities of online multi-media. For example, First Monday uses it.

Buckland wants libraries to become publishers of content by making the platforms available to the researchers. Editors and editorial boards can come from volunteers within the institution, and authors just need to do what they do.

Publication models are changing. May granting agencies are requiring OA components tied with funding. The best part: everyone in the world can see your institution’s output immediately!

Installation of the product is easy — it’s getting the word out that’s hard.

Libraries can make the MARC records freely available, and ensure that the journals are indexed in the Directory of Open Access Journals.

Doing this will build relationships between faculty and the library. Libraries become directly involved in the research output of faculty, which makes libraries more visible to administrators and budget decision-makers. University presses are struggling, but even though they are focused on revenue, OA journal publishing could enhance their visibility and status. Also, if you publish OA, the big G will find it (and other search engines).

CIL 2009: Open Source Library Implementations

Speakers: Karen Kohn and Eric McCloy

Preparing for moving from a traditional ILS to Koha.

They were frustrated with not being able to get at the data in their system, and it was cost-prohibitive to gain access. The user interface was locked into a particular design that was difficult to modify or make ADA-compliant. Staff clients had to be updated on each computer, which was a time-consuming process.

They have a strong IT-library partnership, which meant they knew they could work with a system that needs that kind of support.

How they did it (Fall 2008): dropped "discovery layer" product from their ILS, use the savings to get their federated search working, started doing nightly dumps of records from ILS to Koha (using ILS as back-end, Koha as the user interface), designed web interface (Drupal), and set up a Z39.50 interface to search Koha. Eventually they will be putting Koha out for native searching. Currently, they are testing and de-bugging, and have plans to roll out the migration this summer (2009).

Every once in a while, librarians need to be reminded that [insert tech glitch] is only temporary and everything will be corrected eventually, so don’t fret over the details to the point of getting distracted from the goal.

[Commentary: My library looked at Koha last year, but we need something that can handle acquisitions and serials, and Koha wasn’t at that point yet. It did not occur to me, and I don’t think it occurred to anyone else, that we could use our current ILS for staff and administrative things and make Koha our user interface, which is where it currently excels.]

CI 2009: Unconferences

Presenters: Steve Lawson, Stephen Francoeur, John Blyberg, and Kathryn Greenhill

KG began by asking the audience to share what questions they have about unconferences while SL took notes on a flip chart. Lots of good questions covering a variety of aspects, including all the questions I have.

Keep in mind: who ever comes are the right people; whatever happens is the only thing that could have happened; whenever it starts is the right time. Also keep in mind the law of two feet. If you are in a situation where you are neither getting nor receiving anything of value, then change that or leave.

Many people indicate that they get a lot out of the space inbetween sessions at traditional conferences, and this is what unconferences try to capture. Libraries can also host general unconferences, such as what Deschamps did in Halifax. It doesn’t have to be just library stuff.

You can’t prepare for every aspect of an unconference. You can prepare the space and request that specific people be there, but in the end, its success is based on the engagement of the participants.

Unconferences are casual. You do need to decide the level of casual, such as how much you want to borrow from traditional conference amenities and structure. Organizational sponsorships should be limited to affiliation and financial support — avoid letting them dictate what will happen.

Keynote sessions can influence the conversations that happen afterwards, so be deliberate about whether or not to have one.

The less you have to deal with money the better, and there are pros and cons to having fees. Keep the threshold low to encourage participation. Every day is a bad day for somebody, so just choose a date and time.

Tip: organize an unconference the day before or after a national conference. Folks are coming and going, and it’s easier to schedule that time in and to get institutional funding.

Make use of social software for promoting and organizing the unconference (wikis are good), and also use it for continuing the conversation.

Free as in beer, free as in kittens, and now free as in someone else is paying. Make use of the resources of the participants institutions.

Swag keeps the connection, and if you’re creative, they’re also useful. SF showed the notebooks that they handed out at LibCampNYC, which were branded versions of something like Moleskine notebooks. Hand out the swag at the beginning, along with notes about how the unconference was going to work and an outline of a schedule (if you have one).

You can build communities through unconferences that then are agile enough to continue the interaction and spontaneous gatherings.

"If you feed them they will come. If you give them liquor they will come the next time." — John Blyberg