<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:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"
xmlns:ns0="urn:schemas-microsoft-com:office:smarttags">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Californian FB";
panose-1:2 7 4 3 6 8 11 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Garamond;
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=3 color=blue face=Garamond><span
style='font-size:12.0pt;font-family:Garamond;color:blue'>Hi, Jane,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Garamond><span
style='font-size:12.0pt;font-family:Garamond;color:blue'> My guess is that
you hadn’t seen my response to this issue yet, where I reminded people
that “core” can indeed be entered by non-PCC libraries. But your
comment gave me pause and I decided to check the guidance in OCLC’s
Bibliographic Formats and Standards for entering a “4” (“core”)
in the FF Encoding level byte. Here it is:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Garamond><span
style='font-size:12.0pt;font-family:Garamond;color:blue'> “</span></font><strong><b><font
face="Times New Roman">Core-level</font></b></strong>. A record that is
less-than-full, but greater-than-minimal-level cataloging and that meets core
record standards for completeness. Any OCLC participant may enter a Core-level
record as long as Core-level input standards are followed. A Core-level record
that is entered by a library participating in PCC through BIBCO or CONSER will
contain an authentication code in field 042.”<o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>BTW, following “core-level input standards” here means
ensuring that it meets those standards for completeness NOT that they follow
the PCC requirement for authorized headings. Another way of putting this is
that it is the “pcc” in the 042 that is the guarantee that access
points are authorized, and not the Encoding Level.code relating to its
completeness.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> --Jain</span></font><font
color=blue face=Garamond><span style='font-family:Garamond;color:blue'><o:p></o:p></span></font></p>
<div>
<p style='margin-left:.5in'><font size=3 color=blue face="Californian FB"><span
style='font-size:12.0pt;font-family:"Californian FB";color:blue'>Jain Fletcher<br>
Principal Cataloger & Head, Technical Services Division <br>
Department of Special Collections <br>
Young Research Library - UCLA </span></font><font face="Californian FB"><span
style='font-family:"Californian FB"'><ns0:address w:insAuthor="Jain Fletcher"
w:insDate="2006-09-21T13:15:00Z" w:endInsAuthor="Jain Fletcher"
w:endInsDate="2006-09-21T13:15:00Z"><ns0:Street w:insAuthor="Jain Fletcher"
w:insDate="2006-09-21T13:15:00Z" w:endInsAuthor="Jain Fletcher"
w:endInsDate="2006-09-21T13:15:00Z"><st1:address w:st="on"><st1:Street w:st="on"><font
color=blue><span style='color:blue'>Box</span></font></st1:Street></ns0:Street></st1:address><font
color=blue><span style='color:blue'> 951575</span></font></ns0:address><font
color=blue><span style='color:blue'><br>
</span></font><ns0:place w:insAuthor="Jain Fletcher"
w:insDate="2006-09-21T13:15:00Z" w:endInsAuthor="Jain Fletcher"
w:endInsDate="2006-09-21T13:15:00Z"><ns0:City w:insAuthor="Jain Fletcher"
w:insDate="2006-09-21T13:15:00Z" w:endInsAuthor="Jain Fletcher"
w:endInsDate="2006-09-21T13:15:00Z"><font color=blue><span style='color:blue'>Los
Angeles</span></font></ns0:City><font color=blue><span style='color:blue'>, </span></font><ns0:State
w:insAuthor="Jain Fletcher" w:insDate="2006-09-21T13:15:00Z"
w:endInsAuthor="Jain Fletcher" w:endInsDate="2006-09-21T13:15:00Z"><font
color=blue><span style='color:blue'>CA</span></font></ns0:State><font
color=blue><span style='color:blue'> </span></font><ns0:PostalCode
w:insAuthor="Jain Fletcher" w:insDate="2006-09-21T13:15:00Z"
w:endInsAuthor="Jain Fletcher" w:endInsDate="2006-09-21T13:15:00Z"><font
color=blue><span style='color:blue'>90095-1575</span></font></ns0:PostalCode></ns0:place></span></font><font
color=blue><span style='color:blue'><o:p></o:p></span></font></p>
<p style='margin-left:.5in'><font size=3 color=blue face="Californian FB"><span
style='font-size:12.0pt;font-family:"Californian FB";color:blue'>v: (310)
794-4096<br>
f: (310) 206-1864<br>
e: </span></font><font size=2 color=blue><span style='font-size:10.0pt;
color:blue'><a href="mailto:jfletchr@library.ucla.edu"><font size=3
face="Californian FB"><span style='font-size:12.0pt;font-family:"Californian FB"'>jfletchr@library.ucla.edu</span></font></a>
</span></font><font color=blue><span style='color:blue'><o:p></o:p></span></font></p>
</div>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Jane Gillis<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, September 21, 2006
1:11 PM<br>
<b><span style='font-weight:bold'>To:</span></b> DCRM Revision Group List; DCRM
Revision Group List<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [DCRM-L] Introduction
comments</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I think that separating out pcc, whether core or full, from just full,
might be useful. Pcc records require that all access points be
authorized; full, non-pcc, records do not. Core records do require that
all access points be authorized, because core is only pcc. <br>
<br>
Jane<br>
<br>
At 03:30 PM 9/21/2006 Thursday-0400, Deborah J. Leslie wrote:<br>
<br>
<br>
<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><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><o:p></o:p></p>
</div>
</body>
</html>