<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:"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;}
@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";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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">Thank you everyone for your input. You gave me some things to think about that I hadn’t considered. And I agree that the goal is to not overly complicate things. <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">The question that was raised was from a user that saw our link on Wiley Online Library (for content we don’t have access to). The link appeared near a Wiley button that says “Get access to the full text of this
article” next to the image of a key. That has to be confusing. The multitude of full-text links on publisher’s platforms definitely complicates things.
<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">While I like the simplicity of “Check for Full Text”, I suspect it might help distinguish the link resolver link to include BNL somewhere (similar to what Melissa mentioned). Also, text that might make perfect
sense on one platform may be confusing in another situation. That being said I agree that consistency is important.<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’m going to think on this a bit.<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">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Leah<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Leah Donley<br>
Research Library <br>
Brookhaven National Laboratory<br>
Email: </span><span style="color:#1F497D"><a href="mailto:donley@bnl.gov"><span style="font-size:10.0pt;font-family:"Times New Roman","serif";color:#0563C1">donley@bnl.gov</span></a></span><span style="color:black"><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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><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""> Pennington, Buddy D. [mailto:penningtonb@umkc.edu]
<br>
<b>Sent:</b> Wednesday, February 07, 2018 1:54 PM<br>
<b>To:</b> Flanders, Jo; Zhang, Bin; Donley, Leah; Eril-l@lists.eril-l.org<br>
<b>Subject:</b> RE: Link resolver text<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">I think that is a good one, Jo. We considered that but shortened it to Full Text. Some folks are adverse to Full Text because it is the same language used by many vendors to mean actual full text. If you fall
into that category I would recommend Check for Full Text. <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">Buddy Pennington<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Head of Library Systems & Technology (Librarian III)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Miller Nichols Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">University of Missouri--Kansas City<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> Flanders, Jo [<a href="mailto:jlflanders@stcloudstate.edu">mailto:jlflanders@stcloudstate.edu</a>]
<br>
<b>Sent:</b> Wednesday, February 07, 2018 12:45 PM<br>
<b>To:</b> Pennington, Buddy D. <<a href="mailto:penningtonb@umkc.edu">penningtonb@umkc.edu</a>>; Zhang, Bin <<a href="mailto:bzhang@csus.edu">bzhang@csus.edu</a>>; Donley, Leah <<a href="mailto:donley@bnl.gov">donley@bnl.gov</a>>;
<a href="mailto:Eril-l@lists.eril-l.org">Eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> RE: Link resolver text<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">How about just “Check for Full Text” - does the user really care where they are checking (@soandso)? They just want to know if the full text is available. Leading the user to check for full text at a particular “place” (publisher) is
(or should) be done behind the scenes. So if the user is already into a particular database or journal they can click “check for full text.” Or better yet, the user clicks “check for full text” and they are taken to the resource that gives them full text
if it is available.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Jo Flanders<o:p></o:p></p>
<p class="MsoNormal">Associate Professor, E Resource/Serials Librarian<o:p></o:p></p>
<p class="MsoNormal">University Library<o:p></o:p></p>
<p class="MsoNormal">St Cloud State University<o:p></o:p></p>
<p class="MsoNormal">St Cloud, MN<span style="color:#1F497D"><o:p></o:p></span></p>
<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 [<a href="mailto:eril-l-bounces@lists.eril-l.org">mailto:eril-l-bounces@lists.eril-l.org</a>]
<b>On Behalf Of </b>Pennington, Buddy D.<br>
<b>Sent:</b> Wednesday, February 07, 2018 12:34 PM<br>
<b>To:</b> Zhang, Bin <<a href="mailto:bzhang@csus.edu">bzhang@csus.edu</a>>; Donley, Leah <<a href="mailto:donley@bnl.gov">donley@bnl.gov</a>>;
<a href="mailto:Eril-l@lists.eril-l.org">Eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> Re: [Eril-l] Link resolver text<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">We wrestled with this too. Initially we used “Find it @ UMKC” but we had students think they had to come into the library to get it. We changed it to “Full Text” and sometimes people are confused when they do
not actually land on the full text, but overall we think it is better than what we used before. I’m not sure there is a magic wand answer to this because the underlying technology is complicated but the user doesn’t need to know that.
<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"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Buddy Pennington<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Head of Library Systems & Technology (Librarian III)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Miller Nichols Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">University of Missouri--Kansas City<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 [<a href="mailto:eril-l-bounces@lists.eril-l.org">mailto:eril-l-bounces@lists.eril-l.org</a>]
<b>On Behalf Of </b>Zhang, Bin<br>
<b>Sent:</b> Wednesday, February 07, 2018 12:27 PM<br>
<b>To:</b> Donley, Leah <<a href="mailto:donley@bnl.gov">donley@bnl.gov</a>>; <a href="mailto:Eril-l@lists.eril-l.org">
Eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> Re: [Eril-l] Link resolver text<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">We have “Find It @ Sac State”<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">---</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Bin Zhang</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Digital Information Services Librarian</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Library Systems & IT Services, University Library
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">California State University, Sacramento</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">2000 State University Drive East, Sacramento, CA 95819-6039</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">(916) 278-5664 (O); (916) 278-3891 (F)</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">bzhang AT csus DOT edu</span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<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 [<a href="mailto:eril-l-bounces@lists.eril-l.org">mailto:eril-l-bounces@lists.eril-l.org</a>]
<b>On Behalf Of </b>Donley, Leah<br>
<b>Sent:</b> Wednesday, February 07, 2018 10:22 AM<br>
<b>To:</b> <a href="mailto:Eril-l@lists.eril-l.org">Eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> [Eril-l] Link resolver text<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">For those of you who have a link resolver and have activated it within databases and on publisher’s websites, what do you use for the link resolver text (mouseover text when there is an image or on websites where you can’t include an image
at all)? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Our current practice is to use “Full Text @ BNL”, but I’m rethinking that after a question from a user. I can see how it would be unclear and give the impression that clicking will always lead to accessible full text, instead of CHECKING
for accessible full text, which is really what’s happening. But how to convey that and keep it short and sweet? “Check for Full Text @ BNL”?<o:p></o:p></p>
<p class="MsoNormal"><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">Leah Donley<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Leah Donley<br>
Research Library <br>
Brookhaven National Laboratory<br>
Email: </span><a href="mailto:donley@bnl.gov"><span style="font-size:10.0pt;font-family:"Times New Roman","serif";color:#0563C1">donley@bnl.gov</span></a><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>