<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:"Palatino Linotype";
        panose-1:2 4 5 2 5 5 5 3 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
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;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Palatino Linotype","serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
.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 bgcolor=white lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'>I'd say that the <i>real</i> DCRM intention was to give considerable
flexibility to what constitutes a &quot;full&quot; DCRM record, originating in an
attempt to head off the growing concern of library directors about their hidden
collections. In fact, some of you may remember the hurriedly gathered group of
BSC types who'd attended the LC Hidden Collections conference in September 2003,
sitting on the grass outside the Adams Building with our sandwiches to discuss
exactly this. <o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'>BDRB and DCRB had this flexibility as well, but it wasn't
necessarily apparent. We tried to write it in large letters in DCRM B and S&#8212;that's
what Introduction section X is all about. I encourage my fellow catalogers to code
dcrm and EL=I as long as they've included all the required and the required-if-applicable
elements, and followed DCRM in formulating them. Note well: in DCRM proper, most
notes and headings are optional. &nbsp;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'>As for DCRM(G), perhaps you can embrace this concept of a range
of acceptable levels of cataloging depth by creating an AppendixC-like chart,
giving element-by-element floor requirements for full-level DCRM(G) records. &nbsp;&nbsp;<o:p></o:p></span></p>

<p class=MsoNormal><span style='font-family:"Palatino Linotype","serif";
color:#1F497D'><o:p>&nbsp;</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";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> dcrm-l-bounces@lib.byu.edu
[mailto:dcrm-l-bounces@lib.byu.edu] <b>On Behalf Of </b>Erin Blake<br>
<b>Sent:</b> Tuesday, 30 November, 2010 15:03<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> RE: [DCRM-L] Going from Core-Level to BIBCO Standard Record in DCRM(G)<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<div>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>&lt;...&gt;</span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'><br>
>From what I can tell, the DCRM intention is that guidance come in three sizes:
extra-small (i.e., minimal-level, using Appendix D as the floor), small (i.e.,
more than minimal but less than full, using Appendix C as the floor), and
regular (full level, using the whole manual and its requirements as the floor).
<br>
<br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#1F497D'>&lt;...&gt;</span><span style='font-size:10.0pt;font-family:
"Arial","sans-serif"'>&nbsp;&nbsp;</span><o:p></o:p></p>

</div>

<div>

<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>&nbsp;&nbsp;
<o:p></o:p></span></p>

</div>

</div>

</body>

</html>