Troubleshooting Electronic Resource Problems Reported by Students

Although my job title is user experience librarian, I help out quite a bit with managing electronic resources in my library. Over the past few years, I’ve gone down deep in the weeds countless times trying to figure out what went wrong when a user reported being unable to access an electronic resource. Some times it’s just one article, some times it’s an entire database. The possible points of failure (or confusion) for the user are many. Here’s an exhaustive list (for me, at least) of what commonly goes wrong for our users.

user names and passwords

  • entering the wrong user name and/or password (e.g., typos, misremembered logins, etc.)
  • not knowing what their user name and password is
  • not realizing that the resource requires you to create your own username and password
  • trying to access the resource by going straight to the resource via web search instead of using library’s link (that goes through some sort of authentication system)
  • user has logins for more than one institution in a consortium and uses the wrong one

authentication systems

  • trying to access the resource by going straight to the resource via web search instead of using library’s link (that goes through some sort of authentication system)
  • resource hasn’t been listed correctly in the authentication system (URL for the resource has changed)
  • resource requires some new special set up in the authentication system
  • user is from another library (that may be part of a local or state consortium) but doesn’t realize that resource is strictly limited to users at that specific library
  • authentication system is blocked by firewall/security settings on user’s computer or network


  • database requires specific browser (often Internet Explorer)
  • browser settings need to be changed to allow for specific functionality in the resource

licensing issues

  • user is now an alum and doesn’t realize off-campus access is now gone
  • license doesn’t allow walk-ins and/or alumni to use database

problems caused by the vendor

  • resource is down for all subscribing institutions
  • database is searchable but full text links no longer working
  • vendor has mistakenly shut down access for the library
  • vendor has intentionally shut down access for the library because of suspicious use or expired license
  • vendor hasn’t communicated changes in its holdings to services that rely on that information (such as knowledgebases that help libraries keep track of online journal access)
  • database has agreed to an unusual restrictive license from a publisher whose content is aggregated (e.g., EBSCO and Harvard Business Review)
  • library has cancelled subscription but forgot to remove all links to it on their website, catalog, discovery layers, knowledgebases, etc.

availability options

  • user doesn’t notice the full text links on a record
  • user unaware of interlibrary loan as a service option
  • user has found content that isn’t part of a library’s subscription in a database
  • user unaware that resource might be available elsewhere as open access (e.g., in an institutional repository, on the author’s website, etc.)
  • user has found book or periodical record in the catalog but doesn’t recognize that the resource is print only

out of date info in knowledgebases

  • library has incorrectly listed a resource as something that is subscribed to
  • journal publisher or database publisher hasn’t communicated to the knowledgebase vendor changes in holdings (I’m looking at you Gale)
  • knowledgebase vendor hasn’t yet updated their system with latest info from journal publishers or database vendors

OpenURL linking

  • database where citation-only record was first found failed to create a properly formed OpenURL
  • database that the link resolver menu sent the user to is unable to properly interpret incoming OpenURL
  • user didn’t notice link resolver option in the database (usually labeled locally as “Find it at [name of institution]”)
  • user didn’t understand what to do in the link resolver menu


  • user is trying to re-visit a URL saved from a previous session (instead of using a permalink)
  • permalink that the user got from the database results previously didn’t include URL syntax that would route it through the library’s authentication system
  • permalink that the professor put on the course website or the learning management system isn’t proxied

problems specific to ebooks

  • user expected full book could be downloaded
  • user didn’t realize complexity of getting started (such as registering for an Adobe ID)

problems specific to articles

  • user has a found a short article but mistakenly believes it’s not the whole article

Testing Embedded LibGuides Content on External Sites

At my library, we’re thinking of using LibGuides to manage our database lists for the redesigned library website. I’m just experimenting here to see how well the API from LibGuides works that lets you publish a box from a LibGuide on an external website. Currently, we use a homegrown database to manage the display of databases in A-Z and subject breakdowns on the library site. We also use LibGuides for the usual kinds of subject guides. To help my colleagues who make LibGuides feel confident that the database links they use are the latest ones, I have a privately published LibGuide that maintains a canonical set of URLs. When librarians create new LibGuides and want to link to a given database, they don’t have to copy and paste URLs; instead, they can create a link that has a URL that is mapped to the canonical one. If I have to update the canonical URL in LibGuides, then all the LibGuides that use that mapped URL will automatically get updated with the latest URL.

With no effort to customize the look of this box from my philosophy subject guide, here’s a box republished via API:

LexisNexis Academic To Release Interface Optimized for Mobile Web Browsers

As an update to my last post (“Apps vs. Mobile Web Optimized Interfaces for Search and Discovery”), I just want to make a quick note that LexisNexis has confirmed that their forcoming new mobile interface with LexisNexis Academic will be not be a dowloadable app but instead something that is designed to work in mobile web browsers.

I hope that they’ve designed it so that it automatically detects whether you’re using a browser on a phone and then redirects you to the optimized interface. Some of the database vendors that offer mobile browser interfaces require the library to set up a unique of URLs for the mobile versions, which means the number of links you have to maintain and provide to your user has doubled. As anyone who has tried to maintain electronic resources for a library knows, keeping on top of URL changes for those resources is a major time sink, as the links are usually spread across a wide number of pages on a library website.

Apps vs. Mobile Web Optimized Interfaces for Search and Discovery

I really wish the publishing companies, scholarly societies, and database vendors that are exclusively developing apps for mobile devices would rethink their preference for apps over interfaces that are optimized to work on mobile web browsers. Ever since Apple launched its app store on iTunes, web developers have been debating whether it is preferable to do a mobile web optimized site or instead release an app. Now that the vendors that libraries rely on for databases have earnestly entered the world of mobile design, there seems to be a lack of uniformity of opinion about the best way to proceed. Some companies have only released apps:

Others have only done interfaces that are slimmed down enough to work comfortably within a mobile web browser:

Some have hedged their bets and offer both apps and mobile web interfaces:

Some notable vendors have yet to release their mobile service yet. LexisNexis Academic will have a mobile interface this summer, though I’m still not clear if it’s an app or a mobile browser interface. ProQuest’s new platform for it’s databases is supposed to have mobile browser interface, but I haven’t seen it yet (I’m not sure if it hasn’t been released yet or if it requires you to switch over to the new platform, which we haven’t yet done in my library). Having tried most of the apps and web interfaces for the products above and having thought about how my library will promote them to our students, I’ve come to the conclusion that for the moment, the mobile web experience is superior to the app one. Here are the reasons why I’m not a fan of the apps I’ve seen.

  • Apps have to be downloaded. The user who wants to find something has to first take the extra step of installing an app.
  • Apps have to be updated. I don’t know if the apps that the library vendors will provide will require as frequent updates as the other apps on my phone, but even having to do it at all is an extra annoying step for our users to periodically follow.
  • Clunky authentication. Users have to do things like fill out a form with their app and get an email back from the vendor with a special code to be entered into the app. Other apps have to be “paired” up while the user is on the library’s or college’s network.
  • Idiosyncratic authentication. It’s hard enough getting our users to enter some sort of user name/password combination for most of our databases they access via regular web browsers, but at least it is a consistent experience. With apps, we’re expecting our users to get used to a variety of authentication schemes that vary from app to app. Furthermore, each app requires you to authenticate. If you use a browser to visit library databases (on a regular browser or a web one), you authenticate once that session and use as many databases as you want without having to re-authenticate each time you try a difference resource.
  • Apps take up space. Our library has huge ecosystem of databases. Do we really expect our users will want to use up valuable screen real estate and space in the phone’s memory with all the databases they may need?
  • Eclipse other databases. It’s already challenging enough to get users to recall that there are more databases than the ones with the easy-to-recall brand names (JSTOR, LexisNexis). A user who has downloaded a database app or two is going to be less likely to recall that there may be other, possibly more relevant, database options for mobile search. If you are looking at mobile optimized web page listing all the library’s mobile-friendly databases (perhaps sorted by subject, by title, etc.), there’s a greater chance they’ll use a wider variety of databases than if they’d downloaded an app or two.
  • App names often differ from regular web versions. Why should we add to the mental burden of our users by asking them to recall that what we call IEEE Computer Society Digital Library (an ungodly name to begin with) is the same as IEEE Xplore Mobile Digital Library (the former is the regular web version and the latter is the mobile app version)? Or expect them to know that buried in the sprawling app from Gale called Access My Library are the mobile versions of Business & Company Resource Center, Gale Virtual Reference Library, and more?
  • No link resolvers. I didn’t see any link resolvers in the apps. Admittedly, it’s not clear to me whether the link resolver we use (SFX) works properly in the mobile browsers I’ve used. Assuming that link resolvers can be made to work in the browser, I like that we can recreate the ecoystem of databases and link resolution that we have on the regular web. I don’t see how that ecosystem can be easily recreated in a world of mobile apps for each database.
  • Libraries can’t customize apps. The admin options that libraries are given to tinker with the look and feel of their web-based databases are not available with the app versions of databases.
  • Vendors don’t offer apps for all mobile operating systems. Very few apps come in versions for all the major mobile operating systems: iOS (for iPhones and iPod Touches), Android, and Blackberry.
  • Developing apps is expensive. The wish list of things I would like database vendors to fix or improve is lengthy. Spending precious time and money to develop apps is not at the top of my list. The cheaper and, in my mind, better option, is to develop for mobile web browsers first, as that lets vendors get their products onto a wider range of mobile device more quickly than if they were to take the time to develop apps for each of the mobile OSes.

I recognize that the vendors, publishers, and scholarly societies are just dipping their toes into the world of mobile services. I hope, though, that they don’t get carried away with apps and can recognize the limitations that those apps have right now.

H.W. Wilson Gets Swallowed Up

I was saddened to hear yesterday on the Against the Grain blog that EBSCO would be acquiring H.W. Wilson. While I have no doubt that Wilson was ailing financially for a while and wasn’t exactly winning any love for its interface, I do have fond feelings for the company for two reasons. First, one of the few things that I recall about my elementary school library from the early 1970s was being introduced to the Readers’ Guide to Periodical Literature. Second, while in library school at the Pratt Institute in the last 1990s, I went on a tour of the Wilson offices up in the Bronx. A a burgeoning library geek, I was thrilled to see cubicle farms where staff were actively indexing journals and magazines as we walked by. Even better, though, was the on-site printing plant that Wilson still maintained and was in operation when we visited.

Fewer database vendors means to me less competition and less innovation, bad news for those of us in the library world. Here’s the text of the email that went just went out moments ago to Wilson customers about the acquisition by EBSCO:

A New Future for H.W. Wilson

Dear Customers:

We have exciting news to share.  As you know, it has always been our goal to provide the best products and services to our customers, and we are dedicated to supporting the library community as a whole.  We will continue to uphold these objectives, and will do so together with EBSCO as we move forward. 

Effective May 31, 2011, Wilson has merged with EBSCO Publishing.  We have maintained a strong partnership with EBSCO through the years, and this joining marks an exciting new beginning that will be immensely positive for Wilson customers.  With more than 150 years of combined experience serving libraries and research needs, the strengths of both companies will come together to provide greater products and services – enabling us to take the Wilson databases to unprecedented heights, and together enhance the EBSCO databases as well.  As Wilson databases are added to the EBSCOhost platform, customers will be encouraged to transition to EBSCOhost, and you will begin to see the results of the combined effort of Wilson and EBSCO.

This partnership will enable huge strides for our companies in serving our customers, and helping you to support your end users.  We thank you for your business and loyalty through the years.  We look forward to serving your needs for years to come.

For questions that we anticipate will be frequently asked, please visit:




Deborah Loeding
Vice President, Sales & Marketing


Naming Conventions for Databases

One of the things I struggle with when thinking about the library website is how to name the databases and other online resources that we subscribe to at my library. My general principle is to have the database name on the library website match the way that the database names itself. In general, this means leaving the platform/vendor name out of the name we use on the library website. Rather than say “EBSCOhost Academic Search Complete” or “Academic Search Complete (EBSCOhost),” it makes more sense to just list it as “Academic Search Complete.”

I get that including the platform/vendor name as part of the naming system you use on the website may help those users who can’t quite remember the exact name of the database they were supposed to use or that they used once before. By offering the vendor or platform name (EBSCOhost, ProQuest, WilsonWeb, etc.) as well as the specific database name, we’re giving our users  more details that may trigger recognition. On the other hand, I’m more concerned that students be able to indicate the database name correctly in any citations that they include in a bibliography. In general, the style guides seem to suggest that you just use the database name. Many of the databases will generate citations for sources that you find, and those citations usually leave off the vendor or platform name.

This week, I noticed that a database we’ve listed as “Westlaw Campus” is probably more correctly referred to as “Campus Resarch.” Before I recommend to my colleagues that we rename the database on our site, I’m curious about how other libraries list that database on their library sites. If you’ve got 30 seconds, it would be great if you could indicate on this poll in Doodle how your library handles the naming of this database. I’ll do a post later where I summarize the results.

Librarians vs. Google: Fighting the Web Giant’s Book Deal – TIME

The library community recalls with horror the pricing fiasco that occurred when industry consolidation left academic journals in the hands of five publishing companies. The firms hiked subscription prices 227% over a 14-year period, between 1986 and 2002, forcing cash-strapped libraries to drop many subscriptions, according to Van Orsdel. “The chance of the price being driven up in a similar way (in the Google deal) is really very real,” he says.

I like the quote here from Lee Van Orsdel, who is the dean of university libraries at Grand Valley State University (MI).