<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: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: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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",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-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;}
/* List Definitions */
@list l0
{mso-list-id:987125722;
mso-list-type:hybrid;
mso-list-template-ids:-1127301292 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">Ah, that’s always the question isn’t it</span><span style="font-family:Wingdings;color:#1F497D">J</span><span style="color:#1F497D"> How to get the most bang for the buck!! <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">It depends on <o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">whether or not the resource is actually included in the proquest knowledgebase (pqkb) or not,
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">what level of metadata indexing proquest has done. Does it have minimal metadata based solely on the package and hosting platform(no title list, no item level metadata, etc.), or does it have much
fuller metadata profile?<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">If it’s minimal, we usually turn the resource-level entry on and add it to our “open access” collection so it shows up on our annual stats for Ipeds, ACRL, etc. Then we look in OCLC to see if they have a richer
metadata package. If they do, we grab those records and add them to our opac and they get added to our nightly opac-to-summon marc record load.
<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">It’s really a metadata question as to how much effort we have to put in to make the thing discoverable.
<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">++++++++++++++++++++++++++++++++++++++<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"><a href="mailto:Eric.elmore@utsa.edu">Eric.elmore@utsa.edu</a><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"><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> Bethany Greene [mailto:bethany.d.greene@duke.edu]
<br>
<b>Sent:</b> Friday, August 04, 2017 7:27 AM<br>
<b>To:</b> Eric Elmore <Eric.Elmore@utsa.edu><br>
<b>Subject:</b> RE: Freely accessible/OA resources policies<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Hi Eric,<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">Thank you for your response. I suppose I should have framed my question a bit differently, as we are more interested in how other institutions
<i>manage</i> their freely accessible resources. Do you track these resources in your knowledgebase or otherwise display them in your catalog? We are trying to determine how we can still make these resources discoverable without putting in too much effort.<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,<br>
Bethany<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>Eric Elmore<br>
<b>Sent:</b> Tuesday, August 1, 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></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<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"><a href="mailto:Eric.elmore@utsa.edu">Eric.elmore@utsa.edu</a><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"><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>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></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>