<HTML>
<HEAD>
<TITLE>Re: [DCRM-L] RDA Follow-up to "Cataloging Defensively" Webinar re edition statements</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>I’m interested to know whether the RBMS Bib Standards Committee has investigated possible MARBI receptiveness, and interest from the cataloging community, in a field for supplied edition statements. And given that there is growing consensus that MARC is on its last legs, not to mention the demise of the 503, do you have a sense that a new field is a likely solution? -Jackie<BR>
<BR>
</SPAN><FONT SIZE="4"><SPAN STYLE='font-size:10.5pt'>-- <BR>
Jackie Dooley<BR>
Program Officer<BR>
OCLC Research and the RLG Partnership<BR>
<BR>
949.492.5060 (work/home) -- Pacific Time<BR>
949.295.1529 (mobile)<BR>
<BR>
<BR>
<BR>
</SPAN></FONT><SPAN STYLE='font-size:10pt'><HR ALIGN=CENTER SIZE="3" WIDTH="95%"><B>From: </B>Deborah Leslie <<a href="djleslie@folger.edu">djleslie@folger.edu</a>><BR>
<B>Reply-To: </B>DCRM-L <<a href="dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><BR>
<B>Date: </B>Mon, 15 Nov 2010 11:58:07 -0500<BR>
<B>To: </B>DCRM-L <<a href="dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a>><BR>
<B>Subject: </B>Re: [DCRM-L] RDA Follow-up to "Cataloging Defensively" Webinar re edition statements<BR>
<BR>
</SPAN><FONT COLOR="#1F497D"><FONT SIZE="4"><SPAN STYLE='font-size:12pt'>Richard's got it right. A distinct MARC tag will allow, not only easy disambiguation of similar manifestations, but more precise display options, such as square brackets for those who might want to preserve the distinction between transcribed and supplied text. <BR>
<BR>
</SPAN></FONT></FONT><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><SPAN STYLE='font-size:10pt'><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><B>From:</B> <a href="dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a> [<a href="mailto:dcrm-l-bounces@lib.byu.edu">mailto:dcrm-l-bounces@lib.byu.edu</a>] <B>On Behalf Of </B>Noble, Richard<BR>
<B>Sent:</B> Monday, 15 November, 2010 10:12<BR>
<B>To:</B> DCRM Revision Group List<BR>
<B>Subject:</B> Re: [DCRM-L] RDA Follow-up to "Cataloging Defensively" Webinar re edition statements<BR>
</FONT></SPAN><FONT SIZE="4"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'>The RDA rule over-ruled in the Policy Statement is rather an absurd one, and presumes that the cataloguing agency is a large one, with numerous employees well enough versed in various languages to advise the uncertain cataloguer. There is, of course, an inherent conflict in this use of the 250 field, which is normally based on transcription from the item, when the contents are supplied as editorial invention. So now, per policy, we compromise by making the bracketed statement look like a transcription--that is, we fake it. (This is complicated by the fact that in many languages there is no unambiguous terminology that can be applied, in cataloguing books, to the edition/issue/impression taxonomy, without further qualification and explanation. What is an "edicion"?)<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="4"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'>Notes are less restricted, and a note in the language of the agency is necessary to back up the 250. As has been frequently noted concerning this topic, the invalidation of the 503 field has made it impossible to isolate a search for edition-related terms to a specific field, whether manually or by way of de-duping protocols.<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="4"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'>While it is not an immediate solution (cheating is, and I'm glad you've done it, however inadvertently), I do think that the definition of a new, distinct tag (e.g. 251) for a cataloguer-supplied edition statement in the language of the agency, would be a useful addition, very much on the order of the 246 "other title", which can be anything from any source that the cataloguer thinks will be useful (perhaps not even requiring the 250 as well). If a statement is desperately wanted in the language of the piece, let it be supplied by way of a parallel record created by an agency that writes its records in that language. Some sort of generic, Esperanto-like set of abbreviations would be useful, but I dare say that now meets a solid RDA roadblock, they being not immediately understanded of the people<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="4"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'>This is not a trivial matter, if we want to take FRBR at all seriously: we are talking about the identification/disambiguation of manifestations. Or does this really not matter, in the end? Do we just make a fudge of more or less similar manifestations? I.e., if it doesn't matter to those who don't understand the actual distinctions, whether or not expressed by way of abbreviation, then does it not matter at all?<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="4"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'>FRBR looks to the creation of a bibliographical database, not just a catalogue, but real bibliographies cannot be constructed with the kinds of restrictions that we meet with in rules primarily directed to the purpose of homogenizing master records for use in unmediated copy-cataloguing.<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT><FONT SIZE="5"><FONT FACE="Garamond"><SPAN STYLE='font-size:13pt'><BR>
</SPAN></FONT></FONT><FONT SIZE="4"><FONT FACE="Courier New"><SPAN STYLE='font-size:12pt'>RICHARD NOBLE : RARE BOOKS CATALOGER : JOHN HAY LIBRARY : BROWN UNIVERSITY<BR>
PROVIDENCE, RI 02912 : 401-863-1187/FAX 863-3384 : <a href="RICHARD_NOBLE@BROWN.EDU">RICHARD_NOBLE@BROWN.EDU</a> <BR>
</SPAN></FONT><SPAN STYLE='font-size:12pt'><FONT FACE="Times New Roman"><BR>
On Mon, Nov 15, 2010 at 8:38 AM, Schupbach, William <<a href="w.schupbach@wellcome.ac.uk">w.schupbach@wellcome.ac.uk</a>> wrote:<BR>
"The RDA Library of Congress Policy Statement 2.5.1.4 is an almost exact<BR>
restatement of AACR2 1.2B4, providing for a cataloger-supplied edition<BR>
statement: ?LCPS for 2.5.1.4 <<a href="http://2.5.1.4">http://2.5.1.4</a>> : Recording Edition Statements: If a<BR>
resource lacks an edition statement but it is known to contain<BR>
significant changes from other editions, supply a brief statement in the<BR>
language and script of the title proper and enclose it in square<BR>
brackets.? LC Policy Statements (LCPSs) are the RDA parallels to AACR2<BR>
LC Rule Interpretations (LCRIs)." (Jay Weitz)<BR>
<BR>
I had not noticed this before, but it means that, in most of the cases I<BR>
deal with, I should have been writing those bracketed 250s in Latin. Has<BR>
everybody else been doing this?<BR>
<BR>
William Schupbach<BR>
Wellcome Library, 183 Euston Road, London NW1 2BE<BR>
E-mail: <a href="w.schupbach@wellcome.ac.uk">w.schupbach@wellcome.ac.uk</a><BR>
<BR>
Visit the Wellcome Library Blog at: <a href="http://wellcomelibrary.blogspot.com">http://wellcomelibrary.blogspot.com</a><BR>
<BR>
<BR>
********<BR>
<BR>
<BR>
This message has been scanned for viruses by Websense Hosted Email Security - www.websense.com <<a href="http://www.websense.com">http://www.websense.com</a>> <BR>
<BR>
</FONT></SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>