<font size="2"><font face="georgia,serif">Helena could well have italicized and bolded her apt reference to the implications of cataloging rules for metadata in general (the whole point of RDA, if I understand its defenders' arguments correctly). If catalogers are to be conceived as front-line creators of metadata, then their work should anticipate the conditions under which it will be used; e.g <i><b>many pictures are harvested for use in specialized databases with just a few pieces of metadata attached (not the full catalog record).</b><span class="Apple-style-span" style="font-style: normal;"> Which is basically what I meant in my own response regarding the areas and elements that are likely and especially </span>not<span class="Apple-style-span" style="font-style: normal;"> likely to be harvested from MARC or MARC-like metadata for such purposes. Without correction of some sort, a 245 may be nothing better than uncritically transcribed garbage in that produces garbage out. </span></i></font></font><div>
<font class="Apple-style-span" face="georgia, serif"><b><i><br></i></b></font></div><div><font class="Apple-style-span" face="georgia, serif">I would further remark that this is not a format-specific condition.</font></div>
<div><font class="Apple-style-span" face="georgia, serif"><br></font></div><div><font face="'courier new', monospace">RICHARD NOBLE : RARE BOOKS CATALOGER : JOHN HAY LIBRARY : BROWN UNIVERSITY<br>PROVIDENCE, RI 02912 : 401-863-1187/FAX 863-3384 : <a href="mailto:RICHARD_NOBLE@BROWN.EDU" target="_blank">RICHARD_NOBLE@BROWN.EDU</a> </font><br>
<br><br><div class="gmail_quote">On Thu, Aug 4, 2011 at 6:50 PM, Zinkham, Helena <span dir="ltr"><<a href="mailto:hzin@loc.gov">hzin@loc.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Quick clarification: The DCRM(G) interest in having a transcribed and corrected title appear together in the same title element has nothing to do with protecting catalogers' reputations by pointing out 'who made a mistake.' Nothing.<br>
<br>
Nor is the question being raised with an eye towards consistency of practice over time "within" a library catalog. Quite the opposite--the concern is about what happens when picture titles are taken out of the catalog context and separated from the notes. This separation happens frequently because single pictures are often reproduced in book illustrations, Web pages, and lectures; or, many pictures are harvested for use in specialized databases with just a few pieces of metadata attached (not the full catalog record).<br>
<br>
We're looking for a way to alert catalog users when a title has totally misleading information. We're trying to reduce the chances that, for example, a picture showing Russia is used to represent Poland. True, we don't always know when a picture has an inaccurate title. But when we do, it seems useful to make it easy to recognize the real subject matter. That's the "complete package" -- keep the transcribed and the devised corrected title side by side, so that they travel together when pulled out of the library catalog.<br>
<br>
Is this a rare materials issue? I believe so, in that the inaccurate title issue surfaces most often among historical, limited distribution, and unpublished pictures. But it might primarily be a "graphic materials" issue--the frequency of "wholly inaccurate" titles might well be higher among pictures than other information resources.<br>
<font color="#888888"><br>
Helena Zinkham<br>
Prints & Photographs Division<br>
Library of Congress<br>
</font><div class="im"><br>
-----Original Message-----<br>
From: <a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a> [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>] On Behalf Of Robert Maxwell<br>
Sent: Thursday, August 04, 2011 1:59 PM<br>
To: DCRM Revision Group List<br>
</div><div><div></div><div class="h5">Subject: Re: [DCRM-L] Eliminating an RDA option in DCRM(G) draft: want to allow "i.e." and "[sic]"<br>
<br>
(a) "Quality assurance" is not the same thing as "precise representation." "[sic]" and "[i.e. ...]" are ways we catalogers leave behind the message "Hey, folks, the mistake was in the original--it wasn't ME that made it! Don't blame me!" The desire to do that is understandable, but the same desire is there among catalogers of all sorts, not just rare materials catalogers. I don't see that there's a rare cataloging reason to differ.<br>
<br>
(b) Unintentionally incorrect information no doubt abounds in all graphic materials, not just rare graphic materials. Again, I don't see a rare cataloging reason for the standard to differ.<br>
<br>
(c) I'm not sure I understand why inclusion of "sic" or "i.e." would create a "complete package" for labeling.<br>
<br>
Much as I, too, like to make sure people don't think *I* would ever make a typo in my transcription and so also miss the ability to use "sic" or "i.e." in RDA, I just don't think there's any rare cataloging reason why we should differ here.<br>
<br>
Bob<br>
<br>
Robert L. Maxwell<br>
Head, Special Collections and Formats Catalog Dept.<br>
6728 Harold B. Lee Library<br>
Brigham Young University<br>
Provo, UT 84602<br>
<a href="tel:%28801%29422-5568" value="+18014225568">(801)422-5568</a><br>
________________________________________<br>
From: <a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a> [<a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a>] On Behalf Of Erin Blake [EBlake@FOLGER.edu]<br>
Sent: Wednesday, August 03, 2011 7:31 PM<br>
To: <a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a><br>
Subject: [DCRM-L] Eliminating an RDA option in DCRM(G) draft: want to allow "i.e." and "[sic]"<br>
<br>
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).<br>
<br>
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:<br>
<br>
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<br>
<br>
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 <a href="http://hdl.loc.gov/loc.pnp/ggbain.19657" target="_blank">http://hdl.loc.gov/loc.pnp/ggbain.19657</a> 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]"<br>
<br>
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<br>
<br>
Thoughts? Comments?<br>
<br>
Many thanks,<br>
<br>
Erin (Chair, DCRM(G) Editorial Team)<br>
<br>
--------------------------------------------------<br>
Erin C. Blake, Ph.D. | Curator of Art & Special Collections | Folger Shakespeare Library | 201 E. Capitol St. SE | Washington, DC 20003-1004 | office tel. <a href="tel:%28202%29%20675-0323" value="+12026750323">(202) 675-0323</a> | fax: <a href="tel:%28202%29%20675-0328" value="+12026750328">(202) 675-0328</a> | <a href="mailto:eblake@folger.edu">eblake@folger.edu</a> | <a href="http://www.folger.edu" target="_blank">www.folger.edu</a><br>
<br>
</div></div></blockquote></div><br></div>