The rules for capitalization in AACR2 (and default RDA, which carries them over) are very complex and quite difficult for trainees to grasp, even more so when working with multiple languages. If one is running a minimal level project, it eats into training time, and, since it is pretty much impossible to get right, it is then necessary to set up boundaries for revision. The transcribe what you see approach is also extremely helpful when working with foreign languages that use a lot of diacritics, like French or Vietnamese for those title page designer who leave out a mark here or there. The notion of a cataloger recataloging a record to revert the RDA transcription to AACR2 rules is to me a (nightmarish) legacy of 20th century cataloging which I hope will not infect the younger generations who come to cataloging.
Steven Arakawa Catalog Librarian for Training & Documentation Catalog & Metadata Services, SML, Yale University P.O. Box 208240 New Haven, CT 06520-8240 (203)432-8286 [email protected] ________________________________________ From: Resource Description and Access / Resource Description and Access [[email protected]] On Behalf Of Jonathan Rochkind [[email protected]] Sent: Wednesday, January 12, 2011 10:32 AM To: [email protected] Subject: Re: [RDA-L] Browse and search RDA test data I don't see "value" in all caps, I am just not disturbed by them, and see some sense in transcribing what's on the item in a transcribed field, especially if it will make cataloging simpler or cheaper or easier. Basically, I just don't see it matters too much either way. ________________________________________ From: Resource Description and Access / Resource Description and Access [[email protected]] On Behalf Of Mike Tribby [[email protected]] Sent: Wednesday, January 12, 2011 10:14 AM To: [email protected] Subject: Re: [RDA-L] Browse and search RDA test data Quoting "J. McRee Elrod" <[email protected]>: > Capitalization as found would be acceptable in 505 contents and 520 > summaries, but 245 titles are seen in hitlists with other titles, so > uniformity is more important. > > In the upper case examples I checked, the all caps do not reflect the > source, according to Amazon images. There is no rationalization apart > from bone laziness in harvesting data. Quoting Hal Cain: >Contents notes rendered all uppercase have attracted hostile comment already >(perhaps not here, but certainly on Autocat), when incorporated into >(AACR2) >LC records from linked data produced or captured elsewhere. It's widely >understood that continuous uppercase text is more difficult for most >>people >to read. >I fail to understand what reasonable purpose can be served in using uppercase. > If it's as a paltry attempt to represent the style of the titlepage (or other >>>>source of primary identifying data for a document), that purpose would be >better served by attaching a link to a titlepage image -- which is a strategy >>>>I'm considering for a forthcoming project with early printed books. Perhaps not surprisingly, I find myself in agreement with both Mac and Hal. And I would ask Jonathan and any other list members who see value in all-caps display of titles if they have any thoughts on how to transcribe a title in which all letters are caps, but the letters at the start of the title (and possibly at the start of each word) are _larger_ caps than the caps that make up the rest of the title. I don't think my keyboard or my cataloging software is capable of creating caps in different sizes in the same field, at least not easily. Mike Tribby Senior Cataloger Quality Books Inc. The Best of America's Independent Presses mailto:[email protected]
