<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
At the Beinecke we do the same. I was mistaken to say "instance" and not "occurrence." Perhaps the 655s could be sorted out on that basis.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Stephen Young</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> DCRM-L <dcrm-l-bounces@lib.byu.edu> on behalf of Auyong, Dorothy <dauyong@huntington.org><br>
<b>Sent:</b> Wednesday, May 27, 2020 7:40 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration</font>
<div> </div>
</div>
<div lang="EN-US">
<div class="x_WordSection1">
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
At the Huntington we only apply subfield 5 CSmH to item occurrence, not instance.</p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<b><span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">Dorothy Auyong</span></b></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Garamond",serif">Early Books and Codices Cataloging Manager</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:10.0pt; font-family:"Garamond",serif">Acquisitions, Cataloging & Metadata Services</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<b><span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827; text-transform:uppercase; letter-spacing:.6pt">The Huntington</span></b><b><span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">
</span></b></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">Library, Art Museum, and Botanical Gardens
</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">1151 Oxford Road, San Marino, CA 91108</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span style="font-size:10.0pt; font-family:"Garamond",serif; color:black"><a href="https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.huntington.org%2F&data=02%7C01%7Cstephen.young%40yale.edu%7C4cb2dfa787bd4b34501508d8029760fd%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262196485433439&sdata=I60vEqofI2CjxcwUQEHkoIX0P6%2BkOarRz85a%2F0QtCEE%3D&reserved=0" originalsrc="https://www.huntington.org/" shash="VXW2zZQN94paYuZsFy0jdl1MmjnPmGEZ1ovdM1cGWhwgEy5a2FmCDmyQwBEZecaNBtrNdj3yuUG/z919Zgkh7eAQMDEqdNG11sjGwB3AfH+HH17I4eWLKp1n2El4czzbgKIpw/PHT5dz+JgHdSMkLPA4OB6mUmXBuF7m9bJvKmI="><span lang="DE" style="color:#3E4827">huntington.org</span></a></span><span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827"></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-autospace:none">
<span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">T 626-405-2188</span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827">E
<a href="mailto:dauyong@huntington.org">dauyong@huntington.org</a></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827"> </span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<img border="0" width="55" height="55" id="x_Picture_x0020_6" style="width:.5763in; height:.5763in" data-outlook-trace="F:1|T:1" src="cid:image001.png@01D63445.86D349B0"><span lang="DE" style="font-size:10.0pt; font-family:"Garamond",serif; color:#3E4827"></span></p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<b>From:</b> DCRM-L <dcrm-l-bounces@lib.byu.edu> <b>On Behalf Of </b>Young, Stephen<br>
<b>Sent:</b> Wednesday, May 27, 2020 11:31 AM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration</p>
</div>
</div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; color:black">Our practice for Beinecke records is to add subfield 5 CtY-BR to those 655s that apply to instance and not work. Do others follow a similar practice?</span></p>
</div>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; color:black">Stephen R. Young</span></p>
</div>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; color:black">Rare Book Catalog Librarian</span></p>
</div>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-size:12.0pt; color:black">Beinecke Rare Book and Manuscript Library</span></p>
</div>
<div class="x_MsoNormal" align="center" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<b><span style="color:black">From:</span></b><span style="color:black"> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>> on behalf of Lapka, Francis <<a href="mailto:francis.lapka@yale.edu">francis.lapka@yale.edu</a>><br>
<b>Sent:</b> Wednesday, May 27, 2020 2:20 PM<br>
<b>To:</b> 'dcrm-l@lib.byu.edu' <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> [DCRM-L] 655 field -- migration</span> </p>
<div>
<p class="x_MsoNormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
</div>
<div>
<div>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">Hi all.</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">In a 2018 report on a MARC-to-BIBFRAME data conversion executed by Casalini for Yale, a Yale TF had this to say about the 655 field:</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:.5in">
… Conversion of the 655 field clashes with the ambiguity inherent in MARC bibliographic records; this field could map to work, instance, or item properties. To overcome MARC’s ambiguity in such fields, a converter would have to employ pattern recognition that
goes beyond the MARC encoding: for example, treating all 655 fields with the value “rbprov” in subfield $2 as bf:genreForm with a domain of bf:Item. This might add considerable complexity to the conversion specification, but without this upfront complexity,
the outcome will be one of diminished discovery. …</p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">As the day nears when we may need to convert our MARC to BIBFRAME for production usage, I’m curious if other institutions have started to make plans for how to migrate 655 data to the correct Work/Instance/Item
(WII) entity. In BIBFRAME, the <a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fid.loc.gov%2Fontologies%2Fbibframe.html%23p_genreForm&data=02%7C01%7Cstephen.young%40yale.edu%7C4cb2dfa787bd4b34501508d8029760fd%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262196485433439&sdata=tGh7GQMHGGoBncUlvJXpaXYOJRpHZUoZUIgCrla6BJ0%3D&reserved=0" originalsrc="http://id.loc.gov/ontologies/bibframe.html#p_genreForm" shash="IKXLJE/bx0ot0mvL8+xVQramXbwBYDEQVw2yahNUPPdPKxdJGuwcZxTJK6A8/yluSDfsJDXHz4oCTcMoTsTkCSxqX+Y+24+eNSvsOy8iqXDl3Hnt1TnVwxWfy9h7tZVyKXu2bgLIOs1zsKx82Y3Js7dcWn5z9G9J95BetBghQpY=">
genreForm property</a> can be used with work, instance, or item. In the Library of Congress MARC-to-BIBFRAME conversion specification, the 655 field maps always to bf:Work (see
<a href="https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.loc.gov%2Fbibframe%2Fmtbf%2FConvSpec-3XX-v1.5p.xlsx&data=02%7C01%7Cstephen.young%40yale.edu%7C4cb2dfa787bd4b34501508d8029760fd%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262196485433439&sdata=8v3HmxlfmQfVif9QGgCJxa2kKNvaNVJ8v%2BcqgZUdgto%3D&reserved=0" originalsrc="https://www.loc.gov/bibframe/mtbf/ConvSpec-3XX-v1.5p.xlsx" shash="kggafy69Mml3MRloL/goQFaaqzNR3SvduMpOeaOniNpQ0LEaUVBciHkMRsDnX8f85EetkQGs8vVWXXOtUgK2yPbeKXn3QaCbuvPoZ99sTVdiXWesiwpDvEe5esm1XQeLi4ucJOmdRyUzJc4sEvpeZNuSik2DGo1M7nRssd0UPnA=">
this LC specification</a>). </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">Has your institution started to consider the issue? If so, what are your plans?
</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">More questions:</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="1" type="1" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l5 level1 lfo1">
<span style="font-family:"Georgia Pro",serif">Would it be acceptable to migrate all 655 data to the bf:Work?</span></li></ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="2" type="1" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l8 level1 lfo2">
<span style="font-family:"Georgia Pro",serif">If we’d like 655 data to migrate to Work, Instance, and Item, as appropriate, it seems that there are two broad options to consider:</span></li></ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="2" type="1" style="margin-bottom: 0in;margin-top:0in">
<ol start="1" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l0 level2 lfo3">
<span style="font-family:"Georgia Pro",serif">Leave the 655 data unchanged (from current practice) but add a considerable amount of complexity to the conversion spec to make the WII distinctions; or</span></li></ol>
</ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:1.0in">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="2" type="1" style="margin-bottom: 0in;margin-top:0in">
<ol start="2" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l7 level2 lfo4">
<span style="font-family:"Georgia Pro",serif">Adjust the 655 data in some manner before data conversion, so that WII distinctions are clearly articulated in MARC, requiring less complexity from the conversion spec.</span></li></ol>
</ol>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="3" type="1" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l6 level1 lfo5">
<span style="font-family:"Georgia Pro",serif">In method A – leave the 655 data unchanged – what would be a reasonable strategy? Possibilities:</span></li></ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="3" type="1" style="margin-bottom: 0in;margin-top:0in">
<ol start="1" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l1 level2 lfo6">
<span style="font-family:"Georgia Pro",serif">Make broad mapping rules based on the thesaurus value in 655 subfield $2. For example, $2 rbprov data maps to Item (works well), $2 rbbin maps to Item (accurate more often than not), $2 gmgpc maps to Instance (mostly
true), $2 rbgenr maps to Work (mostly true?), and so on.</span></li></ol>
</ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:1.0in">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="3" type="1" style="margin-bottom: 0in;margin-top:0in">
<ol start="2" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l2 level2 lfo7">
<span style="font-family:"Georgia Pro",serif">Make detailed mapping rules accounting for every expected term, e.g. Publisher’s cloth bindings maps to Instance, and so on.
</span></li></ol>
</ol>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:1.0in">
<span style="font-family:"Georgia Pro",serif">Both of these possibilities assume that the converter – likely the work of a vendor – is able to incorporate such complexity.</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="4" type="1" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l4 level1 lfo8">
<span style="font-family:"Georgia Pro",serif">In method B – adjust the 655 data before conversion – what’s reasonable? I can think of at least one possibility:</span></li></ol>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:.5in">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<ol start="4" type="1" style="margin-bottom: 0in;margin-top:0in">
<ol start="1" type="a" style="margin-bottom: 0in;margin-top:0in">
<li class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:0in; mso-list:l3 level2 lfo9">
<span style="font-family:"Georgia Pro",serif">Add a new nugget of data to the 655 entry to declare a term’s WII alignment. For example, how about a (newly defined) subfield $i? Such a subfield could align the data with WII/WEMI properties, e.g. 655 _7 $i gf-item
$a Bookplates. $2 rbgenr</span></li></ol>
</ol>
<p class="x_xmsolistparagraph" style="margin: 0in 0in 0.0001pt 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;margin-left:1.0in">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">What are the other possibilities? What’s most likely to succeed?</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif">Francis</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Georgia Pro",serif"> </span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Calibri Light",sans-serif">Francis Lapka</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<i><span style="font-family:"Calibri Light",sans-serif">Senior Catalogue Librarian</span></i></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Calibri Light",sans-serif">Department of Rare Books and Manuscripts</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Calibri Light",sans-serif">Yale Center for British Art</span></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
<span style="font-family:"Calibri Light",sans-serif">203-432-9672 · </span><a href="mailto:francis.lapka@yale.edu"><span style="font-family:"Calibri Light",sans-serif; color:blue">francis.lapka@yale.edu</span></a></p>
<p class="x_xmsonormal" style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;">
</p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>