<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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Georgia","serif";
font-variant:normal !important;
color:#1F497D;
text-transform:none;
text-shadow:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
span.special-letter
{mso-style-name:special-letter;}
span.italic
{mso-style-name:italic;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D">Not a bad idea, Allison, although “that is”
<b><i>is</i></b> RDA’s language for corrections. It’s curious to me that RDA has a mechanism for correcting misleading numbering within the element, but not for misleading dates.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal">3.4.5.5 Misleading Numbering<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If the numbering on the last page, leaf, or column of a sequence does not represent the total number of pages, leaves, or columns in that sequence, let it stand uncorrected unless it gives a completely false impression of the extent of
the resource (e.g., when only alternate pages are numbered or when the number on the last page, leaf, or column of the sequence is misprinted).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When correcting misleading numbering, record the numbering as it appears on the last page or leaf followed by that is and the correct number.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">EXAMPLE<o:p></o:p></p>
<p class="MsoNormal">48, that is, 96 pages<o:p></o:p></p>
<p class="MsoNormal">329, that is, 392 pages<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#215868">Deborah J. Leslie, M.A., M.L.S. | Head of Cataloging, Folger Shakespeare Library<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:#215868"><a href="mailto:djleslie@folger.edu"><span style="color:#215868;text-decoration:none">djleslie@folger.edu</span></a> | 202.675-0369 | www.folger.edu</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia","serif";color:#1F497D"><o:p> </o:p></span></p>
<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>Allison Jai O'Dell<br>
<b>Sent:</b> Saturday, 04 August, 2012 11:39<br>
<b>To:</b> DCRM Revision Group List<br>
<b>Subject:</b> Re: [DCRM-L] RDA-acceptable: Indicating misprints<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">I like your inclination here, Deborah.
<br>
<br>
But why not stick with the existing RDA language? Instead of "[that is, ...]" use "[should read ...]" immediately following the misprint, or perhaps, "[Title should read: ....]" at the end of the title field?<br>
<br>
<br>
<br>
Best,<br>
Allison<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
</div>
</body>
</html>