ER&L 2010: Adventures at the Article Level

Speaker: Jamene Brooks-Kieffer

Article level, for those familiar with link resolvers, means the best link type to give to users. The article is the object of pursuit, and the library and the user collaborate on identifying it, locating it, and acquiring it.

In 1980, the only good article-level identification was the Medline ID. Users would need to go through a qualified Medline search to track down relevant articles, and the library would need the article level identifier to make a fast request from another library. Today, the user can search Medline on their own; use the OpenURL linking to get to the full text, print, or ILL request; and obtain the article from the source or ILL. Unlike in 1980, the user no longer needs to find the journal first to get to the article. Also, the librarian’s role is more in providing relevant metadata maintenance to give the user the tools to locate the articles themselves.

In thirty years, the library has moved from being a partner with the user in pursuit of the article to being the magician behind the curtain. Our magic is made possible by the technology we know but that our users do not know.

Unique identifiers solve the problem of making sure that you are retrieving the correct article. CrossRef can link to specific instances of items, but not necessarily the one the user has access to. The link resolver will use that DOI to find other instances of the article available to users of the library. Easy user authentication at the point of need is the final key to implementing article-level services.

One of the library’s biggest roles is facilitating access. It’s not as simple as setting up a link resolver – it must be maintained or the system will break down. Also, document delivery service provides an opportunity to generate goodwill between libraries and users. The next step is supporting the users preferred interface, through tools like LibX, Papers, Google Scholar link resolver integration, and mobile devices. The latter is the most difficult because much of the content is coming from outside service providers and the institutional support for developing applications or web interfaces.

We also need to consider how we deliver the articles users need. We need to evolve our acquisitions process. We need to be ready for article-level usage data, so we need to stop thinking about it as a single-institutional data problem. Aggregated data will help spot trends. Perhaps we could look at the ebook pay-as-you-use model for article-level acquisitions as well?

PIRUS & PIRUS 2 are projects to develop COUNTER-compliant article usage data for all article-hosting entities (both traditional publishers and institutional repositories). Projects like MESUR will inform these kinds of ventures.

Libraries need to be working on recommendation services. Amazon and Netflix are not flukes. Demand, adopt, and promote recommendation tools like bX or LibraryThing for Libraries.

Users are going beyond locating and acquiring the article to storing, discussing, and synthesizing the information. The library could facilitate that. We need something that lets the user connect with others, store articles, and review recommendations that the system provides. We have the technology (magic) to make it available right now: data storage, cloud applications, targeted recommendations, social networks, and pay-per-download.

How do we get there? Cover the basics of identify>locate>acquire. Demand tools that offer services beyond that, or sponsor the creation of desired tools and services. We also need to stay informed of relevant standards and recommendations.

Publishers will need to be a part of this conversation as well, of course. They need to develop models that allow us to retain access to purchased articles. If we are buying on the article level, what incentive is there to have a journal in the first place?

For tenure and promotion purposes, we need to start looking more at the impact factor of the article, not so much the journal-level impact. PLOS provides individual article metrics.

ER&L 2010: Beyond Log-ons and Downloads – meaningful measures of e-resource use

Speaker: Rachel A. Flemming-May

What is “use”? Is it an event? Something that can be measured (with numbers)? Why does it matter?

We spend a lot of money on these resources, and use is frequently treated as an objective for evaluating the value of the resource. But, we don’t really understand what use is.

A primitive concept is something that can’t be boiled down to anything smaller – we just know what it is. Use is frequently treated like a primitive concept – we know it when we see it. To measure use we focus on inputs and outputs, but what do those really say about the nature/value of the library?

This gets more complicated with electronic resources that can be accessed remotely. Patrons often don’t understand that they are using library resources when they use them. “I don’t use the library anymore, I get most of what I need from JSTOR.” D’oh.

Funds are based on assessments and outcomes – how do we show that? The money we spend on electronic resources is not going to get any smaller. ROI is focused more on funded research, but not electronic resources as a whole.

Use is not a primitive concept. When we talk about use, it can be an abstract concept that covers all use of library resources (physical and virtual). Our research often doesn’t specify what we are measuring as use.

Use as a process is the total experience of using the library, from asking reference questions to finding a quiet place to work to accessing resources from home. It is the application of library resources/materials to complete a complex/multi-stage process. We can do observational studies of the physical space, but it’s hard to do them for virtual resources.

Most of our research tends to focus on use as a transaction – things that can be recorded and quantified, but are removed from the user. When we look only at the transaction data, we don’t know anything about why the user viewed/downloaded/searched the resource. Because they are easy to quantify, we over-rely on vendor-supplied usage statistics. We think that COUNTER assures some consistency in measures, but there are still many grey areas (i.e. database time-outs equal more sessions).

We need to shift from focusing on isolated instances of downloads and ref desk questions, but focus on the aggregate of the process from the user perspective. Stats are only one component of this. This is where public services and technical services need to work together to gain a better understanding of the whole. This will require administrative support.

John Law’s study of undergraduate use of resources is a good example of how we need to approach this. Flemming-May thinks that the findings from that study have generated more progress than previous studies that were focused on more specific aspects of use.

How do we do all of this without invading on the privacy of the user? Make sure that your studies are thought-out and pass approval from your institution’s review board.

Transactional data needs to be combined with other information to make it valuable. We can see that a resource is being used or not used, but we need to look deeper to see why and what that means.

As a profession, are we prepared to do the kind of analysis we need to do? Some places are using anthropologists for this. A few LIS programs are requiring a research methods course, but it’s only one class and many don’t get it. This is a great continuing education opportunity for LIS programs.

ER&L 2010: ERMS Success – Harvard’s experience implementing and using an ERM system

Speaker: Abigail Bordeaux

Harvard has over 70 libraries and they are very decentralized. This implementation is for the central office that provides the library systems services for all of the libraries. Ex Libris is their primary vendor for library systems, include the ERMS, Verde. They try to go with vended products and only develop in-house solutions if nothing else is available.

Success was defined as migrating data from old system to new, to improve workflows with improved efficiency, more transparency for users, and working around any problems they encountered. They did not expect to have an ideal system – there were bugs with both the system and their local data. There is no magic bullet. They identified the high-priority areas and worked towards their goals.

Phase I involved a lot of project planning with clearly defined goals/tasks and assessment of the results. The team included the primary users of the system, the project manager (Bordeaux), and a programmer. A key part of planning includes scoping the project (Bordeaux provided a handout of the questions they considered in this process). They had a very detailed project plan using Microsoft Project, and at the very least, the listing out of the details made the interdependencies more clear.

The next stage of the project involved data review and clean-up. Bordeaux thinks that data clean-up is essential for any ERM implementation or migration. They also had to think about the ways the old ERM was used and if that is desirable for the new system.

The local system they created was very close to the DLF recommended fields, but even so, they still had several failed attempts to map the fields between the two systems. As a result, they had a cycle of extracting a small set of records, loading them into Verde, reviewing the data, and then delete the test records out of Verde. They did this several times with small data sets (10 or so), and when they were comfortable with that, they increased the number of records.

They also did a lot of manual data entry. They were able to transfer a lot, but they couldn’t do everything. And some bits of data were not migrated because of the work involved compared to the value of it. In some cases, though, they did want to keep the data, so they entered it manually. Part of what they did to visualize the mapping process, they created screenshots with notes that showed the field connections.

Prior to this project, they were not using Aleph to manage acquisitions. So, they created order records for the resources they wanted to track. The acquisitions workflow had to be reorganized from the ground up. Oddly enough, by having everything paid out of one system, the individual libraries have much more flexibility in spending and reporting. However, it took some public relations work to get the libraries to see the benefits.

As a result of looking at the data in this project, they got a better idea of gaps and other projects regarding their resources.

Phase two began this past fall to begin incorporating the data from the libraries that did not participate in phase one. They now have a small group with folks representing the libraries. This group is coming up with best practices for license agreements and entering data into the fields.

ER&L 2010: Electronic Access and Research Efficiencies – Some Preliminary Findings from the U of TN Library’s ROI Analysis

Speaker: Gayle Baker, University of Tennessee – Knoxville

Phase one: Demonstrate the role of the library information in generating research grand incomes for the institution (i.e. the university spends X amount of money on the library which generates X amount of money in grant research and support).

To do this, they sent out emails to faculty with surveys that included incentives to respond (quantitative and qualitative questions). They gathered university-supplied data about grant proposals and income, and included library budget information. They also interviewed administrators to get a better picture of the priorities of the university.

UIUC’s model: Faculty with grant proposals using the library times the percentage of award success rate times the average grant income, then multiplied that by the grants expended and divided by the total library budget. The end result was that the model showed $4.38 grant income for every dollar invested in the library.

Phase two: Started by testing UIUC’s methodology across eight institutions in eight countries. Speaker didn’t elaborate, but went on to describe the survey they used and examples of survey responses. Interesting, but hard to convey relevance in this format, particularly since it’s so dependent on individual institutions. (On the up side, she has amusing anecdotes.) They used the ROI formula suggested by Carol Tenopir, which is slightly different than described above.

Phase three: IMLS grant for the next three years, headed by Tenopir and Paula Kaufman, and ARL and Syracuse will also be involved. They are trying to put a dollar value on things that are hard to do, such as student retention and success.

Ithaka’s What to Withdraw tool

Have you seen the tool that Ithaka developed to determine what print scholarly journals you could withdraw (discard/store) that are already in your digital collections? It’s pretty nifty for a spreadsheet. About 10-15 minutes of playing with it and a list of our print holdings resulted in giving me a list of around 200 or so actionable titles in our collection, which I passed on to our subject liaison librarians.

The guys who designed it are giving some webinar sessions, and I just attended one. Here are my notes, for what it’s worth. I suggest you participate in a webinar if you’re interested in it. The next one is tomorrow and there’s one on February 10th as well.


Background

  • They have an organizational commitment to preservation: JSTOR, Portico, and Ithaka S+R
  • Libraries are under pressure to both decrease their print collections and to maintain some print copies for the library community as a whole
  • Individual libraries are often unable to identify materials that are sufficiently well-preserved elsewhere
  • The What to Withdraw framework is for general collections of scholarly journals, not monographs, rare books, newspapers, etc.
  • The report/framework is not meant to replace the local decision-making process

What to Withdraw Framework

  • Why do we need to preserve the print materials once we have a digital version?
    • Fix errors in the digital versions
    • Replace poor quality scans or formats
    • Inadequate preservation of the digital content
    • Unreliable access to the digital content
    • Also, local politics or research needs might require access to or preservation of the print
  • Once they developed the rationales, they created specific preservation goals for each category of preservation and then determined the level of preservation needed for each goal.
    • Importance of images in journals (the digitization standards for text is not the same as for images, particularly color images)
    • Quality of the digitization process
    • Ongoing quality assurance processes to fix errors
    • Reliability of digital access (business model, terms & conditions)
    • Digital preservation
  • Commissioned Candace Yano (operations researcher at UC Berkeley) to develop a model for copies needed to meet preservation goals, with the annual loss rate of 0.1% for a dark archive.
    • As a result, they found they needed only two copies to have a >99% confidence than they will still have remaining copies left in twenty years.
    • As a community, this means we need to be retaining at least two copies, if not more.

Decision-Support Tool (proof of concept)

  • JSTOR is an easy first step because many libraries have this resource and many own print copies of the titles in the collections and Harvard & UC already have dim/dark archives of JSTOR titles
  • The tool provides libraries information to identify titles held by Harvard & UC libraries which also have relatively few images

Future Plans

  • Would like to apply the tool to other digital collections and dark/dim archives, and they are looking for partners in this
  • Would also like to incorporate information from other JSTOR repositories (such as Orbis-Cascade)

library day in the life – round 4

Hello. I’m the electronic resources librarian at the University of Richmond, a small private liberal arts university nestled on the edge of suburbia in a medium-sized mid-Atlantic city. Today I am participating in the Library Day in the Life Project for its fourth round. Enjoy!

8:30am Arrive, turn on computer, and go get a cup of coffee from the coffee shop attached to the library. By the time I return, the login screen is displayed, and thus begins the 5 minute long process of logging in and then opening Outlook, Firefox, and TweetDeck. Pidgin starts on its own, thankfully. Update location on FourSquare. (Gotta keep my mayorship!)

8:40am Check schedule on Outlook, note the day’s meeting times, and then check the tasks for the day. At this point, I see that it’s time for a DILO, so I start this entry.

8:50am Weed through the new emails that arrived over the weekend. Note that there is more spam than normal. In the middle of this, my boss cancels one of two meetings today. (w00t!)

9:15am Email processed and sorted into folders and labels. Time to dig into the day’s tasks and action items. Chatty coworkers in the cube farm prompt me to load Songbird and don headphones.

9:25am Send a reminder to the LIB 101 students registered for my seminar on Friday. Work out switching reference desk shifts because my Wednesday LIB 101 seminar conflicts with my regular Wednesday shift. Also send out a note requesting trades for next week’s shifts, since I’ll be away at ER&L.

9:40am Cleared all action items and to-do items, so now it’s time to dig into my current project — gathering 2009 use statistics.

10:30am Electronic resources workflow planning meeting for the next year with an eye towards the next five years.

11:00am Back to gathering use stats. I’ve been working on this for over two weeks, and I’m a little over half-way through. I’d be further along if I could dedicate all my time to it, but unfortunately, meetings, desk schedules, and other action items get in the way.

12:15pm Hunger overrides my obsessive hunt for stats. I brought my lunch with me today, but often I end up grabbing something on the go while I run errands.

1:10pm Process the email that has come in over the past two hours. Only two action items added (yay!) and both are responses to request for information from this morning (yay!), so I’m happy to see them.

1:15pm Back to the side-yet-related project that I started on shortly before lunch. We have a bunch of journals in the “Multiple Vendors :: Single Journals” category in our ERMS, and I’m moving them over to their specific publisher listings if I can, checking to see if we have use stats for them, and requesting admin info when we don’t. There are only about 55 titles, so I’m hoping to get most of this done before my reference desk shift at 3.

3:00pm I’m only half-way through the side-yet-related project, but I have to set it down and go to my reference desk shift now. Answering many technology questions from a retired woman who is attempting to take a class that requires her to use Blackboard and view PowerPoints and things that are highly confusing to her. Checking out netbooks to students and showing them how to scan documents to PDF using the copiers rather than making a bunch of copies. Also, catching up on RSS feeds between the questions.

5:00pm Desk shift over. I have just enough time to wrap up my projects for the day and prep for tomorrow, grab a quick bite to eat, and then I’m off to the other side of campus where I have choir rehearsal until 7pm.

Thank you for reading!

IL2009: Technology: The Engine Driving Pop Culture-Savvy Libraries or Source of Overload?

Speaker: Elizabeth Burns

Technology and pop culture drive each other. Librarians sometimes assume that people using technology like smart phones in libraries are wasting time, both theirs and ours, but we really don’t know how they are using tech. Librarians need to learn how to use the tech that their user community employs, so don’t hinder your staff by limiting what tech they can use while in the workplace.

Libraries also have the responsibility to inform users of the services and technology available to them. Get the tools, learn how to use them, and then get to work building things with them.

Your library’s tech trendspotting group needs more than just the techie people. Get the folks who aren’t as excited about the shiny to participate and ask questions. Don’t let the fear of Betamax stop you – explore new devices and delivery methods now rather than waiting to find out if they have longevity. You never know what’s going to stick.

Speaker: Sarah Houghton-Jan

"Information overload is the Devil"

Some people think that it didn’t exist before mobile phones and home computers, but the potential has always existed. Think about the piles of books you’ve acquired but haven’t read yet. Information overload is all of the piles of things you want to learn but haven’t yet.

"We have become far more proficient in generating information than we are in managing it…"

Librarians are more equipped to handle information overload than most others. Manage your personal information consumption with the same kind of tools and skills you use in your professional life.

Some of the barriers to dealing with information overload are: lack of time or (a perceived lack of time), lack of interest or motivation, not being encouraged/threatened by management, not knowing where to start, and frustration with past attempts. Become like the automatic towel dispensers that have the towels already dispensed and ready to be torn off as needed.

Inventory your inputs and devices. Think before you send/subscribe. Schedule yourself, including unscheduled work and tasks. Use downtime (bring tech that helps you do it). Stay neat. Keep a master waiting list of things that other people "owe" you, and then periodically follow-up on them. Weed, weed, and weed again. Teach others communication etiquette (and stick to it). Schedule unplugged times, and unplug at will.

RSS/Twitter overload: Limit your feeds and following, and regularly evaluate them. Use lists to organize feeds and Twitter friends. Use RSS when applicable, and use it to send you reminders.

Interruptive technology (phone, IM, texts, Twitter, etc): Use them only when they are appropriate for you. Check it when you want to, and don’t interrupt yourself. Use your status message. Lobby for IM or Twitter at your workplace (as an alternative to phone or email, for the status message function & immediacy). Keep your phone number private. Let it ring if you are busy. Remember that work is at work and home is at home, and don’t mix the two.

Email: Stop "doing email" — start scheduling email scanning time, use it when appropriate, and deal with it by subject. Keep your inbox nearly empty and filter your messages. Limit listservs. Follow good email etiquette. Delete and archive, and keep work and personal email separate.

Physical items: Just because you can touch it, doesn’t mean you should keep it. Cancel, cancel, cancel (catalogchoice.org). Weed what you have.

Multimedia: Choose entertainment thoughtfully. Limit television viewing and schedule your entertainment time. Use your commute to your benefit.

Social networking: Schedule time on your networks. Pick a primary network and point other sites towards it. Limit your in-network IM.

Time & stress management: Use your calendar. Take breaks. Eliminate stressful interruptions. Look for software help. Balance your life and work to your own liking, not your boss’s or your spouse’s.

[Read Lifehacker!]

ERMS implementation woes

Ever since vendors started selling electronic resource management systems (ERMS), there has been a session or a round table at NASIG that discussed various libraries’ implementations of their ERMS. A few more hands were raised this year when the room was asked to indicate if they feel like they’ve finished implementing their ERMS, but it’s still a very small minority of librarians. When I did my conference report for NASIG 2009 yesterday (we have a bit of a backlog on monthly conference report meetings since there are so many conferences held in the spring and early summer), I created this using ProjectCartoon to illustrate some of the reasons why ERMS have been so difficult and time-consuming to implement:

ERMS woes

NASIG 2009: Informing Licensing Stakeholders

Towards a More Effective Negotiation

Presenters: Lisa Sibert, Micheline Westfall, Selden Lamoreux, Clint Chamberlain (moderator), Vida Damijonaitis, and Brett Rubinstein

Licensing as a process has not been improving very much. Some publishers are willing to negotiate changes, but some are still resistant. It often takes months to a year to receive fully signed licenses from publishers, which can tie up access or institutional processes. Negotiation time is, of course, a factor, but it should not effect the time it takes for both parties to sign and distribute copies once the language is agreed upon. One panelist noted that larger publishers are often less willing to negotiate than smaller ones. Damijonaitis stated that licenses are touched at fourteen different points in the process on their end, which plays into the length of time.

Publishers are concerned with the way the content is being used and making sure that it is not abused (without consequences). Is it necessary to put copyright violation language in licenses or can it live on purchase orders? Springer has not had any copyright violations that needed to be enforced in the past five or six years. They work with their customers to solve any problems as they come up, and libraries have been quick to deal with the situation. On the library side, some legal departments are not willing to allow libraries to participate in SERU.

Deal breakers: not allowing walk-ins, adjunct faculty, interlibrary loan, governing law, and basic fair use provisions. Usage statistics and uptime guarantees are important and sometimes difficult to negotiate. LibLicense is useful for getting effective language that publishers have agreed to in the past.

It’s not the libraries who tend to be the abusers of license terms or copyright, it’s the users. Libraries are willing to work with publishers, but if the technology has grown to the point where it is too difficult for the library to police use, then some other approach is needed. When we work with publishers that don’t require licenses or use just purchase orders, there is less paperwork, but it also doesn’t indemnify the institution, which is critical in some cases.

Bob Boissy notes that no sales person gets any benefit from long negotiations. They want a sale. They want an invoice. Libraries are interested in getting the content as quickly as possible. I think we all are coming at this with the same desired outcome.