CIL 2010: Library Engagement Through Open Data

Speakers: Oleg Kreymer & Dan Lipcan

Library data is meaningless in and of itself – you need to interpret it to give it meaning. Piotr Adamczyk did much of the work for the presentation, but was not able to attend today due to a schedule conflict.

They created the visual dashboard for many reasons, including a desire to expose the large quantities of data they have collected and stored, but in a way that is interesting and explanatory. It’s also a handy PR tool for promoting the library to benefactors, and to administrators who are often not aware of the details of where and how the library is being effective and the trends in the library. Finally, the data can be targeted to the general public in ways that catch their attention.

The dashboard should also address assessment goals within the library. Data visualization allows us to identify and act upon anomalies. Some visualizations are complex, and you should be sensitive to how you present it.

The ILS is a great source of circulation/collections data. Other statistics can come from the data collected by various library departments, often in spreadsheet format. Google Analytics can capture search terms in catalog searches as well as site traffic data. Download/search statistics from eresources vendors can be massaged and turned into data visualizations.

The free tools they used included IMA Dashboard (local software, Drupal Profile) and IBM Many Eyes and Google Charts (cloud software). The IMA Dashboard takes snapshots of data and publishes it. It’s more of a PR tool.

Many Eyes is a hosted collection of data sets with visualization options. One thing I like was that they used Google Analytics to gather the search terms used on the website and presented that as a word cloud. You could probably do the same with the titles of the pages in a page hit report.

Google Chart Tools are visualizations created by Google and others, and uses Google Spreadsheets to store and retrieve the data. The motion charts are great for showing data moving over time.

Lessons learned… Get administrative support. Identify your target audience(s). Identify the stories you want to tell. Be prepared for spending a lot of time manipulating the data (make sure it’s worth the time). Use a shared repository for the data documents. Pull from data your colleagues are already harvesting. Try, try, and try again.

CIL 2010: The Power in Your Browser – LibX & Zotero

Speaker: Krista Godfrey

She isn’t going to show how to create LibX or Zotero access, but rather how to use them to create life-long learners. Rather than teaching students how to use proprietary tools like Refworks, teaching them tools they can use after graduation will help support their continued research needs.

LibX works in IE and Firefox. They are working on a Chrome version as well. It fits into the search and discovery modules in the research cycle. The toolbar connects to the library catalog and other tools, and right-click menu search options are available on any webpage.  It will also embed icons in places like Amazon that will link to catalog searches, and any page with a document identifier (DOI, ISSN) will now present that identifier as a link to the catalog search.

Zotero is only in Firefox, unfortunately. It’s a records management tool that allows you to collect, manage, cite, and share, which fill in the rest of the modules in the research cycle. It will collect anything, archive anything, and store any attached documents. You can add notes, tags, and enhance the metadata. The citation process works in Word, Open Office, and Google Docs, with a program similar to Write-N-Cite that can be done by dragging and dropping the citation where you want it to go.

One of the down-sides to Zotero when it first came out was that it lived only in one browser on one machine, but the new version comes with server space that you can sync your data to, which allows you to access your data on other browsers/machines. You can create groups and share documents within them, which would be great for a class project.

Why aren’t we teaching Zotero/LibX more? Well, partially because we’ve spent money on other stuff, and we tend to push those more. Also, we might be worried that if we give our users tools to access our content without going through our doors, they may never come back. But, it’s about creating life-long learners, and they won’t be coming through our doors when they graduate. So, we need to teach them tools like these.

CIL 2010: Conversations with the Archivist of the United States

Speakers: “Collector in Chief” David Ferriero interviewed by Paul Holdengräber

Many people don’t know what the archivist does. They often think that the National Archives are a part of the Library of Congress. In fact, the agency is separate.

Ferriero is the highest ranking librarian in the administration. It’s usually a historian or someone with connections to the administration. He was surprised to get the appointment, and had been expecting to head the IMLS instead.

He is working to create a community around the records and how they are being used. His blog talks about creating citizen archivists. In addition, he is working to declassify 100 million documents a year. There is an enormous backlog of these documents going back to WWII. Each record must be reviewed by the agency who initially classified them, and there are 2400 classification guides that are supposed to be reviewed every five years, but around 50% of them have not.

You can’t have an open government if you don’t have good records. When records are created, they need to be ready to migrate formats as needed. There will be a meeting between the chief information officers and the record managers to talk about how to tackle this problem. These two groups have historically not communicated very well.

He’s also working to open up the archives to groups that we don’t often think of being archive users. There will be programs for grade school groups, and more than just tours.

Large digitization projects with commercial entities lock up content for periods of time, including national archives. He recognizes the value that commercial entities bring to the content, but he’s concerned about the access limitations. This may be a factor in what is decided when the contract with Ancestry.com is up.

“It’s nice having a boss down the street, but not, you know, in my face.” (on having not yet met President Obama)

Ferriero thinks we need to save smarter and preserve more digital content.

CIL 2010: Google Wave

Presenters: Rebecca Jones & Bob Keith

Jones was excited to have something that combined chat with cloud applications like Google Docs. Wave is a beginning, but still needs work. Google is not risk-averse, so they put it out and let us bang on it to shape it into something useful.

More people joined Google Wave and abandoned it than those who stuck with it (less than 10% of the room). We needed something that would push us over to incorporating it into our workflows, and we didn’t see that happen.

The presenters created a public wave, which you can find by searching “with:public tag:cil2010”. Ironically, they had to close Wave in order to have enough virtual memory to play the video about Wave.

Imagine that! Google Wave works better in Google Chrome than in other browsers (including Firefox with the Gears extension).

Gadgets add functionality to waves. [note: I’ve also seen waves that get bogged down with too many gadgets, so use them sparingly.] There are also robots that can do tasks, but it seems to be more like text-based games, which have some retro-chic, but no real workflow application.

Wave is good for managing a group to-do list or worklog, planning events, taking and sharing meeting notes, and managing projects. However, all participants need to be Wave users. And, it’s next to impossible to print or otherwise archive a Wave.

The thing to keep in mind with Wave is that it’s not a finished product and probably shouldn’t be out for public consumption yet.

The presentation (available at the CIL website and on the wave) also includes links to a pile of resources for Wave.

CIL 2010: Black Ops Ninja-style Tech Projects

Speakers: Amanda Etches-Johnson, John Blyberg, & Sarah Houghton-Jan

One of the frustrations people have is that there are all sorts of exciting projects you could do, but often they are blocked by things that may be confusing to you. If you’re persistent, you can find ways to get around them.

We need to change the hearts & minds of the stakeholders in order to effectively implement something new. "Because we’ve always done it that way" might be a frustration and source of some amusement, but the reality is that we all have some attachment to established routines and processes. Make sure whatever you implement fits within your institutional strategic plan.

Often you can make changes without anyone noticing, and when they do, it’s already established. Start planning in advance – if you know you want to implement something, get people familiar with the idea or tech before introducing it as something to implement locally. When it’s no longer a foreign or new thing, then they will be more likely to go along with it.

You need to provide a counter-vision for people to latch onto. You need to have a vision that you know will be successful and that people will get behind you on it.

Evidenced-based librarianship requires due diligence. Do a literature search. Ask your colleagues about their experiences. If there is no evidence to support it, do it anyway. Make sure to collect the evidence as you go to share with others.

Try not to step on any toes as you are moving forward on your project (avoid collateral damages). Talk to everyone – you need to know where your project will impact other people, and you don’t know what you don’t know. YOU DO NOT HAVE TO HAVE A MEETING. You can do this virtually.

What if the thing you want to do isn’t right? Give it a try and fully commit to success, and if it fails, that’s okay. You learn more from failure than from success. Figure out what went wrong and why. Don’t be discouraged.

Timing is everything. It may be too soon, so hang on for a bit and deploy when it’s most effective. No right now doesn’t necessarily no six months from now. Don’t get discouraged with nos.

Project teams can be a force for good. The team needs to buy into the process, and having specific goals/tasks can help.

When do you get buy-in from stakeholders versus just going forward with it? Use your best judgment. You often know when you will get unreasonable resistance, so sometimes it’s okay to ask for forgiveness rather than permission, but be ready if it backfires.

Trust yourself. You know what you’re doing.

Know when to quit. Evaluate your situation, and if the returns are diminishing, then it’s time to move on to something else, even if you’ve invested a lot into it already.

Make sure you take care of the infrastructure first. You will have trouble getting stakeholder support for your project if the day-to-day stuff is falling apart. Unless your project is designed to fix infrastructure problems.

Keep some cards hidden. Let people feel like they’ve made suggestions for something (that you’ve already planned to implement) or put off implementing some features unless you or your team have time to do them.

[Sarah recommends drinking heavily, also.]

Update: Sarah has posted a list of the tips, if you would like to consume them unfiltered.

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.

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

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.