<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:#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: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-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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span 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 style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span 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 style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">++++++++++++++++++++++++++++++++++++++<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Eric Elmore |<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Electronic Resources Coordinator |<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The University of Texas at San Antonio |<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">One UTSA Circle |<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">San Antonio, TX. 78249-0671 |<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">(O)210-458-4916/(F)210-458-4577 |<o:p></o:p></span></p>
<p class="MsoNormal"><span 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 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>Bethany Greene<br>
<b>Sent:</b> Monday, July 31, 2017 12:42 PM<br>
<b>To:</b> eril-l@lists.eril-l.org<br>
<b>Subject:</b> [Eril-l] Freely accessible/OA resources policies<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">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Bethany<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">----<o:p></o:p></p>
<p class="MsoNormal">Bethany Greene<o:p></o:p></p>
<p class="MsoNormal">Electronic Resources Management Librarian<o:p></o:p></p>
<p class="MsoNormal">Duke University Libraries<o:p></o:p></p>
<p class="MsoNormal">Durham, NC<o:p></o:p></p>
<p class="MsoNormal">(919) 660-3178<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:bethany.d.greene@duke.edu">bethany.d.greene@duke.edu</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>