________________________________________ From: Resource Description and Access / Resource Description and Access [[email protected]] On Behalf Of J. McRee Elrod [[email protected]] Sent: February-25-11 7:34 PM To: [email protected] Subject: Re: [RDA-L] Abbreviations in RDA -- two preferred names for places
>>it's also applicable to many other elements that can be recorded even >>if no jurisdictional qualifier is needed in an access point. For example, >>place of birth can be recorded as just a country if that is all that is >>known, and you would use abbreviations for the countries found in Appendix >>B.11. See the first example in RDA 9.8.1.3: >But aren't all the examples you give for fiels in records other than >bibliograohic manifestation ones? And in most of the examples you >give, the abbreviated form is a qualifier. I think you're referring to four RDA elements for places that are not used as qualifiers in headings. Elements that are used to identify Persons in RDA: RDA 9.8 Place of Birth RDA 9.9 Place of Death RDA 9.10 Country Associated with the Person RDA 9.11 Place of Residence These are now found in these new MARC authority fields: 370 $a - Place of Birth 370 $b - Place of Death 370 $c - Associated country 370 $e - Place of residence (also used for Headquarters for Corporate Body-- which can be a qualifer) The values for these fields are entered using the abbreviations in RDA Appendix B.11. Example from http://www.loc.gov/marc/authority/ad370.html: 370 $e Calif. This is a good example of why using AACR2 abbreviations is just silly. It's such a headache for catalogers to 1) look up abbreviations in tables over and over again, and 2) remember which fields use these abbreviations and which ones don't. It's simpler to remember a single value ("California" in the above example). If a catalog user saw abbreviations like "A.C.T." or "Man." or "Mo.", what would we expect the user to think? Thomas Brennndorfer Guelph Public Library
