<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR><!--[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="place"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="State"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"></o:SmartTagType><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
        BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
        font-family: Book Antiqua;
}
@font-face {
        font-family: Tahoma;
}
@font-face {
        font-family: Palatino Linotype;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: blue; TEXT-DECORATION: underline
}
P.MsoPlainText {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
LI.MsoPlainText {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
DIV.MsoPlainText {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"
}
SPAN.EmailStyle18 {
        COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=blue link=blue>
<DIV dir=ltr align=left><SPAN class=500581823-01032006><FONT face=Arial
size=2>Since we're discussing how people use core, the only reason I sometimes
code a DCRB record core is if I do not want to supply a call number, i.e., if
the record is for a pamphlet or broadside and we're just going to put it in an
accession number arrangement here. Everything else about the record is full, but
the availability of DCRB Core allows me to contribute the record as a PCC Bibco
record without adding a call number. I don't do this very often (if the call
number is very simple to construct I'll often add one anyway even though we're
not going to use it at BYU and then I code the record as PCC full). So when I
use core I'm not particularly thinking of how I might pare down the record; it
just allows me to contribute a record without including one of the required
fields for book core (the call number).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=500581823-01032006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=500581823-01032006><FONT face=Arial
size=2>Bob</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Robert L. Maxwell<BR>Special Collections and Ancient Languages
Catalog Librarian<BR>Genre/Form Authorities Librarian<BR>6728 Harold B. Lee
Library<BR>Brigham Young University<BR>Provo, UT 84602<BR>(801)422-5568
</FONT></P>
<DIV> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> dcrm-l-bounces@lib.byu.edu
[mailto:dcrm-l-bounces@lib.byu.edu] <B>On Behalf Of </B>Deborah J.
Leslie<BR><B>Sent:</B> Wednesday, March 01, 2006 3:10 PM<BR><B>To:</B> DCRM
Revision Group List<BR><B>Subject:</B> RE: [DCRM-L] DCRB
Core<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=169330722-01032006><FONT color=#0000ff>Thanks, Elaine. It was
in the back of my mind that most of the DCRB and DCRM(B) notes are
optional, as you say, so the distinction between full and core may be hard if
not impossible to pin down. </FONT></SPAN></DIV>
<DIV><SPAN class=169330722-01032006></SPAN><SPAN
class=169330722-01032006></SPAN><FONT color=#0000ff></FONT> </DIV>
<DIV><SPAN
style="FONT-SIZE: 9pt; FONT-FAMILY: 'Palatino Linotype'">________________________<o:p></o:p></SPAN></DIV>
<DIV class=Section1>
<P class=MsoAutoSig><SPAN
style="FONT-SIZE: 9pt; FONT-FAMILY: 'Palatino Linotype'">Deborah J.
Leslie<BR></SPAN><SPAN
style="FONT-SIZE: 9pt; FONT-FAMILY: 'Palatino Linotype'">Folger
Library<BR></SPAN><SPAN
style="FONT-SIZE: 9pt; FONT-FAMILY: 'Palatino Linotype'"><A
href="mailto:djleslie@folger.edu">djleslie@folger.edu</A><BR></SPAN><SPAN
style="FONT-SIZE: 9pt; FONT-FAMILY: 'Palatino Linotype'"><o:p> </o:p></SPAN></P></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma>-----Original Message-----<BR><B>From:</B>
dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu] <B>On Behalf
Of </B>Shiner, Elaine<BR><B>Sent:</B> Wednesday, 01 March, 2006
16:56<BR><B>To:</B> DCRM Revision Group List<BR><B>Subject:</B> RE: [DCRM-L]
DCRB Core<BR><BR></FONT></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I haven’t read
Windy’s study yet, but I’d like to comment about the fact that a lot of
records coded “core” actually meet standards for full level. I’ve
experimented with using the DCRB core standard for some of my books, with
the addition of a signature statement. When I do this, I often start
out coding for core, with the best of intentions, but end up adding a note
or two I hadn’t planned on (because it’s easy, or because I’m lacking in the
requisite self-discipline), and then I find myself wondering whether I’ve
reached full level. It seems easy to know when you’ve fulfilled the
requirements for core, but somehow harder to recognize when you’ve passed
beyond core to full level, probably because the requirements for full-level
vary, depending on the book in hand. I actually find this to be a
problem with using the DCRB core standard. Maybe I just need to review the
books core standards, and keep more clearly in mind all the ways they differ
from full level. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Further,
eliminating optional notes in the DCRB (or DCRM(B)) standard should not
technically affect whether cataloging is full-level or not, should it?
Yet eliminating optional notes is one of the main recommendations of the
DCRB core standard. I wonder how many rare book catalogers may code a
record “4” as a way of letting colleagues know that options have not been
taken; that is, the record may be technically full level, but falls
far short of the treatment they would like to give the book. That’s
not what the DCRB standard is for, yet I myself feel tempted to use it that
way.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'">Elaine Shiner, Head
Cataloguer<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'">William Andrews Clark
Memorial Library<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'">Email: <A
href="mailto:shiner@humnet.ucla.edu">shiner@humnet.ucla.edu</A><o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'">Phone:
323-731-8529<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT face="Book Antiqua"><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Book Antiqua'">Fax:
323-731-8617</SPAN></FONT></P></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>