<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Palatino Linotype","serif";
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
p.Default, li.Default, div.Default
{mso-style-name:Default;
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Cambria","serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'>Dear all,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'>The task force Erin mentioned appears in this way in the Bib Standards minutes for Annual 2011 (from <a href="http://rbms.info/committees/minutes/minutes.shtml#bibliographic_standards">http://rbms.info/committees/minutes/minutes.shtml#bibliographic_standards</a>) :<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><p class=Default><b><span style='font-size:11.5pt'>16. Action plan (All-but-inevitable advent of RDA and its impact on DCRM) </span></b><span style='font-size:11.5pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.5pt'>Skuce called for the formation of a group to formulate recommendations regarding RDA’s impact on DCRM. Initial volunteers for the task force were Deborah J. Leslie and Catherine Uecker; John Attig was named as another potential member. Fletcher recommended that since the RDA guidelines are going to be rewritten for clarity rather than content, the task force should synthesize the existing directions using their own wording rather than quoting directly from the existing guidelines. Leslie pointed out that since the national libraries will be adopting RDA in a modified way we don’t want to get ahead of practice, but we can begin establishing general principles and wait on specific recommendations. Barrett mentioned that OLAC is making suggestions regarding the rewording of problematic areas; perhaps BSC could also contribute suggestions for problem areas related to rare materials.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.5pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'>You can be sure that any changes in DCRM practice won't be formulated or implemented without wide discussion. Speaking for myself and not as a member of the Task Force, I expect that actual revision of DCRM(B) to bring it in line with RDA instead of AACR2 is still several years down the road. The RDA dust has to settle first in the larger cataloging community, and the rare materials cataloging community will need plenty of time to assess the fallout and make decisions that best serve the users of our materials and the users of our catalogs. The task force just formed will not produce that kind of thorough assessment, but rather the approach that we want to take now that RDA in some form will be implemented by the national libraries. (At least that's what I'm thinking—we don't have a charge yet.) <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:#0070C0'>Deborah J. Leslie, M.A., M.L.S. | Head of Cataloging, Folger Shakespeare Library | 201 East Capitol St., S.E. | Washington, D.C. 20003<br><a href="mailto:djleslie@folger.edu"><span style='color:#0070C0'>djleslie@folger.edu</span></a></span><span style='color:#1F497D'> </span><span style='font-size:9.0pt;color:#0070C0'>| 202.675-0369 | <a href="http://www.folger.edu/"><span style='color:#0070C0'>http://www.folger.edu</span></a> <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Palatino Linotype","serif";color:#1F497D'><o:p> </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"'>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>Linda, Oksana<br><b>Sent:</b> Thursday, 04 August, 2011 11:42<br><b>To:</b> DCRM Revision Group List<br><b>Subject:</b> Re: [DCRM-L] Eliminating an RDA option in DCRM(G) draft: want to allow "i.e." and "[sic]"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>Dear Erin:<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>I would like </span><span style='font-family:"Times New Roman","serif"'>to add my support for retaining the brackets in the physical description area.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>The usage of "i.e." and "[sic]" is extremely important, I can’t even imagine loosing it. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif"'>Thank you,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Times New Roman","serif"'>Oksana. <span style='color:black'><o:p></o:p></span></span></p><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Consolas;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>______________________<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>Oksana Katerine Linda<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>University of Michigan<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'>William L. Clements Library<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Times New Roman","serif";color:black'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:black'><o:p> </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"'>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>Erin Blake<br><b>Sent:</b> Wednesday, August 03, 2011 9:32 PM<br><b>To:</b> dcrm-l@lib.byu.edu<br><b>Subject:</b> [DCRM-L] Eliminating an RDA option in DCRM(G) draft: want to allow "i.e." and "[sic]"<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As you may know, the DCRM(G) draft incorporates some boxed "RDA alternatives" in cases where standard RDA convention differs from AACR2 (e.g. "RDA alternative: Use 'diameter' instead of the abbreviation 'diam.'") and there are no rare materials or graphic materials reasons to differ (as suggested by Barbara Tillett and others, and approved in principle by the RBMS Bibliographic Standards Committee, in order for DCRM(G) to be a transitional manual).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the draft reviewed for the public hearing, we included the RDA alternative "Do not follow inaccuracies with '[sic]' or 'i.e.' and the correction in square brackets. Instead, make a note correcting the inaccuracy (RDA 1.7.9)." HOWEVER, further work has convinced us we DO need "[sic]" and "i.e." in transcriptions, for various reasons, including:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>a) "Precise representation" (DCRM III.2.2.) is key for sophisticated special collections users and "i.e." and "[sic]" provide quality-assurance that the representation is precise<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>b) Unintentionally incorrect information is not infrequent in graphic materials, which are not "self describing" the way books with title pages are, and such inaccuracies need immediate correction in order to make sense to users. For example, the image at http://hdl.loc.gov/loc.pnp/ggbain.19657 was wrongly titled "Royal Palace, Warsaw" by the news agency that created it; it actually depicts the Kremlin, so its title according to DCRM(G) should be "Royal Palace, Warsaw [i.e. Kremlin Palace, Moscow]" <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>c) Title and imprint information commonly get pulled out for image databases and picture captioning, so we need a complete package in those areas; moving corrections to the notes splits information that needs to stay assembled for user convenience<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thoughts? Comments?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Many thanks,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> Erin (Chair, DCRM(G) Editorial Team)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>--------------------------------------------------<o:p></o:p></p><p class=MsoNormal>Erin C. Blake, Ph.D. | Curator of Art & Special Collections | Folger Shakespeare Library | 201 E. Capitol St. SE | Washington, DC 20003-1004 | office tel. (202) 675-0323 | fax: (202) 675-0328 | eblake@folger.edu | www.folger.edu<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>