320 likes | 336 Views
Learn how to identify corporate bodies, including their names, locations, dates, and identifiers, in accordance with RDA guidelines.
E N D
RDA Test “Train the Trainer” Module 7: Identifying Corporate Bodies [Content as of Mar. 31, 2010]
Scope of “corporate body” • Definition (RDA 8.1.2) = “an organization or group of persons and/or organizations that is identified by a particular name and that acts, or may act, as a unit” • Includes ad hoc events (such as athletic contests, exhibitions, expeditions, fairs, and festivals) and vessels (e.g., ships and spacecraft)
Language and script • RDA 8.4 • Name in the language and script in which it appears in the resource used for name • Alternative: a transliterated form as a substitute for or in addition to the found form • Other attributes in language and script prescribed in instructions • If no language or script prescribed, then in language/script preferred by the agency (0.11.2)
General guidelines (RDA 8.5) • Capitalization of name – see RDA appendix A.2 • Numbers in name in found form • Ordinal numeral connected to meeting, etc. -- see RDA 11.6.1.6 • Accents in name as found; add if needed • Abbreviations in name – see RDA appendix B.2
Elements covered in this module • Core • Core if … • Other elements if change from AACR2 • MARC 21 changes included in the above
Terminology • Name of the corporate body = “word, character, or group of words and/or characters by which a corporate body is known” • Preferred name • For current implementations = the form of name used when constructing the authorized access point • Variant name • For current implementations = the form of name used when constructing a variant access point
Sources of information • Preferred name: priority order (RDA 11.2.2.2) • Preferred sources of information (RDA 2.2.2) in resources associated with the corporate body • Other formal statements appearing in resources associated with the corporate body • Other sources including reference sources
Preferred name for the corporate body • RDA 11.2.2 • Choose the form most commonly known • Variant spellings: choose the form found in the first resource received (RDA 11.2.2.5.1) • LC will keep its policy to change to the later spelling in cases of orthographic reform
Location of conference, etc. • RDA 11.3.2 • In form as authorized access point (ch. 16) • No “rule of three” when sessions held in three or more locations (separated by semicolons in access point -- RDA E.2.2.4) • If conference held online, location is “Online”
MARC for Location of conference • Access point: in subfield $c • 370 field (authority format only): $c, $e, $f 111 2# $a National and Household Food Security Workshop $d(2003 : $c Lusaka, Zambia) 370 ## $e Lusaka, Zambia
Date associated with the corporate body • RDA 11.4 • Scope = date(s) of a conference, etc., or date of establishment/termination of a corporate body • Generally a year or years unless need to be more specific to distinguish
Date associated with the corporate body • Core element in two situations: • As the date or dates of a conference or similar event • As the date of establishment or termination of a corporate body if needed to break a conflict
MARC for Date of corporate body • Access point for conference, etc.: in $d • Access point for other corporate body: added in parentheses to the preferred name of the corporate body • 046 field: $s, $t
MARC for Date of corporate body 046 ## $s 2010 111 2# $a Olympic Winter Games $n (21st : $d 2010 : $c Vancouver, B.C.) 370 ## $f Vancouver, B.C. 046 ## $s 1946 110 2# $a Gesellschaft für Musikforschung (1946–)
Number of a conference, etc. • RDA 11.6 • Scope = “designation of the sequencing of a conference, etc., within a series of conferences, etc.” • As ordinal numeral from any source • MARC in access point: in subfield $n • No separate MARC field for this element
Identifier for the corporate body • RDA 11.12 • Scope: “character string uniquely associated with a corporate body, or with a surrogate for a corporate body (e.g., an authority record), that serves to differentiate that corporate body from other corporate bodies” • Precede the identifier with indication of person or agency, etc., responsible for assigning the identifier
MARC for Identifier for a body • In access point in bibliographic records, record control number in MARC subfield $0 (Authority record control number) • In authority records: • a record control number in field 001, 010, etc. • other identifiers in field 024 with first indicator “7” (ensure that source of code has been added to MARC list cited in subfield $2)
Core elements to distinguish • RDA 0.6.4: If elements are being recorded to distinguish the preferred name of one corporate body from that of another, record the elements: • either as additions to the authorized access point representing the corporate body [RDA Test], • as separate elements, or • as both
Location of headquarters, etc. • RDA 11.3.3 • Scope: • country, state, province, etc., or local place of headquarters, or • geographic area of corporate body’s activities • Core if needed to distinguish one corporate body from another with the same name • In form as authorized access point (Ch. 16)
MARC for … headquarters • Access point: added in parentheses to the preferred name of the corporate body • 370 field (authority format only): $c, $e, $f 110 2# $a Sociedad Nacional de Agricultura (Chile) 370 ## $c Chile
Associated institution • RDA 11.5 • Core: • for conferences, etc., if the institution’s name provides better identification than the local place name or if the local place name is unknown or cannot be readily determined • if needed to distinguish one corporate body from another with the same name
Associated institution • In the form and language recorded as the preferred name for the institution (not the authorized access point) • MARC for access point: • for a conference: subfield $c • other access points: add to the preferred name of the corporate body (subfielding and punctuation may vary) • No separate MARC field for the element
MARC for Associated institution 046 ## $s 1997 111 2# $a International Conference on Georgian Psalmody $n (2nd : $d 1997 : $c Colchester Institute) 110 2# $a B’nai B’rith Hillel Federation Jewish Student Center (University of Cincinnati)
Other designation associated with the corporate body • RDA 11.7 • Scope: • a word, phrase, or abbreviation indicating incorporation or legal status • any term serving to differentiate the body from other corporate bodies, persons, etc.
Other designation … • Core: • For a body whose name does not convey the idea of a corporate body • if needed to distinguish one corporate body from another with the same name
MARC for Other designation • Access point: add in parentheses to the preferred name of the corporate body (subfielding may vary) • No separate MARC field for the element 111 2# $a Beanpot (Hockey tournament) 151 ## $a Korea (South)
Other changes for corporate bodies • One instruction (11.2.2.11) for conferences, congresses, meetings, exhibitions, fairs, festivals, etc. • Retain frequency in the name of a conference, congress, or meeting • Omit year of convocation from the name of an exhibition, fair, or festival
Current authority record practice now in RDA • Status of identification (RDA 8.10) • MARC 008/33 • Source consulted (RDA 8.12) • MARC 670 • Cataloguer’s note (RDA 8.13) • MARC 667
MARC coding changes for RDA authority records • 008/10: value “z” (Other) • 040 $a ___ $b ___ $c ___ $e rda
Other new fields in MARC authority format for corporate bodies • 371: address • 372: field of activity • 377: associated language
MARC Authority 670 field • If no separate MARC field for an RDA element for corporate bodies (e.g., associated institution), generally give information in 670 field • Agency decision for repeating in 670 field any element already recorded in a separate MARC field • Many of new MARC fields include “source” subfields
More information on authority format new fields • LC Network Development and MARC Standards Office site: • Training document #5 for LC’s proposed practice for the RDA Test http://www.loc.gov/marc/authority/ecadhome.html