1 / 74

Module E: Identifying persons, families, and corporate bodies

Module E: Identifying persons, families, and corporate bodies. -- not relationships. User task: identify. FRBR and FRAD Group 2 entities. RDA chapters 8 = General guidelines ... 9 = Identifying persons 10 = Identifying families 11 = Identifying corporate bodies

miad
Download Presentation

Module E: Identifying persons, families, and corporate bodies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Module E:Identifying persons, families, and corporate bodies -- not relationships User task: identify

  2. FRBR and FRAD Group 2 entities • RDA chapters • 8 = General guidelines ... • 9 = Identifying persons • 10 = Identifying families • 11 = Identifying corporate bodies • Group 2 entities have relationships (module F) • To works, expressions, manifestations, and items (FRBR Group 1 entities) • To other Group 2 entities RDA at LC 2011 -- Module E

  3. Core elements to distinguish • If elements are being recorded to distinguish one person, family, or corporate body from another, RDA gives choices for recording the elements (RDA 0.6.4): • LC policy: always give as additions to the authorized access point • LC policy: cataloger judgment to also give as separate elements in authority records RDA at LC 2011 -- Module E

  4. Authorized access points • Forms created according to RDA ch. 8-11 • See RDA appendix E and LCPS 1.7.1 for punctuation, etc. (AACR2 style carried forward) • Used in bibliographic records 1XX, 6XX, and 7XX to express relationships to resources being cataloged • Used in other authority records as 5XX fields (relationships to other Group 2 entities) or as part of name/title 4XX fields (relationships to resources) RDA at LC 2011 -- Module E

  5. Already an NAR in LC/NAF? -- changes from the Test • Until there are LC/PCC decisions about which AACR2 forms are valid for RDA, use established form (AACR2 or RDA)alreadyin the LC/NAF • Will be a mixture of AACR2 and RDA forms in bibliographic records • Do not add an RDA form in 7XX in an AACR2 authority record • LC will work with OCLC, SkyRiver, and others about updating access points RDA at LC 2011 -- Module E

  6. General guidelines in ch. 8 • Language and script for names (RDA 8.4): • U.S.: In authorized and variant access points, apply the alternative to give a romanized form. • For some languages (see LCPS 8.4, LCPS 9.2.2.5.3, etc.), can also give variant access points in original language/script • Other elements: if instructions in ch. 9-11 don’t specify language, give element in English. RDA at LC 2011 -- Module E

  7. Preferred & Variant names • Preferred name: form to be used when constructing the authorized access point in bibliographic records and 1XX field of name authority records • Variant name: form used in variant access points (4XX fields in name authority records) RDA at LC 2011 -- Module E

  8. Sources for elements • Preferred name (in order of preference): • Preferred sources of information (see RDA 2.2.2) in resources associated with the entity • Other formal statements appearing in resources associated with the entity • Other sources (including reference sources) RDA at LC 2011 -- Module E

  9. Sources for elements • If person, family, or corporate body is the subject of the work, may use reference sources to determine the commonly-known form of preferred name • Other elements: any source RDA at LC 2011 -- Module E

  10. Variant access points • Which variants to include in authority record as 4XX fields? • None are core in RDA • LC policy: cataloger judgment • Consider what userswould need or find helpful (other catalogers are users, too) RDA at LC 2011 -- Module E

  11. Context of this module • Elements in authorized access points • Other identifying elements • New fields for some of the data elements in authority records RDA at LC 2011 -- Module E

  12. Chapter 9:Identifying persons RDA 8.1.2: “An individual or an identity established by an individual (either alone or in collaboration with one or more other individuals)” RDA at LC 2011 -- Module E

  13. Scope of “person” • RDA 9.0: Includes fictitious entities: • Miss Piggy, Snoopy, etc. now in scope if presented as having responsibility in some way for a work, expression, manifestation, or item • LC policy: also real non-humans • Contact PSD if a fictitious entity is already represented by a subject heading RDA at LC 2011 -- Module E

  14. Persons: Authorized access points (RDA 9.19) • RDA 9.19.1.1: how to put together the elements to construct an authorized point [with links back to specific elements] • Preferred name is the basis • Additions to the name as instructed under 9.19.1.2–9.19.1.7 • LC policy change for additions and order: date(s) of birth and/or death if available; if still need to differentiate, then cataloger judgment on choice RDA at LC 2011 -- Module E

  15. Additions to the preferred name • 9.19.1.2 (9.4 and 9.6): title or other designation associated with the person # • 9.19.1.3 (9.3.2/9.3.3): date of birth and/or death * • 9.19.1.4 (9.5): fuller form of name ^ • 9.19.1.5 (9.3.4): period of activity of person ^ • 9.19.1.6 (9.16): profession or occupation # ^ • 9.19.1.7 (9.15): field of activity of person # ^ # = required for certain names LC policy: * = give if available; ^ = add to differentiate RDA at LC 2011 -- Module E

  16. Preferred name (RDA 9.2.2) • Choose the form most commonly known • Surnames: words, etc., indicatingrelationships (e.g., Jr., IV) part of the preferred name -- not just to differentiate • Variant spellings: choose the form found on the first resource received (RDA 9.2.2.5.4) RDA at LC 2011 -- Module E

  17. Preferred name (RDA 9.2.2) • Different names for the same person (RDA 9.2.2.6) and change of name (RDA 9.2.2.7) • If individual has more than one identity, a preferred name for each identity (RDA 9.2.2.8) • No time period restrictions • Different categories of names: RDA 9.2.2.9-RDA 9.2.2.26 • Change in sources for names in Hebrew alphabet (LCPS 9.2.2.5.3) RDA at LC 2011 -- Module E

  18. Changes in preferred names • Terms of address only if part of the preferred name -- not as additions: • Name consists only of the surname (RDA 9.2.2.9.3: Seuss, Dr.) • Married person identified only by a partner’s name and a term of address (RDA 9.2.2.9.4: Davis, Maxwell, Mrs.) • Part of a phrase consisting of a forename(s) preceded by a term of address (RDA 9.2.2.23: Sam, Cousin) RDA at LC 2011 -- Module E

  19. Additions to the preferred name: limited scope • Title of the person (RDA 9.4): • Royalty, nobility, or ecclesiastical rank or office • Person of religious vocation • Other designation associated with the person (RDA 9.6): • Christian saints • Spirits RDA at LC 2011 -- Module E

  20. Addition: Date associated with the person • LC policy: • Date of birth (RDA 9.3.2) -- if available • Date of death (RDA 9.3.3) -- if available • Period of activity of the person – no restrictions on time period in RDA (RDA 9.3.4) -- cataloger judgment if needed to differentiate • Guidelines for probable dates (RDA 9.3.1) RDA at LC 2011 -- Module E

  21. Changes when giving dates • Abbreviations “cent.,” “ca.,” “b.,” “d.,” and “fl.” not in appendix B • “cent.” becomes “century” • “approximately” replaces “ca.” • “b.” and “d.” dates: LC policy to use hyphens instead of spelling out the abbreviations • Use “active” for “fl.”: LC policy RDA at LC 2011 -- Module E

  22. Addition: fuller form of name • Scope: • Full form of a part of a name represented only by an initial or abbreviation in the form chosen as the preferred name, or • A part of the name not included in the form chosen as the preferred name (change from AACR2) • LC policy for new NARs: only add fuller form from another source to the preferred name if need to differentiate (change from Test policy) RDA at LC 2011 -- Module E

  23. Addition: Profession or occupation and Field of activity • Core: • If name does notconvey the idea of a person • LC policy: cataloger judgment choice to distinguish one person from another with the same name • Some overlap in examples for two elements -- to be discussed by JSC in November 2011 • MARC X00 $c – always in parentheses RDA at LC 2011 -- Module E

  24. New fields in MARC 21 authority format for persons • 046: Special coded dates (RDA 9.3) • 370: Associated place (RDA 9.8-9.11) * • 371: Address (RDA 9.12) * • 372: Field of activity (RDA 9.15) • 373: Affiliation (RDA 9.13) * • 374: Occupation (RDA 9.16) • 375: Gender (RDA 9.7) * • 377: Associated language (RDA 9.14) * • 378: Fuller form of personal name (RDA 9.5) * -- not yet implemented * = not eligible for authorized access points RDA at LC 2011 -- Module E

  25. Elements not eligible for inclusion in authorized access points • May be helpful for identification: • Associated place (RDA 9.8-9.11) • Address (RDA 9.12) • Affiliation (RDA 9.13) • Gender (RDA 9.7) • Language of the person (RDA 9.14) • Biographical information (RDA 9.17) RDA at LC 2011 -- Module E

  26. Associated place (RDA 9.8-9.11) • Places: • Place of birth and/or death • Country associated with the person • Place of residence • Place given in 370 field in form it would be as an addition to an access point; LC policy change: NAR not required • If not a jurisdiction, in separate 370 with vocabulary (e.g., LCSH) in subfield $2 RDA at LC 2011 -- Module E

  27. Address (RDA 9.12) • Mailing address • Email address • Only if publicly available • MARC field 371 RDA at LC 2011 -- Module E

  28. Affiliation (RDA 9.13) • Scope = name of group(s) with which the person has been or is affiliated • e.g., employment, education, membership • Affiliation given in form found on the resource • MARC field 373 (renamed this year to “Associated group”) RDA at LC 2011 -- Module E

  29. Gender (RDA 9.7) • Scope = gender with which a person identifies • Open list of terms in instruction + others as needed • MARC field 375 • Use subfield $2 if not from RDA RDA at LC 2011 -- Module E

  30. Language of the person (RDA 9.14) • Scope = language(s) used by the person in writing, speaking, singing, etc. • MARC field 377 • In MARC, form is three-character code from MARC code list of languages -- no prescribed order if more than one language RDA at LC 2011 -- Module E

  31. Biographical information (RDA 9.17) • Scope = information pertaining to life or history of a person • Can incorporate information from separate fields into a “public note” • MARC field 678 RDA at LC 2011 -- Module E

  32. Questions about persons? RDA at LC 2011 -- Module E

  33. Chapter 10:Identifying families 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” RDA at LC 2011 -- Module E

  34. Role 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)) Also possible for general library materials: genealogy newsletters, family reunion publications, etc. RDA at LC 2011 -- Module E

  35. NARs vs. subject headings • Ch. 10 applies to distinctive family entities • Continue the current subject cataloging policy for generalfamily groupings (SHM instruction sheet H 1631) • If no subject heading for the general family name, establish the subject heading • Separate authority records will exist in the LC/NACO Authority File and LCSH RDA at LC 2011 -- Module E

  36. Clarify difference in NAR for family (LCPS 10.0) • 667 field: • 008 coding • 008/11 = value “n” (not applicable) • 008/15 = value “b” (not appropriate) SUBJECT USAGE: This heading is not valid for use as a subject; use a family name heading from LCSH. RDA at LC 2011 -- Module E

  37. Families: Authorized access points (RDA 10.10) • RDA 10.10.1.1: how to put together the elements to construct an authorized point [with links back to specific elements] • Preferred name is the basis • Additions to the name as instructed under 10.10.1.2–10.10.1.5, in that order, as applicable RDA at LC 2011 -- Module E

  38. Additions to the preferred name • 10.10.1.2 (10.3): type of family • 10.10.1.3 (10.4): date associated with the family • 10.10.1.4 (10.5): place associated with the family ^ % • 10.10.1.5 (10/6) : prominent member of the family ^ % LC policy: ^ = if need to differentiate; % = cataloger judgment to add if don’t need to differentiate RDA at LC 2011 -- Module E

  39. Preferred name (RDA 10.2.2) • Choose the form most commonly known • Surname or equivalent • Royal house, dynasty, clan, etc. • MARC X00 3# $a RDA at LC 2011 -- Module E

  40. Addition: Type of family • Scope = categorization or generic descriptor for the type of family” • Not a controlled vocabulary – cataloger’s choice • “Family,” “Clan,” “Royal house,” “Dynasty,” etc. • MARC X00: added in parentheses to the preferred name 100 3# $a Ingebretson (Family) RDA at LC 2011 -- Module E

  41. Addition: Date associated with the family • Scope = “a significant date associated with a family,” e.g., • 1802-1945 • 202 B.C.-220 A.D. • 4th-9th centuries • MARC X00 $d 100 3# $a Pahlavi (Dynasty : $d 1925-1979) RDA at LC 2011 -- Module E

  42. Addition: Place associated with family • Scope = “place where a family resides or has resided or has some connection” • Core in access point if needed to distinguish one family from another with the same name • Give place in form as an authorized access point (ch. 16) in subfield $c (this use of place requires an NAR) 100 3# $a Nayak (Dynasty : $d 1529–1739 : $c Madurai, India) RDA at LC 2011 -- Module E

  43. Addition: Prominent member of family • Scope = “a well-known individual who is a member of a family” • Core in access point if needed to distinguish one family from another with the same name • Give name in form as an authorized access point (ch. 9) in subfield $g (this use of place requires an NAR) 100 3# $a Medici (Royal house : $g Medici, Lorenzo de’, 1449-1492) RDA at LC 2011 -- Module E

  44. New fields in MARC 21 authority format for families • 046: Special coded dates (RDA 10.4) • 370: Associated place (RDA 10.5) • 376: Family information: type of family (RDA 10.3), prominent member (RDA 10.6), hereditary title (RDA 10.7) * * “Hereditary title” not eligible for authorized access points RDA at LC 2011 -- Module E

  45. Elements not eligible for inclusion in authorized access points • May be helpful for identification: • Hereditary title (RDA 10.7) • Family history (RDA 10.8) RDA at LC 2011 -- Module E

  46. Hereditary title (RDA 10.7) • Scope = title of nobility associated with a family: • e.g., Earls of Shrewsbury ducs d'Orléans • MARC 376 subfield $c • Hereditary titles can also be given as variant access points (RDA 10.2.3.5) RDA at LC 2011 -- Module E

  47. Family history (RDA 10.8) • Scope = information pertaining to the history of a family • Can incorporate information from separate fields into a “public note” • MARC field 678 RDA at LC 2011 -- Module E

  48. Questions about families? RDA at LC 2011 -- Module E

  49. Chapter 11:Identifying corporate bodies 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” RDA at LC 2011 -- Module E

  50. Corporate bodies: Authorized access points (RDA 11.13) • RDA 11.13.1.1: how to put together the elements to construct an authorized point [with links back to specific elements] • Preferred name is the basis • Additions to the name as instructed under 11.13.1.2–11.13.1.8, in that order, as applicable RDA at LC 2011 -- Module E

More Related