LITA 2008: What is “Social Cataloging” and Why Should You Care?

“Having games in the library strikes me as being like having bocce in the frat house.”

Speaker: Tim Spalding, Founder of LibraryThing

“I have no practical advice for you, but I have inspiration and screen shots.” Such as, images from Dr. Horrible’s Sing-Along Blog and book pile photo submissions.

Social cataloging does not need to be defined. LibraryThing is a good example of social cataloging, but it’s not the only resource out there like that. (LibraryThing is now larger than the Library of Congress.) Good Reads focuses more on the social aspects, and Shelfari is being revived by Amazon. There are other sites like CiteULike and Last.fm that do social cataloging of things other than books.

Social cataloging explores the socialization. LibraryThing embraces the social and the digital because there is no physical aspect (except for what you have in your own collection).

Social cataloging ladder:

  • personal cataloging – your stuff
  • exhibitionism, voyeurism – about you and your stuff
  • self expression – book pile photos, reviews
  • implicit social cataloging – tag clouds on books that incorporate data from all owners, recommendations, connect with other owners of more obscure books
  • social networking – “friends” lists, users who share your books, groups
  • sharing – book covers of different editions, author photos
  • explicit social cataloging – work-level records (any title you would agree on at a cocktail party) for both books and authors, series data
  • collaborative cataloging – building the catalogs of famous dead people, developing an open-source alternative to Dewey

Regarding why Spalding felt it necessary to pull data from libraries and not just Amazon, he says, “Once you are over the age of 30 and you are not a Philistine, you have books that Amazon is not currently selling.”

Interesting factoid about how things are tagged on LibraryThing: LGBT and GLBT tags have two completely different lists of books.

Traditional cataloging is based on the physical form of cataloging with cards. It was too difficult to change subjects or to add weight to particular subjects because you couldn’t do that with physical cards. We need to get away from this now that we have all the flexibility of digital cataloging. Digital cataloging is social cataloging.

LibraryThing users are doing about 1,000 work combinations per day! Voluntarily! Experts on book topics are the ones pulling the data together, not experts on cataloging.

LibraryThing members figured out what books are on Dr. Horrible’s shelf based on a fuzzy still from the video. And then the guy who lives in the apartment where it was filmed corrected the editions listed.

There are many non-librarians who are passionate about books and classification. People care about libraries and library data.

On the other hand, we suck. Our catalogs are fundamentally not open to the web because our pages are often session-specific and not friendly to index spiders. Worldcat.org is getting fewer visitors, whereas Dogster.com is getting more.

Library 2.0 is in danger. Libraries are concentrating on what they can do, not what they can do best. We don’t need to have blogs or pages on Facebook. “Having games in the library strikes me as being like having bocce in the frat house.”

Do not pay anyone for Library 2.0 stuff. Do it yourself. OCLC is not yourself.

Or, pay Spalding for his 2.0 enhancements (LibraryThing for Libraries).

Social cataloging is about the catalog, about what you can do right now, about passion, and about giving (not taking).

thing 15: library/web 2.0

Librarians should be on the forefront of providing information services to users, but for some reason, we have a sizable contingent who seem to think that the innovations of the 70s and 80s are good enough for now. They’re the ones most often reacting negatively to anyone who mentions anything Library 2.0.

Anytime someone mentions some new web tool or gadget, and you think or say, “We don’t need that in our library!” or “What would you want to use that for?” stop for a moment. Do you use a computer in your daily library work? Do you use email to communicate with your colleagues and users? Have you talked to someone on the phone recently? These are all technologies that at some point in time, someone(s) didn’t think were needed in a library. They were wrong.

Maybe you don’t need to be on Twitter or Facebook to reach your users. (In fact, there have been many informal studies that indicate that students don’t want us in their social spaces.) But, you can use online social networking tools to expand your professional network, learn about what your colleagues are doing to improve services in their libraries, and share the things you are doing in your own library. Surely those are things that benefit the profession?

These things that people talk about as Web 2.0 are simply tools. You can choose how and when you will use them.

Library 2.0 has been used to describe a mindset that is open to exploring these tools and using them to enhance library services, but I think that has been a part of our profession for a long time. Library 2.0 was there when we began moving from card catalogs to online public access terminals. Library 2.0 was there when we opened up the stacks and allowed users to browse the shelves. Library 2.0 was there when we created free, circulating libraries that allowed anyone to access the knowledge they contained.

The philosophy of Library 2.0 isn’t anything new, we’re just using different words to describe what we already do best — exploring innovative ways to connect users with the information they are seeking.

NASIG 2008: Using Institutional and Library Identifiers to Ensure Access to Electronic Resources

Presenters: Helen Henderson, Don Hamparian, and John Shaw

One of the perpetual problems with online access to journals is that often, something breaks down on the supply chain, and the library discovers that access has disappeared. The presenters seek to offer ideas for preventing this from happening.

Henderson showed a list of 15 transactions that take place in acquiring and maintaining a subscription to a single title. There are plenty of places for a breakdown. Name changes, agent changes, publisher changes, hosting platform changes, price changes, bundle changes, licensing changes, authentication changes, etc.

OCLC’s WorldCat Registry maintains institutional information for libraries, which is populated and augmented by libraries and partners. Libraries can use it to register their OpenURL resolvers, IP addresses, and to share the profile with selected organizations. OCLC uses it to configure WorldCat Local, among other things. Vendors use it as an OpenURL gateway service and to verify customer data.

Ringgold’s Identify database and services normalizes institutional information for publishers. It includes consortia membership information and the Anglicized name, as well as many of the data elements in OCLC’s registry. Rather than OCLC symbol, they have an identifying number for each institution.

Potential interactions between the two identifiers includes a maping between them. The two directories do not have as much overlapping information as you might think.

Standards and identifiers are becoming even more important to the supply chain with the transition to electronic publication. Publishers need clean records in order to provide holdings lists to libraries and OpenURL resolvers, among other things. Publishers use services like WorldCat Registry and Identify to improve their data, service, and cost-savings that gets passed on to subscribers.

ICEDIS is a standard for the exchange of data between publishers and agents. It is old and has been implemented differently. They are hoping to develop an XML version by 2010, which will include the institutional identifier. ONIX is working on developing automatic holdings reports that will be fed into ERMS.

Project TRANSFER will create a way to exchange subscription information using a unique identifier. KBART is another initiative looking at a portion of the solution. I² (part of NISO) is looking at standardizing metadata using identifiers, beyond just for library resources. CORE is a project in the vendor community working on communicating between the ILS and the ERMS.

Standards will help ease the pain of price agreement between publishers and agents, customer identification, consortia membership and entitlements, and many of the other things that cause the supply chain to break down.

Libraries should include their identifier numbers in orders. The subscription agents are too overwhelmed to implement the kind of change that would require them to look up and add this to every record. Ringgold & OCLC are in communication with NISO to create a standard that is not proprietary.

NASIG 2008: Managing Divergence of Print and Online Journals

Presenters: Beth Weston and Deena Acton

The National Library of Medicine spent 2007 examined the impact of content differences between print and online journals on library operations and services. They then followed up on this in 2008. In evaluating the situation, the NLM team working on this project were tasked with locating the differences between print and online, noting them, and then determining their impact.

One thing that is worth noting here is that the NLM is an archival library, by which I mean they consider it a part of their mission to retain copies of everything they collect. And, their ILL service to other libraries is considered an essential function.

Because NLM is responsible for indexing content for MEDLINE, they were able to locate the differences through the indexing workflow. They have noticed that there is anecdotal evidence of an increase in online-only content. Aside from the indexing, which will be decreasing over time, differences between print and online are discovered by patrons and reference librarians, as well as interlibrary loan staff.

The working group recommends that publishers take responsibility for identifying the version of record, and develop and implement a standard for communicating that version to subscribers. However, that’s only a start. Libraries will then need to determine how they will note that in their records, as well as workflows for following up on it.

The set that the working group looked at included 149 titles from 58 publishers, in both print and online formats, but which had additional online-only content. Data was collected for a specific set of these journals on: number of complete articles in each edition, editorials, commentary/letters, book/media reviews, advertisements, announcements/calendar items, and continuing education materials. Notifications about new issues, author correspondence information, and other extraneous content that is format-specific was not considered.

Approximately 13% of the articles were online-only, and 18% of the articles contained article-level online-only supplementary materials. Based on the one year sampling, they estimate that 12,739 articles from these 149 titles could be online-only.

One reason why there may be an increase in the divergence is due to the volume of content publishers want to provide versus the cost of printing all of it. It is likely that as the cost of publishing ejournals decreases in relation to the cost of print publishing, we will see more of this divergence.

[Side note: I really wish we would move away from the “presenting the data from my study” sessions to “here’s how I applied the data from my study” sessions.]

NASIG 2008: When Did eBooks Become Serials?

Presenters: Kim Armstrong, Bob Nardini, Peter McCracken, and Rick Lugg

Because this is a serials conference, Lugg provided us with a title change and enumeration to differentiate this presentation from the repeat in the afternoon. Serialists (& librarians in general) love corny inside jokes.

eBook users want to use the work; to browse, to search, and to have the institution subscribe to it for them. Much of this is due to the success and model of ejournals.

eJournals have brought about many changes in information provision. More content is now available to users, and they are increasingly using it more. However, archive and access issues have not been fully addressed, nor have possible solutions thoroughly tested. In addition, ejournals (and other subscription items) have taken over more and more of the materials budget, which has necessitated greater selection. And, in many ways, ejournals are more labor-intensive than print.

Subscription has become one of the most successful models for ebook providers. There are some emerging models in addition to subscription or purchase. EBL, for example, offers short-term rental options.

There are many more titles and decisions involved in purchasing ebooks as opposed to journals. The content isn’t as well advertised through abstracting and indexing sources, since it’s one large thing rather than millions of little things aggregated together under one title.

Acquisition of ebooks provides its own unique challenges, ranging from the variety of sources to the mechanisms of selection. Is the content static or dynamic? One-time purchases or ongoing commitments? What libraries say verses what they do — we say we can’t buy more subscriptions, yet we continue to do so.


Library/Consortial View

Librarians have been trying to figure out what to do with ebooks, whether to purchase them, and how we should go about doing so for at least ten years.

The Committee on Institutional Cooperation coordinated a deal with Springer and MyiLibrary to purchase Springer’s entire ebook collection from 2005-2010. Access went live in January 2008, and over the first five months of 2008, ebook use on the Springer platform was nearly half that of the ejournal use, even without catalog records or promoting it. On the other hand, the MyiLibrary use was a quarter or less, partially due to MyiLibrary’s lack of OpenURL support.

We need to make sure that we stay relevant to our users needs and not become just a place to store their archival literature.


eBookseller View

Back in the day, the hot topic in the monographic world was approval plans. Eventually they figured that out, and book acquisition became routine. Now we have serials-like problems for both booksellers and book buyers.

Approval plans had a seriality to them, but we haven’t come up with something similar for ebooks. Billing and inventory systems for booksellers are set up for individual book sales, not subscriptions.

The vendor/aggregator is challenged with incorporating content from a variety of publisher sources, each with their own unique quirks. Bibliographic control can take the route of treating ebooks like print books, but we’re in a time of change that may necessitate a different solution.

Maybe the panel should have been called, “When will ebooks and serials become one big database?”

eResource Access & Management View

The differences between ebooks and ejournals on the management side really isn’t all that different. The metadata, however, is exponentially larger when dealing with ebooks verses ejournals. The bibliographic standards (or those accepted) are higher for books than for journals.

How do we handle various editions? Do we go with the LibraryThing model of collecting all editions under one work record?

managing electronic resources

Longing for the perfect ERMS….

In 2003, I attended the ACRL conference in Charlotte. One of the sessions I sat in on was about home-grown electronic resource management tools. After having dealt with digital and manilla folders of stuff, constantly searching for info, and not having any sort of long-term archiving plan for getting at the information, the idea of having a system that did that for me seemed miraculous.

Fast-forward five years. I’ve now had the pleasure of working with two moderately functional commercial ERMS, and neither are the miracle solution I had hoped for.

Now that I’ve had the opportunity to get under the hood of “traditional” ERMS, I have an idea as to why they are flawed — they’re approaching electronic resource management as a metadata storage problem, rather than a workflow problem. Creating a system that includes all the fields recommended by the DLF ERM Initiative is a good start, but it’s only a start. We need something that goes beyond that to creating a workflow that can include input and required actions from various different people similar to the workflow outlined in the DLF document.

My ideal ERMS is one that make it easy to input licensing and acquisitions data, automatically triggers alerts for follow-up, and provides relevant license information to users and staff. I’m currently managing more electronic resources than ever. I need a tool that makes keeping track of them as simple and painless as possible. Unfortunately, I don’t think the commercially available products are at that point yet, and as far as I know, no one is working on an open source solution.

CiL 2008: Catalog Effectiveness

Speaker: Rebekah Kilzer

The Ohio State University Libraries have used Google Analytics for assessing the use of the OPAC. It’s free for sites up to five million page views per month — OSU has 1-2 million page views per month. Libraries would want to use this because most integrated library systems offer little in the way of use statistics, and what they do have isn’t very… useful. You will need to add some code that will display on all OPAC pages.

Getting details about how users interact with your catalog can help with making decisions about enhancements. For example, knowing how many dial-up users interact with the site could determine whether or not you want to develop style sheets specifically for them, for example. You can also track what links are being followed, which can contribute to discussions on link real estate.

There are several libraries that are mashing up Google Analytics information with other Google tools.


Speakers: Cathy Weng and Jia Mi

The OPAC is a data-centered, card-catalog retrieval system that is good for finding known items, but not so good as an information discovery tool. It’s designed for librarians, not users. Librarian’s perceptions of users (forgetful, impatient) prevents librarians from recognizing changes in user behavior and ineffective OPAC design.

In order to see how current academic libraries represent and use OPAC systems, they studied 123 ARL libraries’ public interfaces and search capabilities as well as their bibliographic displays. In the search options, two-thirds of libraries use “keyword” as the default and the other third use “title.” The study also looked at whether or not the keyword search was a true keyword search with an automatic “and” or if the search was treated as a phrase. Few libraries used relevancy ranking as the default search results sorting.

There are some great disparities in OPAC quality. Search terms and search boxes are not retained on the results page, post-search limit functions are not always readily available, item status are not available on search results page, and the search keywords are not highlighted. These are things that the most popular non-library search engines do, which is what our users expect the library OPAC to do.

Display labels are MARC mapping, not intuitive. Some labels are suitable for certain types of materials but not all (proper name labels for items that are “authored” by conferences). They are potentially confusing (LCSH & MeSH) and occasionally inaccurate. The study found that there were varying levels of effort put to making the labels more user-friendly and not full of library jargon.

In addition to label displays, OPACs also suffer from the way the records are displayed. The order of bibliographic elements effect how users find relevant information to determine whether or not the item found is what they need.

There are three factors that contribute to the problem of the OPAC: system limitations, libraries not exploiting full functionality of ILS, and MARC standards are not well suited to online bibliographic display. We want a system that doesn’t need to be taught, that trusts users as co-developers, and we want to maximize and creatively utilize the system’s functionality.

The presentation gave great examples of why the OPAC sucks, but few concrete examples of solutions beyond the lipstick-on-a-pig catalog overlay products. I would have liked to have a list of suggestions for label names, record display, etc., since we were given examples of what doesn’t work or is confusing.

CiL 2008: Woepac to Wowpac

Moderator: Karen G. Schneider – “You’re going to go un-suck your OPACs, right?”


Speaker: Roy Tennant

Tennant spent the last ten years trying to kill off the term OPAC.

The ILS is your back end system, which is different from the discovery system (doesn’t replace the ILS). Both of these systems can be locally configured or hosted elsewhere. Worldcat Local is a particular kind of discovery system that Tenant will talk about if he has time.

Traditionally, users would search the ILS to locate items, but now the discovery system will search the ILS and other sources and present it to the user in a less “card catalog” way. Things to consider: Do you want to replace your ILS or just your public interface? Can you consider open source options (Koha, Evergreen, vuFind, LibraryFind etc.)? Do you have the technical expertise to set it up and maintain it? Are you willing to regularly harvest data from your catalog to power a separate user interface?


Speaker: Kate Sheehan

Speaking from her experience of being at the first library to implement LibraryThing for Libraries.

The OPAC sucks, so we look for something else, like LibraryThing. The users of LibraryThing want to be catalogers, which Sheehan finds amusing (and so did the audience) because so few librarians want to be catalogers. “It’s a bunch of really excited curators.”

LibraryThing for libraries takes the information available in LibraryThing (images, tags, etc.) and drops them into the OPAC (platform independent). The display includes other editions of books owned by the library, recommendations based on what people actually read, and a tag cloud. The tag cloud links to a tag browser that opens up on top of the catalog and allows users to explore other resources in the catalog based on natural language tags rather than just subject headings. Using a Greasmonkey script in your browser, you can also incorporate user reviews pulled from LibraryThing. Statistics show that the library is averaging around 30 tag clicks and 18 recommendations per day, which is pretty good for a library that size.

“Arson is fantastic. It keeps your libraries fresh.” — Sheehan joking about an unusual form of collection weeding (Danbury was burnt to the ground a few years ago)

Data doesn’t grow on trees. Getting a bunch of useful information dropped into the catalog saves staff time and energy. LibraryThing for Libraries didn’t ask for a lot from patrons, and it gave them a lot in return.


Speaker: Cindi Trainor

Are we there yet? No. We can buy products or use open source programs, but they still are not the solution.

Today’s websites are consist of content, community (interaction with other users), interactivity (single user customization), and interoperability (mashups). RSS feeds are the intersection of interactivity and content. There are a few websites that are in the sweet spot in the middle of all of these: Amazon (26/32)*, Flickr (26/32), Pandora (20/32), and Wikipedia (21/32) are a few examples.

Where are the next generation catalog enhancements? Each product has a varying degree of each element. Using a scoring system with 8 points for each of the four elements, these products were ranked: Encore (10/32), LibraryFind (12/32), Scriblio (14/32), and WorldCat Local (16/32). Trainor looked at whether the content lived in the system or elsewhere and the degree to which it pulled information from sources not in the catalog. Library products still have a long way to go – Voyager scored a 2/32.

*Trainor’s scoring system as described in paragraph three.


Speaker: John Blyberg

When we talk about OPACs, we tend to fetishize them. In theory, it’s not hard to create a Wowpac. The difficulty is in creating the system that lives behind it. We have lost touch with the ability to empower ourselves to fix the problems we have with integrated library systems and our online public access catalogs.

The OPAC is a reflection of the health of the system. The OPAC should be spilling out onto our website and beyond, mashing it up with other sites. The only way that can happen is with a rich API, which we don’t have.

The title of systems librarian is becoming redundant because we all have a responsibility and role in maintaining the health of library systems. In today’s information ecology, there is no destination — we’re online experiencing information everywhere.

There is no way to predict how the information ecology will change, so we need systems that will be flexible and can grow and change over time. (Sopac 2.0 will be released later this year for libraries who want to do something different with their OPACs.) Containers will fail. Containers are temporary. We cannot hang our hat on one specific format — we need systems that permit portability of data.

Nobody in libraries talks about “the enterprise” like they do in the corporate world. Design and development of the enterprise cannot be done by a committee, unless they are simply advisors.

The 21st century library remains un-designed – so let’s get going on it.