<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Yes – LexisNexis linking failures have increased this past year, it seems, and it is the number one problem report we receive from users.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I reported this during the winter to both LexisNexis and Summon. They were going to work together to improve it. I haven’t heard back that they’ve re-indexed LN content. I don’t think it’s gotten better.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We haven’t had a conversation about this at my library this year. We have had it in the past, and decided we did not want to exclude those results from Summon despite their high linking failure rate. I hope that
the “news” callout (which we have enabled) helps the most vulnerable users avoid choosing LexisNexis results when they are not needed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I am also interested in hearing back from others on this issue.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Amy Fry<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Associate Professor, E-resources Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Jerome Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Bowling Green, OH 43403<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:afry@bgsu.edu"><span style="color:#0563C1">afry@bgsu.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="color:#1F497D">email is the best way to reach me</span></i><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Eril-l [mailto:eril-l-bounces@lists.eril-l.org]
<b>On Behalf Of </b>Mandi Schwarz<br>
<b>Sent:</b> Monday, April 25, 2016 6:36 PM<br>
<b>To:</b> Serials in Libraries Discussion Forum (SERIALST@LISTSERV.NASIG.ORG) <SERIALST@LISTSERV.NASIG.ORG>; eril-l@lists.eril-l.org<br>
<b>Subject:</b> [Eril-l] LexisNexis OpenURL failures<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello colleagues,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">(Apologies for cross-posting.)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Mandi<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">[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:
<span style="color:black">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.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mandi Schwarz<br>
Library Assistant – Electronic Resources<br>
University of Northern British Columbia<br>
250-960-6455; <a href="mailto:Mandi.Schwarz@unbc.ca">Mandi.Schwarz@unbc.ca</a><o:p></o:p></p>
</div>
</body>
</html>