<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 10 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Palatino Linotype";
panose-1:2 4 5 2 5 5 5 3 3 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 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";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
text-align:center;
page-break-after:avoid;
font-size:16.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.MsoEnvelopeAddress, li.MsoEnvelopeAddress, div.MsoEnvelopeAddress
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:2.0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Arial Unicode MS";}
p.MsoEnvelopeReturn, li.MsoEnvelopeReturn, div.MsoEnvelopeReturn
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Arial Unicode MS";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Tablenames, li.Tablenames, div.Tablenames
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.3in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman";}
p.P0Char, li.P0Char, div.P0Char
{margin:0in;
margin-bottom:.0001pt;
font-size:15.0pt;
font-family:"Times New Roman";
font-variant:small-caps;
font-weight:bold;}
p.Paragraphnormal, li.Paragraphnormal, div.Paragraphnormal
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.normalbold
{font-weight:bold;}
p.Paragraphnormalbold, li.Paragraphnormalbold, div.Paragraphnormalbold
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.StyleParagraphnormalNotBold, li.StyleParagraphnormalNotBold, div.StyleParagraphnormalNotBold
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Heading2, li.Heading2, div.Heading2
{margin-top:.25in;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:13.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.Heading1, li.Heading1, div.Heading1
{margin:0in;
margin-bottom:.0001pt;
font-size:15.0pt;
font-family:"Times New Roman";
font-variant:small-caps;
font-weight:bold;}
p.Normalparagraph25indent, li.Normalparagraph25indent, div.Normalparagraph25indent
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Header2, li.Header2, div.Header2
{margin-top:.25in;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:13.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.Alternativeruletext, li.Alternativeruletext, div.Alternativeruletext
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Times New Roman";}
p.Normalparagraphbold, li.Normalparagraphbold, div.Normalparagraphbold
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
font-weight:bold;}
span.12ptitalic
{font-family:"Palatino Linotype";
font-style:italic;}
span.12pt
{font-family:"Palatino Linotype";
font-style:italic;}
span.normalitalic
{font-family:"Palatino Linotype";
font-style:italic;}
p.Header2smcaps, li.Header2smcaps, div.Header2smcaps
{margin-top:.25in;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:13.0pt;
font-family:"Times New Roman";
font-variant:small-caps;
font-weight:bold;}
span.EmailStyle36
{font-family:"Arial Unicode MS";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face="Arial Unicode MS"><span
style='font-size:11.0pt;font-family:"Arial Unicode MS";color:blue'>Thanks to
Jain for the clarification on PCC full. I am on the side of downplaying the
BIBCO aspect, and so would support Manon</span></font><font size=2 color=blue><span
style='font-size:11.0pt;color:blue'>’</span></font><font size=2
color=blue face="Arial Unicode MS"><span style='font-size:11.0pt;font-family:
"Arial Unicode MS";color:blue'>s idea of putting this information in a footnote
for both full and core. D.</span></font></p>
<div>
<p><font size=1 color=blue face="Arial Unicode MS"><span style='font-size:7.5pt;
font-family:"Arial Unicode MS";color:blue'>__________________________________________</span></font><font
color=blue><span style='color:blue'> <br>
</span></font><font size=1 color=blue face="Arial Unicode MS"><span
style='font-size:7.5pt;font-family:"Arial Unicode MS";color:blue'>Deborah J.
Leslie</span></font><font size=1 color=blue face="Arial Unicode MS"><span
style='font-size:7.5pt;font-family:"Arial Unicode MS";color:blue'>, M.A.,
M.L.S.<br>
Chair, RBMS Bibliographic Standards Committee<br>
<a href="http://www.folger.edu/bsc/index.html">http://www.folger.edu/bsc/index.html</a><br>
Head of Cataloging, Folger Shakespeare Library<br>
201 East Capitol St., S.E., Washington, D.C. 20003</span></font><font
color=blue><span style='color:blue'> <br>
</span></font><font size=1 color=blue face="Arial Unicode MS"><span
style='font-size:7.5pt;font-family:"Arial Unicode MS";color:blue'>djleslie@folger.edu
|| 202.675-0369 ||</span></font><font color=blue><span style='color:blue'> </span></font><font
size=1 color=blue face="Arial Unicode MS"><span style='font-size:7.5pt;
font-family:"Arial Unicode MS";color:blue'><a href="http://www.folger.ed">http://www.folger.ed</a>u</span></font><font
color=blue><span style='color:blue'> </span></font></p>
</div>
<p class=MsoNormal style='margin-left:.5in'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'>-----Original Message-----<br>
<b><span style='font-weight:bold'>From:</span></b> dcrm-l-bounces@lib.byu.edu
[mailto:dcrm-l-bounces@lib.byu.edu] <b><span style='font-weight:bold'>On Behalf
Of </span></b>Manon Theroux<br>
<b><span style='font-weight:bold'>Sent:</span></b> 21 September 2006 17:30<br>
<b><span style='font-weight:bold'>To:</span></b> </span></font><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>DCRM</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Revision
Group List</span></font><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'><br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>DCRM</span></font><font
size=2 face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>-L]
Introduction comments</span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>It's true that core started out as a PCC endeavor,
unlike full, but since the current reality is that any library can create a
core-level record, just as any library can create a full-level record, I think
it makes sense to account for all 4 variations of these two levels in some way
(full, core, PCC full, PCC core). Especially if it might help to eliminate
confusion about options! If we wanted to downplay the BIBCO aspect in the Intro
sections on core and full, we could put the sentence(s) about the BIBCO
authority record requirements in footnotes. I think Joe was arguing along these
lines at one point, wasn't he?<br>
<br>
-Manon<br>
<br>
<br>
At 03:30 PM 9/21/2006, you wrote:<br>
<br>
<br>
</span></font></p>
<p class=MsoNormal style='margin-right:0in;margin-bottom:12.0pt;margin-left:
.5in'><font size=3 face="Arial Unicode MS"><span style='font-size:12.0pt;
font-family:"Arial Unicode MS"'>Possibly because the definition of core-level
cataloging is a</span></font> <font face="Arial Unicode MS"><span
style='font-family:"Arial Unicode MS"'>BIBCO endeavor, is it not, whereas
full-level cataloging did not originate with PCC. Therefore, mention of</span></font>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>BIBCO
requirements make sense in the section on</span></font> <font color=blue
face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS";color:blue'>core</span></font><font
face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>, but not
necessarily in the section on</span></font> <font face="Arial Unicode MS"><span
style='font-family:"Arial Unicode MS"'>full. <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>__________________________________________<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Deborah
J. Leslie, M.A., M.L.S.<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Chair,
RBMS Bibliographic Standards Committee<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'><a
href="http://www.folger.edu/bsc/index.html">http://www.folger.edu/bsc/index.html</a><br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Head
of Cataloging, Folger Shakespeare Library<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>201
East Capitol St., S.E., Washington, D.C. 20003<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>djleslie@folger.edu
|| 202.675-0369 || <a href="http://www.folger.edu">http://www.folger.edu</a>
<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>-----Original
Message-----<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>From:
dcrm-l-bounces@lib.byu.edu [<a href="mailto:dcrm-l-bounces@lib.byu.edu">
mailto:dcrm-l-bounces@lib.byu.edu</a>] On Behalf Of Manon Theroux<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Sent:
21 September 2006 15:26<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>To:
DCRM Revision Group List<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Subject:
RE: [DCRM-L] Introduction comments<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>You're
right, Nina, at least for PCC full-level <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>records.
The BIBCO Manual seems pretty clear <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>about
it. I'm so glad you spoke up.<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>So,
in the full-level section of the Intro, we need to strike:<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>"The
name headings need not be established using <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>authority
records, although full authority work <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>will
generally result in greater consistency of headings and improved access."<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>And
I suggest we include the following somewhere in that paragraph:<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>"If
an institution is a BIBCO participant, <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>contributing
full-level records as part of the <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Program
for Cooperative Cataloging (PCC), all <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>headings
must be established in the LC/NACO and LC/SACO Authority Files."<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>to
parallel the text in the core-level section.<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Now
I wonder what led me/us to think the way we <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>did.
This text has been in the Pre-Cataloging <br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>Decisions
section for a long time!<br>
</span></font><br>
<font face="Arial Unicode MS"><span style='font-family:"Arial Unicode MS"'>-Manon<br>
<br>
</span></font></p>
</div>
</body>
</html>