<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=utf-8">
<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;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* 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.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:11.0pt;
font-family:"Calibri",sans-serif;}
p.gmail-m3701716581122425089msolistparagraph, li.gmail-m3701716581122425089msolistparagraph, div.gmail-m3701716581122425089msolistparagraph
{mso-style-name:gmail-m_3701716581122425089msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Georgia",serif;
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:521014815;
mso-list-template-ids:-1174252900;}
@list l0:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:848562601;
mso-list-template-ids:-1566005156;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1951205475;
mso-list-template-ids:-819791026;}
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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Erin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I believe YUL’s IT department has confirmed that option 3 would work – if all the related procedural complexities were worked out. The item_type_code and item_type_name data values
are certainly available through the API, as in this example: <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a href="https://libapp.library.yale.edu/VoySearch/GetAllMfhdItem?bibid=1166765">https://libapp.library.yale.edu/VoySearch/GetAllMfhdItem?bibid=1166765</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Francis<span style="font-family:"Georgia",serif;color:#1F497D">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b>From:</b> DCRM-L [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of
</b>Erin Blake<br>
<b>Sent:</b> Monday, May 13, 2019 12:57 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] access restriction data (Aeon)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Oooh! Is option 3 (Item Type) something that's actually known to work, or are you just wondering? We don't currently use the Voyager API with Aeon (but will after we upgrade to TomCat Webvoyage), but we'd been assuming we'd be able to pull
from the 506 in the mfhd.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If the 506 in the mfhd won't pass through, we definitely <i>
could </i>use an Item Type -- currently we have a grand total of three item types (Open stacks, Vault, Online resource) and none of them are actually used for anything at the moment.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Erin.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">----------------</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif">Erin Blake, Ph.D. | Senior Cataloger | Folger Shakespeare Library | 201 E. Capitol St. SE, Washington, DC, 20003 |
<a href="mailto:eblake@folger.edu">eblake@folger.edu</a> | office tel. +1 202-675-0323 |
<a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.folger.edu&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796914701&sdata=ypSFbPmqFl9lfFMbOw793GNVGpNM1UT4%2FWuEa5JRwsY%3D&reserved=0">
www.folger.edu</a></span> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, May 13, 2019 at 11:14 AM Lapka, Francis <<a href="mailto:francis.lapka@yale.edu">francis.lapka@yale.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif">For those who have implemented Aeon, I’m keen to hear how you pass access restriction information from your OPAC to Aeon (not from finding
aids). </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif">As Yale considers new procedures, at least three options come to mind:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<ol start="1" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l2 level1 lfo1">
<span style="font-family:"Georgia",serif">Record the restriction in the <a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fbibliographic%2Fbd506.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796914701&sdata=z9XC9X6MZtZttXyIlgXJ160ZRuA9nfnRL4r74YivWYQ%3D&reserved=0" target="_blank">
506 field</a> of the Bib record. The 1<sup>st</sup> indicator provides a machine-actionable value; the text provides an elaboration.
<i>Drawback</i>: When we have more than one copy, a 506 in the Bib may inadequately specify the copy to which it applies (in terms of machine actionability, at least).
</span><o:p></o:p></li></ol>
<p class="gmail-m3701716581122425089msolistparagraph"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<ol start="2" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l1 level1 lfo2">
<span style="font-family:"Georgia",serif">Record the restriction in the <a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.loc.gov%2Fmarc%2Fholdings%2Fhd506.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C686d03a044164965036308d6d7c425ac%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636933634796924705&sdata=EpQUB1UCAuBmv1RZb2alIYcAGaMZNFhQMJvHf7SFQFY%3D&reserved=0" target="_blank">
506 field</a> of the Holdings record. This allows us to specify a copy. <i>But</i>: [a] it may inadequately specify the volume or part to which it applies (in terms of machine actionability, at least), and [b] the Holdings 506 is not passed to our OPAC, nor
is it made available in our Voyager API (is the same true for other Voyager institutions?)</span><o:p></o:p></li></ol>
<p class="gmail-m3701716581122425089msolistparagraph"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<ol start="3" type="1">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:0in;mso-list:l0 level1 lfo3">
<span style="font-family:"Georgia",serif">Record the restriction by creating (or using) a separate Item Type (in the Voyager item record). If starting a catalog from scratch, this might be the most logical approach. It’s unclear if we could do this at Yale,
because we have so many procedures tied to the existing item types.</span><o:p></o:p></li></ol>
<p class="gmail-m3701716581122425089msolistparagraph"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif">All advice is appreciated.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif">Francis</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Georgia",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Francis Lapka · Senior Catalogue Librarian</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Department of Rare Books and Manuscripts</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Yale Center for British Art</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">203-432-9672 ·
<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>