<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:"Georgia Pro";}
/* 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:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxmsonormal, li.xxmsonormal, div.xxmsonormal
{mso-style-name:x_xmsonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxmsolistparagraph, li.xxmsolistparagraph, div.xxmsolistparagraph
{mso-style-name:x_xmsolistparagraph;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxmsonormal0, li.xxmsonormal0, div.xxmsonormal0
{mso-style-name:x_x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxxmsonormal, li.xxxmsonormal, div.xxxmsonormal
{mso-style-name:x_x_xmsonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.xxxmsolistparagraph, li.xxxmsolistparagraph, div.xxxmsolistparagraph
{mso-style-name:x_x_xmsolistparagraph;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Georgia Pro",serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal-compose;
font-family:"Georgia Pro",serif;
color:windowtext;}
.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:439644342;
mso-list-template-ids:-1;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1309360324;
mso-list-template-ids:-1;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1400714325;
mso-list-template-ids:-1;}
@list l2:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3
{mso-list-id:1749423784;
mso-list-template-ids:-1;}
@list l3:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4
{mso-list-id:1823885486;
mso-list-template-ids:-1;}
@list l4:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level2
{mso-level-start-at:2;
mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5
{mso-list-id:1908414808;
mso-list-template-ids:-1;}
@list l5:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6
{mso-list-id:1942495209;
mso-list-template-ids:-1;}
@list l6:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l6:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7
{mso-list-id:1987775679;
mso-list-template-ids:-1;}
@list l7:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8
{mso-list-id:2076781012;
mso-list-template-ids:-1;}
@list l8:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l8:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Thanks Stephen, Dorothy, and Jeff for your responses.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">I think my original query has taken an inadvertent detour. It wasn’t my intent to question the well-established practice of using subfield $5 in conjunction with 655 fields to indicate that
a form/genre term applies to a specific copy. This is good and proper.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">The main thrust of my question is this: when we reach the day when our catalogs are batch converted from MARC to BIBFRAME, how can we apply a machine-actionable mechanism (without human mediation)
to ensure that the 655 headings are appropriately mapped to the pertinent items, instances,
<i>and </i>works?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Certainly the presence of a subfield $5 is already a machine-actionable clue that a given 655 heading should be matched with an item (though it’s regrettable that subfield $5 specifies an institution
instead of an actual copy – esp. when there’s more than one copy). But in current practice, there’s no explicit indication whether a term should be matched to an instance (manifestation) or a work. What’s the best way to plan for batch conversion processes
that correctly identify the proper domain for all 655 headings?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif"><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> DCRM-L <dcrm-l-bounces@lib.byu.edu> <b>On Behalf Of
</b>Jeff Barton<br>
<b>Sent:</b> Wednesday, May 27, 2020 10:05 PM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We code as $5 (NjP) 655 entries (and the accompanying 500 field notes) that refer to aspects at the item level – or “copy specific” in bibliographicese. These are generally unique to the copy at hand. The exception among the RBMS thesauri
would be terms from the Genre thesaurus terms, which apply more broadly to the work. I’d be interested in what others do in this regard too.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In that general connection, I’d also be interested to know how others are generally using sub-field divisions Form/Genre terms. I seem to recall from MidWinter that many were subdividing chronologically only by century. Is that an accurate
recollection? I’d also be interested in if/how others might be subdividing 655 terms geographically, and if so at what level”: city, state/province/county, or country? If geographic aspects (inscriptions or bookseller tickets, for instance) can be reasonably
identified with a location, that is.<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"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="color:black">Jeff Barton<o:p></o:p></span></p>
<p><span style="color:black">Cotsen Library Cataloger<o:p></o:p></span></p>
<p><span style="color:black">Rare Books & Special Collections Department<o:p></o:p></span></p>
<p><span style="color:black">Princeton University Library<o:p></o:p></span></p>
<p><span style="color:black">One Washington Rd.<o:p></o:p></span></p>
<p><span style="color:black">Princeton, NJ 08544 <o:p></o:p></span></p>
<p><span style="color:black"><a href="mailto:jpbarton@princeton.edu" target="_blank"><span style="color:black">jpbarton@princeton.edu</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><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 Young, Stephen <<a href="mailto:stephen.young@yale.edu">stephen.young@yale.edu</a>><br>
<b>Sent:</b> Wednesday, May 27, 2020 9:31:18 PM<br>
<b>To:</b> DCRM Users' Group <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">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.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Stephen Young<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="98%" align="center">
</div>
<div id="x_divRplyFwdMsg">
<p class="MsoNormal"><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 Auyong, Dorothy <<a href="mailto:dauyong@huntington.org">dauyong@huntington.org</a>><br>
<b>Sent:</b> Wednesday, May 27, 2020 7:40 PM<br>
<b>To:</b> DCRM Users' Group <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration</span> <o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xxmsonormal0">At the Huntington we only apply subfield 5 CSmH to item occurrence, not instance.<o:p></o:p></p>
<p class="xxmsonormal0"> <o:p></o:p></p>
<p class="xxmsonormal0"> <o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827">Dorothy Auyong</span></b><o:p></o:p></p>
<p class="xxmsonormal0"><span style="font-size:10.0pt;font-family:"Garamond",serif">Early Books and Codices Cataloging Manager</span><o:p></o:p></p>
<p class="xxmsonormal0"><span style="font-size:10.0pt;font-family:"Garamond",serif">Acquisitions, Cataloging & Metadata Services</span><o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827"> </span><o:p></o:p></p>
<p class="xxmsonormal0" style="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><o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827">Library, Art Museum, and Botanical Gardens
</span><o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827">1151 Oxford Road, San Marino, CA 91108</span><o:p></o:p></p>
<p class="xxmsonormal0" style="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%7Cfrancis.lapka%40yale.edu%7C5d4925d42b6846c6d98408d802ab9f6e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262283435350119&sdata=%2FD6aFarZljoOOL5ed%2Bi%2FOcUq%2BYUnc0sgUiIJqFAka0g%3D&reserved=0"><span lang="DE" style="color:#3E4827">huntington.org</span></a></span><o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827"> </span><o:p></o:p></p>
<p class="xxmsonormal0" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827">T 626-405-2188</span><o:p></o:p></p>
<p class="xxmsonormal0"><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><o:p></o:p></p>
<p class="xxmsonormal0"><span lang="DE" style="font-size:10.0pt;font-family:"Garamond",serif;color:#3E4827"> </span><o:p></o:p></p>
<p class="xxmsonormal0"><img border="0" width="55" height="55" style="width:.575in;height:.575in" id="x_x_Picture_x0020_6" src="cid:image001.png@01D634C9.E80857A0"><o:p></o:p></p>
<p class="xxmsonormal0"> <o:p></o:p></p>
<p class="xxmsonormal0"> <o:p></o:p></p>
<p class="xxmsonormal0"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="xxmsonormal0"><b>From:</b> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>>
<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 <<a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> Re: [DCRM-L] 655 field -- migration<o:p></o:p></p>
</div>
</div>
<p class="xxmsonormal0"> <o:p></o:p></p>
<div>
<p class="xxmsonormal0"><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><o:p></o:p></p>
</div>
<div>
<p class="xxmsonormal0"><span style="font-size:12.0pt;color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="xxmsonormal0"><span style="font-size:12.0pt;color:black">Stephen R. Young</span><o:p></o:p></p>
</div>
<div>
<p class="xxmsonormal0"><span style="font-size:12.0pt;color:black">Rare Book Catalog Librarian</span><o:p></o:p></p>
</div>
<div>
<p class="xxmsonormal0"><span style="font-size:12.0pt;color:black">Beinecke Rare Book and Manuscript Library</span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="x_x_divRplyFwdMsg">
<p class="xxmsonormal0"><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> <o:p></o:p></p>
<div>
<p class="xxmsonormal0"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif">Hi all.</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><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><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal" style="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. …<o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><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%7Cfrancis.lapka%40yale.edu%7C5d4925d42b6846c6d98408d802ab9f6e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262283435360114&sdata=qSzjUVTA6y%2BDJKN3%2FVO%2F5YEng2ykRQdQrAfWUWQSn4E%3D&reserved=0">
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%7Cfrancis.lapka%40yale.edu%7C5d4925d42b6846c6d98408d802ab9f6e%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637262283435370107&sdata=kFSzZ54FyC%2BnH7fiW%2BcP6JT2h53JOLp2PFC11H7V0nI%3D&reserved=0">
this LC specification</a>). </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif">Has your institution started to consider the issue? If so, what are your plans?
</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif">More questions:</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
<p class="xxxmsolistparagraph" style="margin-left:.5in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
<p class="xxxmsolistparagraph" style="margin-left:.5in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
</ol>
<p class="xxxmsolistparagraph" style="margin-left:1.0in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="4" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
</ol>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
<p class="xxxmsolistparagraph" style="margin-left:.5in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
</ol>
<p class="xxxmsolistparagraph" style="margin-left:1.0in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
</ol>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsolistparagraph" style="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><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="3" type="1">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
<p class="xxxmsonormal" style="margin-left:.5in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<ol style="margin-top:0in" start="2" type="1">
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="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><o:p></o:p></li></ol>
</ol>
<p class="xxxmsolistparagraph" style="margin-left:1.0in"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif">What are the other possibilities? What’s most likely to succeed?</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif">Francis</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Georgia Pro",serif"> </span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Calibri Light",sans-serif">Francis Lapka</span><o:p></o:p></p>
<p class="xxxmsonormal"><i><span style="font-family:"Calibri Light",sans-serif">Senior Catalogue Librarian</span></i><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Calibri Light",sans-serif">Department of Rare Books and Manuscripts</span><o:p></o:p></p>
<p class="xxxmsonormal"><span style="font-family:"Calibri Light",sans-serif">Yale Center for British Art</span><o:p></o:p></p>
<p class="xxxmsonormal"><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">francis.lapka@yale.edu</span></a><o:p></o:p></p>
<p class="xxxmsonormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>