RDA Test “Train the Trainer”

RDA Test “Train the Trainer” Module 6: Identifying Families [Content as of Mar. 31, 2010]

Scope of “family” • Definition (RDA 8.1.2) = “two or more persons related by birth, marriage, adoption, civil union, or similar legal status, or who otherwise present themselves as a family” • Doesn’t include those corporate bodies using “family” or similar word in their names

Scope of “family” • Now considered creators, contributors, etc. • Important for archives, museums, and special collections • May supplement RDA with specialist manuals (e.g., Describing archives : a content standard (DACS))

General guidelines (RDA 8.5) • Capitalization of name – see RDA appendix A.2 • Numbers in name in found form • Accents in name as found; add if needed • Abbreviations in name – see RDA appendix B.2

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)

Sources of information • Preferred name: priority order (RDA 10.2.2.2) • Preferred sources of information (RDA 2.2.2) in resources associated with the family • Other formal statements appearing in resources associated with the family • Other sources including reference sources • Other elements: generally, any source

Terminology • Name of the family = “word, character, or group of words and/or characters by which a family 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

Elements covered in this module • Core • Core if … • MARC 21 changes included in the above

Preferred name for the family • RDA 10.2.2.2 • Choose the form most commonly known: • Surname or equivalent • Royal house, dynasty, clan, etc. • MARC for access point: X00 3# $a

Type of family • RDA 10.3 • Scope: categorization or generic descriptor for the type of family • Not a controlled vocabulary • Examples: “Family,” “Clan,” “Royal house,” “Dynasty”

MARC for Type of family • Access point: added to the preferred name for the family • 376 field (authority format only): $a 100 3# $a Ingebretson (Family) 376 ## $a Family

Date associated with the family • RDA 10.4 • Scope = “a significant date associated with a family” • Examples: • 1802-1945 • 202 B.C.–220 A.D. • 4th–9th centuries

MARC for Date … family • Access point: added in subfield $d • 046 field (authority format only): $s, $t 046 ## $s 1925 $t 1979 100 3# $a Pahlavi (Dynasty : $d 1925-1979) 376 ## $a Dynasty

Identifier for the family • RDA 10.9 • Scope = “a character string uniquely associated with a family, or with a surrogate for a family (e.g., an authority record), that serves to differentiate that family from other families” • Precede the identifier with indication of person or agency, etc., responsible for assigning the identifier

MARC for Identifier for a family • 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 family from that of another, record the elements: • either as additions to the authorized access point representing the family [RDA Test], • asseparate elements, or • as both

Place associated with the family • RDA 10.5 • Scope = “place where a family resides or has resided or has some connection” • Core if needed to distinguish one family from another with the same name • In form as authorized access point (ch. 16)

MARC for Place … family • Access point: added in subfield $c • 370 field (authority format only): $c, $e, $f 046 ## $s 1529 $t 1739 100 3# $a Nayak (Dynasty : $d 1529–1739 : $c Madurai, India) 370 ## $e Madurai, India 376 ## $a Dynasty

Prominent member of the family • RDA 10.6 • Scope = “a well-known individual who is a member of a family” • Core if needed to distinguish one person from another with the same name • In form of authorized access point (ch. 9)

MARC for Prominent … family • Access point: added in subfield $g • 376 field (authority format only): $b 100 3# $a Medici (Royal house : $g Medici, Lorenzo de’, 1449-1492) 376 ## $a Royal house $b Medici, Lorenzo de’, 1449-1942

Current authority record practice now in RDA • Status of identification (RDA 8.10) • MARC 008/33 • Undifferentiated name indicator (RDA 8.11) • MARC 008/32 • 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

MARC Authority 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

RDA Test “Train the Trainer”