<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Bookman Old Style";
panose-1:2 5 6 4 5 5 5 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Bookman Old Style","serif";
color:black;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Hello all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Karen Nipps mentioned last week that we at Harvard are waiting for responses from OCLC. I am sending a slightly edited version of the email that I sent asking for clarification
on what I understand to be the available documentation, particularly the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www5.oclc.org_downloads_webinars_InstitutionRecordswebinar-5FQA-5Fsummary.pdf&d=BQMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=3nc7uBjJc9SXjstUJb4MBv_VwPSQWN0xkOiqaALNXBA&m=LQ8ElOsrT9QGfqO0l17Yx6edIpe3yBCFVbtkMeDAzYo&s=KwC0sM9fXU2WuQR-ChvE-6PBPqm83WVB23w45HdfDZQ&e=">
transcript of the Q & A from the two webinars</a>, as it seems relevant to various parts of the current discussion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Honor<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Questions/comments for OCLC:
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Question 21 says that 541 and 561 fields are not included in LBD, though OCLC will consider them in the future. To be quite frank, I’m feeling as though I’ve really missed
something important about the purpose of the LBD if these fields are not included—they are, after all, defined as copy specific. This is additionally frustrating because the illustrative sticky notes on the
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oclc.org_content_dam_support_documentation_cataloging_Working-5Fwith-5FLBDs.pdf&d=BQMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=3nc7uBjJc9SXjstUJb4MBv_VwPSQWN0xkOiqaALNXBA&m=LQ8ElOsrT9QGfqO0l17Yx6edIpe3yBCFVbtkMeDAzYo&s=iC5c8j-VCuJe4QWy_fY2JYVPlo8Z9KHveojtOmYSZAI&e=">
Working with LBD</a> documentation are for exactly the kind of information that is recorded in these fields.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">I am also not really persuaded that provenance, ownership and custody information rightfully belong in the master record (question 26) of published materials. For example,
OCLC #191248862, which has provenance and binding descriptions from two separate libraries, but 29 other holdings (several of the IRs contain varying degrees of copy specific info, including provenance)—I can imagine what this would look like if even a third
of the holding libraries had individual 561s, but I am having a harder time imagining how this could usefully be presented to users on the front end (never mind catalogers).</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">On a related note, #191248862 is also an example of 655s with $5, contra the response in question 38. This is a great example of a mix of copy specific and as issued 655s
(though the as issued binding headings may not still be true for all holdings), but also of copy specific 655s that may be applicable to more than one copy (Authors' presentation inscriptions (Provenance)), yet the $5 is defined as not repeatable, so would
require an additional field for each holding library if this information were to be retained in the master. Given that the RBMS controlled vocabularies are a mix of terms that can only be copy specific, those that are always true of the resource and those
that can be either, I think that application guidelines are probably desirable.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Bookman Old Style","serif";color:black">Other fields that I consider to be either per se or potentially copy specific and therefore should be valid LBD are the 506, 562, 563 and 583.
</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Bookman Old Style","serif";color:black">Honor Moody<br>
Cataloger<br>
Schlesinger Library<br>
Radcliffe Institute for Advanced Study<br>
3 James Street<br>
Cambridge, MA 02138<br>
Tel.: (617) 495-4223<br>
Email: hmoody@radcliffe.harvard.edu</span><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:black">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Bookman Old Style","serif";color:black"><o:p> </o:p></span></p>
</div>
</body>
</html>