<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Helvetica 55 Roman";}
/* 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-compose;
font-family:"Georgia","serif";
color:windowtext;}
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-family:"Calibri","sans-serif";}
@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="font-family:"Georgia","serif"">Good afternoon everyone,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">We use 360 Link for our link resolver service. Content accessed via the link resolver is generally opened in a window with a sidebar frame w/ info about the publication, error report form, and
a librarian help chat option. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">Some platforms have to be added to the “sidebar exclude list” so that this frame does not appear, otherwise the site won’t load properly or the content is otherwise inaccessible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">It seems that we are adding more platforms to the exclusion list recently. Our main ExLibris/ProQuest tech support person concurs:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Courier New"">“I think it's a growing trend. Cross-site scripting is a security risk, as well as "framing" content to put ads around it, so a lot of providers don't like to do it. Hopefully providers are responsive
to client feedback, since you're the ones who pay them. I would encourage you to let them know you don't like it. We just have to work around it when we can.”<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">Sure, we <i>can</i> ask our providers to allow frames, but if they see it as a security risk and the content itself is still accessible, they’re probably not going to switch back.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">I’m interested in whether other libraries are experiencing the same/similar issues. And what does the future of link resolving services look like, if this is the case? Will there be a way to provide
our users with the error report form, librarian chat, etc. without resorting to frames?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">(Relatedly, the error report form “spoofs” the sender’s email, which then gets filtered by our email security system because that’s a common spam/phishing technique. I guess I’m just frustrated
that the tools we’re trying to use to help our users are also commonly used for more malicious purposes. /venting)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">Thanks, and I hope y’all have a great weekend,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif"">Louise<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia","serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="193" height="4" id="Picture_x0020_9" src="cid:image001.png@01D22BAC.5C76E230" alt="Line.eps"><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif"">Louise Kidder</span></b><span style="font-size:8.0pt;font-family:"Helvetica 55 Roman""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616364">Discovery Services Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616364">Moody Medical Library/Academic Resources<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616364"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616364">University of Texas Medical Branch<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616364">301 University Blvd., Galveston, TX 77555-1035<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif"">P<span style="color:#616265">
</span><span style="color:#616364">409.772.8741</span><span style="color:#616265">
</span>F<span style="color:#616265"> </span><span style="color:#616364">409.762.9782</span><span style="color:#616265"><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif"">E<span style="color:#616265">
</span><span style="color:#EA2839"><a href="mailto:tlkidder@utmb.edu"><span style="color:blue">tlkidder@utmb.edu</span></a><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#EA2839"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#EA2839"><img border="0" width="154" height="74" id="Picture_x0020_2" src="cid:image002.png@01D22BAC.5C76E230" alt="UTMBlogo"></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#616265"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>