[Eril-l] LexisNexis OpenURL failures

Tue Apr 26 05:40:05 PDT 2016

Good morning,

GVSU actually ended up canceling the resource for this very reason.  There were a few professors upset with the move, but for the most part everyone realizes that we have to send the message with our dollars that OpenURL functionality isn't an option, it's a must.

Jeffrey Daniels
Head of Knowledge Access and Resource Management Services
Grand Valley State University Libraries
danielsj at gvsu.edu<mailto:danielsj at gvsu.edu>

From: Eril-l [mailto:eril-l-bounces at lists.eril-l.org] On Behalf Of Catherine C Tuohy
Sent: Tuesday, April 26, 2016 7:04 AM
To: Mandi Schwarz; Serials in Libraries Discussion Forum (SERIALST at LISTSERV.NASIG.ORG); eril-l at lists.eril-l.org
Subject: Re: [Eril-l] LexisNexis OpenURL failures

It's never worked from SFX, but we keep it in the KB in order to let staff/faculty/students know where a specific journal's  coverage is located, then teach them to use that specific interface as well.  It's not a fun interface to use.

Catherine C. Tuohy
Assistant Director of Technology and Technical Services
Emmanuel College Library
400 The Fenway
Boston, MA 02115
617-264-7658

________________________________
From: Eril-l <eril-l-bounces at lists.eril-l.org> on behalf of Mandi Schwarz <Mandi.Schwarz at unbc.ca>
Sent: Monday, April 25, 2016 6:35 PM
To: Serials in Libraries Discussion Forum (SERIALST at LISTSERV.NASIG.ORG); eril-l at lists.eril-l.org
Subject: [Eril-l] LexisNexis OpenURL failures

Hello colleagues,

(Apologies for cross-posting.)

We have noticed a distressing number of OpenURL failures for LexisNexis content. Using our Summon instance, I located 100 articles (each in a different, mostly-randomly-chosen publication [1]) to test; 34 of them failed to get from our link resolver (360 Link) to the full text in LexisNexis. There are two errors that we encounter: "No Documents Found: You can edit your search and try again." and "Error: The document section name you entered is invalid. Please check for spelling errors or duplicate information." Comparing the citation in Summon with the article in LexisNexis, I often see no glaring errors. Serials Solutions maintains that the disconnect occurs with LexisNexis' unique indexing; to date, LexisNexis has been uninterested in rectifying this.

A 34% failure rate also indicates the inverse: a 66% success rate. Our librarians will be reviewing this to see if this meets the minimum success threshold; if not, we will discuss what we can do to minimize the impact on our users, which may include removing LexisNexis article-level results from Summon.

Our question to you is: Have you noticed similar failures at your institution? If so, have you changed how you present LexisNexis content to your users?

Thank you,

Mandi

[1] Using an updated title list from LexisNexis, I would randomly scroll through the list with my eyes closed and click on a cell. I would check that publication for language (I searched only English publications, because I was using an English search term) and format; I discovered that may publication types are not fully indexed in Summon, including: Boards, Panels & Tribunals; Cases; Decisions; Legislation, Statutes & Codes; and, Web-based Publications. As such, I chose publications listed as: Law Reviews & Journals; Magazines & Journals; or any type of 'News' item. I would then combine a publication title search with a truncated keyword, such as 'increas*', and work down the list until I found a title that returned at least one article for testing, which I would also choose by blind scrolling. Then I'd scroll the spreadsheet for the next title and repeat the process. While this method isn't scientifically random, it met the needs for this test.

Mandi Schwarz
Library Assistant - Electronic Resources
University of Northern British Columbia
250-960-6455; Mandi.Schwarz at unbc.ca<mailto:Mandi.Schwarz at unbc.ca>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.eril-l.org/pipermail/eril-l-eril-l.org/attachments/20160426/f9ab3413/attachment-0001.html>