<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 12 (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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
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.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Bob,<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'>I share your concern re: the new
BIBCO standard record requirement for the 050. We haven’t assigned
classification numbers to any of our Rare Materials here at the Huntington
since before I was born. To create full-blown LC call numbers for all of our
original cataloging would require a fairly serious investment in workflow and
re-training. I admit to being rusty beyond belief in the skill.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Dorothy Auyong</span><span style='font-size:12.0pt;font-family:
"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Principal Rare Book Cataloger</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>Huntington Library</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'><a href="mailto:dauyong@huntington.org">dauyong@huntington.org</a></span><span
style='color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Robert
Maxwell<br>
<b>Sent:</b> Wednesday, October 14, 2009 6:03 PM<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> [DCRM-L] BIBCO Standard Record<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>As most of you know, the BIBCO standard record has now been
approved (see message and link below). One of my catalogers points out
that this seems to blast out of the water DCRM(B) Core, since core is now
obsolete. The main problem with this is that in DCRM(B) Core 050 was not
required; this was the main reason we used the core here. 050 is required in
the new BIBCO Standard Record. I know many of us commented on this specific
issue to the PCC Policy Committee, but our comments appear to have fallen on
deaf ears. Is anyone involved in this standard on DCRM-L? If so, could you
comment?<o:p></o:p></p>
<p class=MsoNormal><br>
Would the chair of Bibliographic Standards care to request clarification and/or
protest? This change will greatly diminish our BYU PCC contributions in areas
where we use idiosyncratic call number schemes and do not want to take the time
to create full blown LC call numbers for 050 (e.g. series of pamphlets). (Until
we get clarification on this issue we intend to continue to code DCRM(B) PCC
records without 050 as core.)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=Default><span style='font-family:"Calibri","sans-serif"'>These are the
members of the committee that created the BIBCO Standard Record policy: <o:p></o:p></span></p>
<p class=Default><span style='font-size:11.5pt;font-family:"Calibri","sans-serif"'>Members:
Magda El-Sherbini, Ohio State University, Rebecca Malek-Wiley, Tulane
University, Caroline Miller, University of California, Los Angeles, Louise
Ratliff, University of California, Los Angeles, Carolyn Sturtevant, Coop,
Library of Congress <o:p></o:p></span></p>
<p class=Default><span style='font-size:11.5pt;font-family:"Calibri","sans-serif"'>Iris
Wolley, Columbia University (coordinator) <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.5pt'>Liaisons: Joe Kiegel,
Standing Committee on Standards, University of Washington, Rebecca Lubas,
Standing Committee on Automation, University of New Mexico, Bob Wolverton,
Standing Committee on Training, Mississippi State University</span><o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Bob<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Robert L. Maxwell<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Special Collections and Ancient Languages
Catalog Librarian<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Genre/Form Authorities Librarian<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>6728 Harold B. Lee Library<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Brigham Young University<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>Provo, UT 84602<o:p></o:p></span></p>
<p class=MsoNormal style='text-autospace:none'><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'>(801)422-5568 <o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>-----Original Message-----<o:p></o:p></p>
<p class=MsoPlainText>From: Program for Cooperative Cataloging [mailto:PCCLIST@loc.gov]
On Behalf Of Antony Robert David Franks<o:p></o:p></p>
<p class=MsoPlainText>Sent: Wednesday, October 07, 2009 2:01 PM<o:p></o:p></p>
<p class=MsoPlainText>To: PCCLIST@LISTSERV.LOC.GOV<o:p></o:p></p>
<p class=MsoPlainText>Subject: BIBCO Standard Record Approved<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The PCC Policy Committee (PoCo) has approved the creation
of a BIBCO<o:p></o:p></p>
<p class=MsoPlainText>Standard Record (BSR) for monographic
materials. The requirements for<o:p></o:p></p>
<p class=MsoPlainText>the BSR for monographs were laid out in the final report
of the Task Group on BIBCO Standard Record Requirements, available from the PCC
Website at: <a href="http://www.loc.gov/catdir/pcc/bibco/BSR-Final-Report.pdf">http://www.loc.gov/catdir/pcc/bibco/BSR-Final-Report.pdf</a>
<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText> <o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>The Policy Committee will be discussing the details of
BSR implementation at its upcoming meeting (November 5 and 6, 2009) at the
Library of Congress. The PoCo will also consider the process of creating
BSR<o:p></o:p></p>
<p class=MsoPlainText>guidelines for other formats. Details will be
forthcoming after the<o:p></o:p></p>
<p class=MsoPlainText>November meetings in Washington.<o:p></o:p></p>
<p class=MsoPlainText><o:p> </o:p></p>
<p class=MsoPlainText>Anthony R.D. Franks<o:p></o:p></p>
<p class=MsoPlainText>Head, Cooperative Programs Section<o:p></o:p></p>
<p class=MsoPlainText>Cooperative and Instructional Programs Division Library of
Congress<o:p></o:p></p>
<p class=MsoPlainText>202-707-2822 (voice)<o:p></o:p></p>
<p class=MsoPlainText>202-252-2082 (fax)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>