CIL 2010: looking ahead

I spent some time this morning planning my schedule for Computers in Libraries. It’s next week, so I figured it was time to start getting my head into conference/learning mode. Plus, I feel more relaxed when I’m prepared in advance.

I must say, after browsing through the entire schedule, there are fewer sessions I’m really jazzed about seeing this year than the first year I went. Don’t get me wrong — I still think it’s a good conference. But, having gone the past two years, I’m seeing some of the same sessions (and often the same speakers) show up again this year, and I’m having a hard time imagining that the content will be fresh enough for me to glean something new from them.

So, instead, I’m trying to branch out and attend sessions on other topics. This is good for me because I consider the ITI conferences to be like ALA only geekier — broad swaths of librarians from all sorts of libraries and departments, getting together to talk about tech in libraries. It gets me out of my cubby hole of electronic resources.

However, I’m not as into library instruction (for example) as I am gadgets and gizmos, so I think this CIL is going to be a different experience for me than the CIL I attended two years ago.

March reading

I started reading Getting Things Done by David Allen and ReWork by Jason Fried and David Heinemeier Hansson (co-founders of 37 Signals). I’m enjoying both and am forcing myself to carve out time for them, but I still wasn’t able to finish them in the month. I did, however complete two books.

Alabama’s Civil Rights Trail: An Illustrated Guide to the Cradle of Freedom by Frye Gaillard, with a forward by Juan Williams, was not a book I would have chosen myself (it was sent to me for review), but turned out to be an interesting read. It’s in part a travel guide, but mostly is a history lesson about events related to the civil rights movement in Alabama, mainly in the 20th century.

Guyland: The Perilous World Where Boys Become Men by Michael S. Kimmel is the One Book, One Campus selection at MPOW this year. I refrained from reading further ahead than the chapters we were discussing, so I finished the book at the same time our lunchtime discussions ended. It’s an interesting perspective on “guy” culture and how much that dominates the rest of American/Western culture. I don’t agree with all of Kimmel’s arguments, but they gave me food for thought. I highly recommend this book to anyone in a university setting (male or female).

tweaking my workflow

Over the past year, I’ve become a Lifehacker fanatic. I read the site regularly, and sometimes I even use it as a reward for finishing some unpleasant task. While I don’t do every lifehack suggested or install every app suggested, I have been making incremental changes in the way I approach things. Here are a few:

  • Earlier this year, I used HabitForge to get into a routine of going to bed by 11pm and getting up at 6am, which I’ve mostly continued to do. I’ve not done so well at the other routine of eating breakfast at home, but that is partially due to not being dilligent about having breakfast items on hand (i.e. I’ve been out of milk for almost a week now and I still haven’t remembered to pick up some when I had the chance).
  • Numerous ideas of how to process/manage email and tasks have led to my current system that is a hybrid of flags and search filters in Outlook, and the daily planning that defines my dayjob workflow.
  • I have a growing collection of DIY gift ideas for next Christmas, should my family decide to go the “make it yourself” gift route again. I’ll be better prepared this time.

I’m certain there are more things I could point out, but all I can remember right now are the relatively new ones. Everything else has either fallen away or has become so integrated that I don’t remember why or when I started doing it.

One more thing: I’m regularly inspired to clean my physical desktop when I see yet another need and cleverly organized featured workspace.

February reading

That’s right. Reading. Not plural. I finished only one book last month, at it was just the last few chapters I didn’t finish in January. I have a good excuse, though: my limited spare time last month was consumed with packing and moving and unpacking.

The book I finished was for the semi-annual book discussion group at work. We selected Nicholson Carr’s The Big Switch last fall, but weren’t able to meet to talk about it until early January. Here are my final thoughts on the book:

I found the parallels between the evolution of the delivery of electricity from self-contained generator systems to the modern-day grid and the evolution of personal computing applications from desktop to the cloud to be fascinating, and a good argument for cloud computing. However, once making that argument, the author proceeds to show his true colors as an anti-technology, privacy-focused, Matrix-fearing Luddite. Disappointing.

snapshot of a week

My boss asked us to track the time we spent on various tasks and projects to get an idea of areas where we could use student help or better coordination within the department. Here’s a visual representation of a (mostly) typical week:sampleweek
A typical day is full of things involving the management of electronic resources that aren’t routine, but come up regularly. For the things that aren’t a part of a defined project or task group, I tossed them into the “putting out fires” category, which may be why it’s the largest.

I should note that the meeting slice included time spent preparing for meetings as well as time spent in them. I am striving to reduce time spent in or preparing for meetings, particularly since they are often not as productive as the time spent on doing my job. Unfortunately, some of that is out of my control due to being a member of several standing committees with regular meetings.

[I meant to publish this back on February 11th when I wrote it, but somehow it ended up saved as a draft instead.]

January readings

I always do better at the beginning of the year than later on, so I’m not going to crow too much about being on track for reading 50 this year, particularly since two are graphic novels that took less than 20 minutes to read. Nevertheless, here’s the round-up:

The first and last books I read this month are The Ghost Brigades and The Last Colony by John Scalzi. Continuing on in the Old Man’s War universe, the first is from the perspective (mostly) of Jane Sagan, although not in the first person like OMW. The second is once again from first person perspective of John Perry. While TLC explains more of the politics of the OMW universe, I found TGB to be more interesting reading due to the issues of sentience and self-hood that Scalzi explores in the story. The fourth book, Zoe’s Tale, is on my reading list for this month.

Star Trek: Art of the Film is one that I read and reviewed for Blogcritics. It’s “is part coffee table book and part behind-the-scenes glimpse at the creation of the film.” Most of what I have to say about it, I said in the review, so check that out if you’re interested.

I started reading the new Wonder Woman comic series last year, and I found that I’m missing the context of an incredible amount of backstory, so I picked up copies of the first two trade paperbacks, Who Is Wonder Woman? and Love and Murder. It’s still a bit confusing, since even though they are the start of a new series, there is still an underlying assumption that the reader is familiar with the history of Wonder Woman. Me, I just vaguely remember the TV show. Anyway, I think I’ll continue getting the trade paperbacks instead of the single issues. It’s more cost-effective, and I need the longer story arcs to keep track of what’s happening.

ER&L 2010: Where are we headed? Tools & Technologies for the future

Speakers: Ross Singer & Andrew Nagy

Software as a service saves the institution time and money because the infrastructure is hosted and maintained by someone else. Computing has gone from centralized, mainframe processing to an even mix of personal computers on an networked enterprise to once again a very centralized environment with cloud applications and thin clients.

Library resource discovery is, to a certain extent, already in the cloud. We use online databases and open web search, WorldCat, and next gen catalog interfaces. The next gen catalog places the focus on the institution’s resources, but it’s not the complete solution. (People see a search box and they want to run queries on it – doesn’t matter where it is or what it is.) The next gen catalog is only providing access to local resources, and while it looks like modern interfaces, the back end is still old-school library indexing that doesn’t work well with keyword searching.

Web-scale discovery is a one-stop shop that provides increased access, enhances research, and provides and increase ROI for the library. Our users don’t use Google because it’s Google, they use it because it’s simple, easy, and fast.

How do we make our data relevant when administration doesn’t think what we do is as important anymore? Linked data might be one solution. Unfortunately, we don’t do that very well. We are really good at identifying things but bad at linking them.

If every component of a record is given identifiers, it’s possible to generate all sorts of combinations and displays and search results via linking the identifiers together. RDF provides a framework for this.

Also, once we start using common identifiers, then we can pull in data from other sources to increase the richness of our metadata. Mashups FTW!

ER&L 2010: E-book Management – It Sounds Serial!

Speakers: Dani L. Roach & Carolyn DeLuca

How do you define an ebook? How is it different from a print book? From another online resource? Is it like pornography – you know it when you see it? “An electronic equivalent of a distinct print title.” What about regularly updated ebooks? For the purposes of this presentation, an ebook is defined by its content, format, delivery, and fund designation.

Purchase impacts delivery and delivery impacts purchase – we need to know the platform, the publisher, the simultaneous user level, bundle options, pricing options (more than cost – includes release dates, platforms, and licensing), funding options, content, and vendor options (dealing more one-on-one with publishers). We now have multiple purchasing pots and need to budget annually for ebooks – sounds like a serial. Purchasing decisions impact collection development, including selection decisions, duplicate copies, weeding, preferences/impressions, and virtual content that requires new methods of tracking.

After you purchase an ebook bundle, then you have to figure out what you actually have. The publisher doesn’t always know, and the license doesn’t always reflect reality, and your ERMS/link resolve may not have the right information, either. Also, the publisher doesn’t always remove the older editions promptly, so you have to ask them to “weed.”

Do you use vendor-supplied MARC records or purchase OCLC record sets? Do you get vendor-neutral records, or multiple records for each source (and you will have duplicates).

Who does what? Is your binding person managing the archival process? Is circulation downloading the ebooks to readers? Is your acquisitions person ordering ebooks, or does your license manger now need to do that? How many times to library staff touch a printed book after it is cataloged and shelved? How about ebooks?

Users are already used to jumping from platform to platform – don’t let that excuse get in the way of purchasing decisions.

Ebooks that are static monographs that are one-time purchases are pretty much like print books. When ebooks become hybrids that incorporate aspects of ejournals and subscription databases, it gets complicated.

Why would a library buy an ebook rather than purchase it in a consortia setting? With print books, you can share them, so shouldn’t we want to that with ebooks? Yes, but ebooks are relatively so new that we haven’t quite figured out how to do this effectively, and consorital purchases are often too slow for title-by-title purchases.

ER&L 2010: Developing a methodology for evaluating the cost-effectiveness of journal packages

Speaker: Nisa Bakkalbasi

Journal packages offer capped price increases, access to non-subscribed content, and it’s easier to manage than title-by-title subscriptions. But, the economic downturn has resulted in even the price caps not being enough to sustain the packages.

Her library only seriously considers COUNTER reports, which is handy, since most package publishers provide them. They add to that the publisher’s title-by-title list price, as well as some subject categories and fund codes. Their analysis includes quantitative and qualitative variables using pivot tables.

In addition, they look at the pricing/sales model for the package: base value, subscribed/non-subscribed titles, cancellation allowance, price cap/increase, deep discount for print rate, perpetual/post-cancellation access rights, duration of the contract, transfer titles, and third-party titles.

So, the essential question is, are we paying more for the package than for specific titles (perhaps fewer than we currently have) if we dissolved the journal package?

She takes the usage reports for at least the past three years in order to look at trends, and excludes titles that are based on separate pricing models, and also excluded backfile usage if that was a separate purchase (COUNTER JR1a subtracted from JR1 – and you will need to know what years the publisher is calling the backfile). Then she adds list prices for all titles (subscribed & non-subscribed). Then, she calculates the cost-per-use of the titles, and uses the ILL cost (per the ILL department) as a threshold for possible renewals or cancellations.

The final decision depends on the base value paid by the library, the collection budget increase/decrease, price cap, and the quality/consistency of ILL service (money is not everything). This method is only about the costs, and it does not address the value of the resources to the users beyond what they may have looked at. There may be other factors that contributed to non-use.

ER&L 2010: Comparison Complexities – the challenges of automating cost-per-use data management

Speakers: Jesse Koennecke & Bill Kara

We have the use reports, but it’s harder to pull in the acquisitions information because of the systems it lives in and the different subscription/purchase models. Cornell had a cut in staffing and an immediate need to assess their resources, so they began to triage statistics cost/use requests. They are not doing systematic or comprehensive reviews of all usage and cost per use.

In the past, they have tried doing manual preparation of reports (merging files, adding data), but that’s time-consuming. They’ve had to set up processes to consistently record data from year to year. Some vendor solutions have been partially successful, and they are looking to emerging options as well. Non-publisher data such as link resolver use data and proxy logs might be sufficient for some resources, or for adding a layer to the COUNTER information to possibly explain some use. All of this has required certain skill sets (databases, spreadsheets, etc.)

Currently, they are working on managing expectations. They need to define the product that their users (selectors, administrators) can expect on a regular basis, what they can handle on request, and what might need a cost/benefit decision. In order to get accurate time estimates for the work, they looked at 17 of their larger publisher-based accounts (not aggregated collections) to get an idea of patterns and unique issues. As an unfortunate side effect, every time they look at something, they get an idea of even more projects they will need to do.

The matrix they use includes: paid titles v. total titles, differences among publishers/accounts, license period, cancellations/swaps allowed, frontfile/backfile, payment data location (package, title, membership), and use data location and standard. Some of the challenges with usage data include non-COUNTER compliance or no data at all, multiple platforms for the same title, combined subscriptions and/or title changes, titles transferred between publishers, and subscribed content v. purchased content. Cost data depends on the nature of the account and the nature of the package.

For packages, you can divide the single line item by the total use, but that doesn’t help the selectors assess the individual subset of titles relevant to their areas/budgets. This gets more complicated when you have packages and individual titles from a single publisher.

Future possibilities: better automated matching of cost and use data, with some useful data elements such as multiple cost or price points, and formulas for various subscription models. They would also like to consolidate accounts within a single publisher to reduce confusion. Also, they need more documentation so that it’s not just in the minds of long-term staff.