<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: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;}
@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";}
@font-face
{font-family:"Open Sans Light";}
/* 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.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-style-priority:99;
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;
mso-style-priority:99;
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;
mso-style-priority:99;
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;
mso-style-priority:99;
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;
mso-style-priority:99;
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;
mso-style-priority:99;
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;
mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Georgia Pro",serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Georgia Pro",serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Georgia Pro",serif;
color:windowtext;}
span.EmailStyle30
{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:10884799;
mso-list-type:hybrid;
mso-list-template-ids:-1548964220 167305508 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:439644342;
mso-list-template-ids:-1;}
@list l1:level1
{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:1185559828;
mso-list-type:hybrid;
mso-list-template-ids:2025225312 -2118594498 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1309360324;
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-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:1400714325;
mso-list-template-ids:-1;}
@list l4:level1
{mso-level-start-at:2;
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:1749423784;
mso-list-template-ids:-1;}
@list l5:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
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:1823885486;
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-start-at:2;
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:1908414808;
mso-list-template-ids:1261738196;}
@list l7:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l7:level2
{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:1936672144;
mso-list-template-ids:1704908732;}
@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-start-at:2;
mso-level-number-format:alpha-lower;
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;}
@list l9
{mso-list-id:1942495209;
mso-list-template-ids:-1;}
@list l9:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l9:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10
{mso-list-id:1987775679;
mso-list-template-ids:-1;}
@list l10:level1
{mso-level-start-at:4;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l10:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11
{mso-list-id:2076781012;
mso-list-template-ids:1695578194;}
@list l11:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l11:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia Pro",serif">Thank you Paloma for your thoughtful reply.
<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">Full disclosure: though my questions are based in part on the anticipated headaches of a migration to BIBFRAME, they are also motivated by the desire to have records from my department (rare
books & mss) play well with records from the art collections at my museum (e.g., paintings, prints, and drawings) in our shared online catalog. In the museum catalog, we have facets for genre and work type, which correspond (roughly) to Work genre/form and
Instance genre/form. <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 ran several reports this morning to get a clearer summary of the 27,000+ 655 occurrences in our records, especially those used most often. A review of this data (at a skim) confirms earlier
hunches:<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">Terms from these thesauri are probably at least 90% aligned with work:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#4472C4;margin-left:0in;mso-list:l2 level1 lfo12">
<span style="font-family:"Georgia Pro",serif">fast<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#4472C4;margin-left:0in;mso-list:l2 level1 lfo12">
<span style="font-family:"Georgia Pro",serif">lcgft<o:p></o:p></span></li></ul>
<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">Terms from these thesauri are probably at least 90% aligned with instance:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:#4472C4;margin-left:0in;mso-list:l2 level1 lfo12">
<span style="font-family:"Georgia Pro",serif">gmgpc<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#4472C4;margin-left:0in;mso-list:l2 level1 lfo12">
<span style="font-family:"Georgia Pro",serif">rbpri<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#4472C4;margin-left:0in;mso-list:l2 level1 lfo12">
<span style="font-family:"Georgia Pro",serif">rbpub<o:p></o:p></span></li></ul>
<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">With consistent application of $5, terms from
<span style="color:#4472C4">rbbin </span>can be aligned with Instance or Item with a level of confidence near 100%.<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">With <span style="color:#4472C4">
rbprov</span>, terms should always align to Item.<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">Terms from these thesauri have the most ambiguous alignment, with some terms in real gray areas:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo12"><span style="font-family:"Georgia Pro",serif;color:#4472C4">aat</span><span style="font-family:"Georgia Pro",serif">: in my dataset, the alignment is about 60% Instance and 40% Work<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo12"><span style="font-family:"Georgia Pro",serif;color:#4472C4">rbgenr</span><span style="font-family:"Georgia Pro",serif">: in my dataset, the alignment is about 75% Work and 25% Instance.
<o:p></o:p></span></li></ul>
<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">Then there’s <span style="color:#4472C4">
rbpap</span>, which I’m inclined to map to bf:baseMaterial (or medium in my museum catalog) – rather than treat as a genre/form.<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">A question for RBMS Controlled Vocabularies editors: when the six existing RBMS thesauri are
<a href="http://rbms.info/cv-comments/2019/01/09/rbms-controlled-vocabulary-reorganization-update/">
integrated into a single cohesive thesaurus,</a> will the six source codes ($2) be replaced with a single value? If so – and if this change transpires while we are still in a MARC environment (at least partially) – will there be something in our MARC data to
indicate the facet to which a term belongs (works, objects, production, provenance, publishing)?<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:"Calibri Light",sans-serif">Francis Lapka<o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-family:"Calibri Light",sans-serif">Senior Catalogue Librarian<o:p></o:p></span></i></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Department of Rare Books and Manuscripts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri Light",sans-serif">Yale Center for British Art<o:p></o:p></span></p>
<p class="MsoNormal"><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><span style="font-family:"Calibri Light",sans-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>Graciani Picardo, Paloma<br>
<b>Sent:</b> Friday, May 29, 2020 6:29 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"><span style="color:#1F497D">Hi Francis,<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">at the Ransom Center we have started kind of similar conversations but from the angle of original BIBFRAME metadata creation. As members of the LD4P2 cohort (and in the context of the current shelter-at-home
situation) we are spending a good chunk of our time "re-cataloging" one of our collections in the RDF based cataloging platform developed for the project.
<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">To your first question, we early on decided on assigning the proper genre/form term to the proper BF entity, and that would be our expectation for a programmatic conversion. That said, while the parsing is obvious
for what goes to the item, it might not be so obvious sometimes (even for human eyes!) for what goes to the Work or Instance, since it depends on the nature of the work/expression.
<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">To your second question, even though we haven't discussed this yet at the center, I would always feel more inclined towards Method B (adjust 655 to potential mapping). In my experience, you might lose some crucial
data post migration that could have been very helpful for data remediation decisions. That said, your question made me curious about the likeability of approach A working for us (leaving the 655 unchanged), so I had a quick look at our use of the 655 field
throughout time. Of the 34,500 occurrences of the field 655 in our catalog, there are around 50 different values on the $2, reduced to 29 after some quick OpenRefine magic. More than half are "rbgenr" terms, with "fast", "aat", "rbbin", "gsafd" and "lcgft"
being the only ones with more than a thousand occurrences. Honestly, the only ones of these I would feel confident to assign programmatically based on source are "rbbin" and "gsafd". On the other hand, our use of $5 is very recent, so that would not work for
our legacy data either. As per a conversion based on pattern recognition, well, we might have up to seven different variations for a given vocabulary term (typos, plural/singular, etc..), so that approach will have to be preceded by some heavy pre-migration
data clean up or be extremely complex.<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">The idea of implementing a new subfield to indicate corresponding BF entities sounds very interesting and I would like to hear more about logistics or drawbacks for that approach. For instance, how would that
new field impact data display in our current ILS/LSPs (assuming that those data manipulations would get started well in advance before migration to BIBFRAME)? I also would be interested in further discussions around the challenge of associating any copy specific
access point (not just genre/form but former owners, annotators, inscribers, etc..) to the actual item when there are many items to one manifestation description.
<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">Anyway, I better stop before I get too much into the weeds, but hope any of this helped. I am excited to see this conversation getting started and would also love to hear use cases and thoughts from other institutions!
<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">Happy Friday!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Paloma<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#404040">Paloma Graciani Picardo|
</span><span style="font-size:9.0pt;font-family:"Open Sans Light";color:gray">she, her, hers</span><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#404040"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#404040">Metadata Librarian and Head, Printed & Published Media</span></i><b><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#404040"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#404040">Harry Ransom Center | The University of Texas at Austin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Open Sans Light";color:#1F497D"><a href="https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hrc.utexas.edu%2F&data=02%7C01%7Cfrancis.lapka%40yale.edu%7C51ba68f0b4434566e62d08d8041fc04f%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637263881722536629&sdata=JnMFvtL3nVouqR4esunb5xduekJ9jGZmhjJLBzjuCBk%3D&reserved=0"><span style="color:#0563C1">www.hrc.utexas.edu</span></a>
<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><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>Lapka, Francis<br>
<b>Sent:</b> Thursday, May 28, 2020 7:28 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="MsoNormal"><o:p> </o:p></p>
<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 <<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>>
<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 <<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="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%7C51ba68f0b4434566e62d08d8041fc04f%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637263881722536629&sdata=UURPFJw2nWK599jp9HxNPXH3slvPANww4SfRr6uKtAY%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:.5729in;height:.5729in" id="x_x_Picture_x0020_6" src="cid:image002.png@01D63821.FB0B8240"><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%7C51ba68f0b4434566e62d08d8041fc04f%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637263881722546625&sdata=9vRs3WztTpJw04%2FfkOOxOlqdIP1PPOjxESTfssjJTsM%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%7C51ba68f0b4434566e62d08d8041fc04f%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C1%7C637263881722546625&sdata=rdo8YHWmVgR7geHMmHcS9ZDNEXRPBraAPP2BaajzqsE%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="1" type="1">
<li class="MsoNormal" style="mso-list:l7 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="2" type="1">
<li class="MsoNormal" style="mso-list:l11 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:l1 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:l10 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:l9 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:l3 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:l4 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="4" type="1">
<li class="MsoNormal" style="mso-list:l8 level1 lfo10"><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:l5 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>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="1" cellspacing="3" cellpadding="0" style="background:#FDFAE7;border:solid #FCD146 1.0pt;border-left:solid #FCD146 6.0pt">
<tbody>
<tr>
<td style="border:none;padding:6.0pt 6.0pt 6.0pt 12.0pt">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">This message is from an external sender.
<a href="https://ut.service-now.com/sp?id=kb_article&number=KB0011401"><span style="text-decoration:none">Learn more about why this matters.</span></a>
<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
</div>
</body>
</html>