<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:x="urn:schemas-microsoft-com:office:excel" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
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-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">I’d agree that it isn’t worth spending a lot of time on this. After vetting and adding we tend to use the disclaimer ‘we cannot guarantee access’ for OA titles as some of them are
unreliable; and of course if a broken link or a redirect (we have had in the past some OA titles morphing into porn sites, for example) was reported we would remove access. Otherwise we tend to concentrate on paid materials.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Louise<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">Louise Penn BA (Hons) MCLIP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Head of Resources and Technology<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Library Services<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#1F497D">University of West London</span></b><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">St Mary’s Road, Ealing, London, W5 5RF<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">Email <a href="mailto:louise.penn@uwl.ac.uk">
<span style="color:#0563C1">louise.penn@uwl.ac.uk</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Phone 0208 231 2328<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Linked In: </span><span style="font-size:8.5pt;font-family:"Arial",sans-serif;color:#333333;background:#F6F6F6">https://uk.linkedin.com/in/louisepenn</span><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;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Eril-l [mailto:eril-l-bounces@lists.eril-l.org]
<b>On Behalf Of </b>Eric Elmore<br>
<b>Sent:</b> 03 August 2017 17:27<br>
<b>To:</b> eril-l@lists.eril-l.org<br>
<b>Subject:</b> Re: [Eril-l] Freely accessible/OA resources policies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Yeah, we definitely took the less-is-better approach with OA resources. We vet them for incousion in our collection, then leave them unless the resource somehow becomes problematic (stops being
oa, changes hosting platforms, etc.). There’s so many other issues to deal with we tend to not worry much about the oa after we add them to our collections. Have a great day, it’s almost the weekend</span><span lang="EN-US" style="font-family:Wingdings;color:#1F497D">J</span><span lang="EN-US" style="color:#1F497D"><br>
E<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Eric Elmore |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Electronic Resources Coordinator |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The University of Texas at San Antonio |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">One UTSA Circle |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">San Antonio, TX. 78249-0671 |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">(O)210-458-4916/(F)210-458-4577 |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><a href="mailto:Eric.elmore@utsa.edu">Eric.elmore@utsa.edu</a> |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Lawless, Jane [<a href="mailto:jlawless@post03.curry.edu">mailto:jlawless@post03.curry.edu</a>]
<br>
<b>Sent:</b> Wednesday, August 02, 2017 7:59 AM<br>
<b>To:</b> Eric Elmore <<a href="mailto:Eric.Elmore@utsa.edu">Eric.Elmore@utsa.edu</a>>;
<a href="mailto:eril-l@lists.eril-l.org">eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> RE: Freely accessible/OA resources policies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Eric, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Our electronic resource evaluation, for better or for worse, is very tied to our renewal cycle. Resources that are not renewed, with associated cost, don’t go through a process of assessing: is this
resource used, is it still relevant, has it changed in a way that no longer meets our needs, etc. OA resources are added and don’t have a system of evaluation. That may not be a problem – depends on whether your goal for your electronic collection. But it
does seem to be an area where policy clarification could help.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Jane<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Jane Lawless, MLS, BA<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Associate Professor<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Electronic Resources and Serials Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Levin Library<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Curry College<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">1071 Blue Hill Avenue<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Milton MA 02186<br>
<a href="mailto:jlawless@curry.edu">jlawless@curry.edu</a> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">(617) 333 – 2245 <o:p>
</o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> 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>Eric Elmore<br>
<b>Sent:</b> Tuesday, August 01, 2017 2:10 PM<br>
<b>To:</b> <a href="mailto:eril-l@lists.eril-l.org">eril-l@lists.eril-l.org</a><br>
<b>Subject:</b> Re: [Eril-l] Freely accessible/OA resources policies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I apologize for this sounding dim, but how are OA resources not the same as any other resource, except that you don’t have to order and pay for them like a traditional resource? I mean they follow
all the normal rules of deciding on the “appropriateness of the content to your collection”, and then go straight to the “making them available” part by adding marc records to your opac and/or activation in your erm system.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">When we first started talking about adding oa resources to our profile, we just amended our “collections policy” to include them and moved on. Do you really need an entirely separate policy?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Eric Elmore |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Electronic Resources Coordinator |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">The University of Texas at San Antonio |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">One UTSA Circle |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">San Antonio, TX. 78249-0671 |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">(O)210-458-4916/(F)210-458-4577 |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><a href="mailto:Eric.elmore@utsa.edu">Eric.elmore@utsa.edu</a> |<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> 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>Bethany Greene<br>
<b>Sent:</b> Monday, July 31, 2017 12:42 PM<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] Freely accessible/OA resources policies<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Hello all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">If applicable, would anyone mind sharing their policy for acquiring, managing, and making accessible freely accessible/open access resources? Or could you point me in the direction of resources that may come in handy
for developing this type of policy? I’ve not had much luck finding these resources through the course of my own research. Please feel free to reply on or off list.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Bethany<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">----<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Bethany Greene<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Electronic Resources Management Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Duke University Libraries<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Durham, NC<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">(919) 660-3178<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><a href="mailto:bethany.d.greene@duke.edu">bethany.d.greene@duke.edu</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>