<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:black;}
.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:black">Hi everyone,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thank you all for your responses! I have compiled them, along with my original message, into th</span><span style="color:black">is document: https://drive.google.com/file/d/0ByZdFwoUk3oRQWNhRUt1OUc2XzA/view?usp=sharing</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">The consensus is that LexisNexis is a terrible platform – which is no surprise to those of us who work with it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">I have continued to ask LN to send their title list to link resolvers, and I finally got this response:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">“The A to Z lists for LN Academic are available for download from this site by region:
<a href="http://www.amdev.net/rpt_download.php?reg=CAN"><span style="color:black">http://www.amdev.net/rpt_download.php?reg=CAN</span></a> (this is the link for the Canadian reports.) These reports are updated on a quarterly basis.</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">These lists can be shared with any customers or link resolvers. I do have a list of a few list resolver providers (ProQuest – Serials Solutions, EBSCO) that I do notify when the list is
updated, so Serials Solutions should be aware of when the lists are updated. Link resolvers typically use the list labeled “Open URL” to determine how to construct the links to LNA, while the A to Z list provides a comprehensive view of all of the content
in the LNA menu.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">This is much better than the original response, which was essentially “we don’t send lists to link resolvers.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thank you again – I’ll be taking all of this information to our librarians so they can make a decision about access points specifically, and continuing our subscription.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Mandi<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">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></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Eril-l [<a href="mailto:eril-l-bounces@lists.eril-l.org">mailto:eril-l-bounces@lists.eril-l.org</a>]
<b>On Behalf Of </b>Mandi Schwarz<br>
<b>Sent:</b> Monday, April 25, 2016 3:36 PM<br>
<b>To:</b> Serials in Libraries Discussion Forum (<a href="mailto:SERIALST@LISTSERV.NASIG.ORG">SERIALST@LISTSERV.NASIG.ORG</a>);
<a href="mailto:eril-l@lists.eril-l.org">eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> [Eril-l] LexisNexis OpenURL failures<o:p></o:p></span></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>