Module 4: Persons, Families, and Corporate Bodies -- Authorized access points and authority records Library of Congress RDA Seminar, University of Florence,

Slides:



Advertisements
Similar presentations
Future of Cataloging RDA and other innovations Pt. 2.
Advertisements

RDA Test Train the Trainer Module 2: Structure [Content as of Mar. 31, 2010]
LC Training for RDA: Resource Description & Access Module 5: Authorities I Part 5: Identifying Persons Cooperative and Instructional Programs Division.
Module 4: Persons, Families, and Corporate Bodies -- Elements and authorized access points LC RDA for Georgia Cataloging Summit Aug. 9-10, 2011.
Christee Pascale, Associate Head, Metadata & Catloging Jacquie Samples, Continuing & Electronic Resources Librarian North Carolina State University Libraries.
Identifying Persons and Corporate Bodies 1 -- elements and authorized access points James/Kuhagen for VLA - Feb. 5, 2013.
RDA Test “Train the Trainer” Module 6: Identifying Families [Content as of Mar. 31, 2010]
MARC 21, FRBR, RDA Review terminology (especially for non-native English speakers) Conceptual models Elements Attributes Future: Probably not a bib record,
T ASK G ROUP TO F ORMULATE OR R ECOMMEND PCC/NACO RDA P OLICY ON A UTHORITY I SSUES : S UMMARY OF R ECOMMENDATIONS Kathy Glennan University of Maryland.
RDA & Serials. RDA Toolkit CONSER RDA Cataloging Checklist for Textual Serials (DRAFT) CONSER RDA Core Elements Where’s that Tool? CONSER RDA Cataloging.
LC Training for RDA: Resource Description & Access Module 6: Authorities II Part 3: Identifying Places Cooperative and Instructional Programs Division.
RDA Records for Persons 3a. Conferencia Regional sobre Catalogación Universidad Autónoma de San Luis Potosí de Marzo 2011 Robert L. Maxwell Chair,
RDA and Authority Records: Enhancing Discovery Adam L. Schiff Principal Cataloger University of Washington Libraries OLA Conference 2014.
Teaching RDA Train-the-trainer course for RDA: Resource Description and Access Presented by the National Library of Australia September – November 2012.
RDA Test at LC Module 1: Overview What RDA Is; Structure.
Module B: Identifying works User task = identify.
Module 8 Series in AACR2 and RDA: What’s the same? What’s different?
RDA: A New Standard Supporting Resource Discovery Presentation given at the CLA conference session The Future of Resource Discovery: Promoting Resource.
LC Training for RDA: Resource Description & Access Module 6: Authorities II Part 1: Identifying Families Cooperative and Instructional Programs Division.
Teaching RDA Train-the-trainer course for RDA: Resource Description and Access Presented by the National Library of Australia September – November 2012.
RDA Test at LC Module 4: Persons, Families, and Corporate Bodies Authorized Access Points and Authority Records.
Module 4: Persons, Families, and Corporate Bodies -- Elements and authorized access points LC RDA for NASIG - June 1, 2011.
Descriptive Cataloging Using RDA Module 8 Identifying Persons, Families, and Corporate Bodies Cooperative and Instructional Programs Division Library of.
Module 5: Relationships -- in bibliographic records and in authority records.
LC Training for RDA: Resource Description & Access
RDA AND AUTHORITY CONTROL Name: Hester Marais Job Title: Authority Describer Tel: Your institution's logo.
RDA Test “Train the Trainer” Module 7: Identifying Corporate Bodies [Content as of Mar. 31, 2010]
RDA Test “Train the Trainer Module 1: What RDA is and isn’t [Content as of Mar. 31, 2010]
Module C: Identifying expressions User task: identify.
7: Basics of RDA Relationships for Serials Relationships in RDA Relationship designators Creators and other corporate bodies related to works Corporate.
LC Training for RDA: Resource Description & Access Module 6: Authorities II Part 4: FRBR Group One and NARs Cooperative and Instructional Programs Division.
Description Week 5 LBSC 671 Creating Information Infrastructures.
RDA Authority Records in Voyager Jenifer Marquardt (UGA) And Julie Dyles (UGA)
LC Training for RDA: Resource Description & Access Authorities Day 1 Cooperative and Instructional Programs Division Library of Congress, 2012 Adapted.
Module 5: Relationships -- in bibliographic records and in authority records LC RDA for NASIG - June 1, 2011.
RDA in NACO Module 10 Non-Latin Languages. 2 2 RDA and AACR2 in Non-Latin Authority Work As in other areas, most NACO instructions on NAR creation are.
Module 4: Persons, Families, and Corporate Bodies -- Elements and authorized access points Library of Congress RDA Preconference for MLA/DLA May 4, 2011.
CONSER RDA Bridge Training [date] Presenters : [names] 1.
Changing and Reviewing Name Authority Records © The British Library Board 2014.
RDA Toolkit With thanks to Lori Robare (University of Oregon) and Robert Maxwell (Brigham Young University) for most of these slides.
New MARC Fields with RDA Bibliographic and Authority Formats Bibliographic and Authority Formats.
Module 8 Series in AACR2 and RDA: What’s the same? What’s different?
Pan-Canadian RDA Training Module: Cataloguing with RDA.
RDA in NACO Module 2.b MARC 21 in NACO RDA Authority Records: Old and New Fields.
RDA Test “Train the Trainer” Module 5: Identifying Persons [Content as of Mar. 31, 2010]
Module 8: Changes to RDA LC RDA for NASIG - June 1, in general and for serials.
Module 3: Identifying works and expressions LC RDA for NASIG - June 1, 2011.
RDA in NACO Module 6.a RDA Chapter 11: Identifying Corporate Bodies—Overview Recording the Attributes.
Cambridge University Library RDA Toolkit Training session Adapted for Cambridge use by Janet Davis.
1 Making Changes to Personal Name and Corporate Body Authority Records Module 7. Making Changes to Existing Name and Work/Expression Authority Records.
RDA in NACO Module 4.a Module 4.b Module 4.c RDA Chapter 9: Identifying Persons— Overview Recording the Attributes.
Identifying Series: Attributes of a Work and Attributes of an Expression: RDA Chapters 5 and 6 Module 2a.
10/12/98Organization of Information in Collections Form of Names -- Personal Names (cont), Corporate Names and Uniform Titles University of California,
LC Training for RDA: Resource Description & Access Authorities Day 2 Cooperative and Instructional Programs Division Library of Congress, 2012 Adapted.
RDA Compared with AACR2 Presentation given at the ALA conference program session Look Before You Leap: taking RDA for a test-drive July 11, 2009 by Tom.
RDA DAY 1 – part 2 web version 1. 2 When you catalog a “book” in hand: You are working with a FRBR Group 1 Item The bibliographic record you create will.
Authority Control Interest Group RDA and MARC ALA Mid-Winter Denver 23 January 2009 John Espley VTLS Inc.
RDA in NACO Module 3 RDA Toolkit and where you find the instructions you need: Name entities and attributes.
11 Ana Lupe Cristán Policy and Standards Division Library of Congress June 2012 Name Authorities - What’s New?
10/12/98Organization of Information in Collections Form of Names -- Personal Names (cont) and Corporate Names University of California, Berkeley School.
LC Training for RDA: Resource Description & Access Module 5: Authorities I Part 4: RDA Toolkit Cooperative and Instructional Programs Division Library.
RDA Training University of Nevada, Las Vegas May2013 Module 3 RDA Basics Using the RDA Toolkit.
The British Library Guide to RDA Name Authority Records © The British Library Board 2014.
Current initiatives in developing library linked data Gordon Dunsire Presented at the Cataloguing and Indexing Group Scotland seminar “Linked data and.
Book Cataloging with RDA. RDA Instructions & Guidelines General things: – Core elements (required) – Alternative guidelines and instructions – Optional.
RDA for Law Catalogers Cataloging New Editions of Monographs presented at the AALL Annual Meeting 2012 July 21, 2012 (revised July 31, 2012) George Prager.
PCC Preparations for RDA Linda Barnhart RDA Forum -- ALA Annual June 23, 2012 Anaheim, California.
Forming Names According to RDA
2016 CTP Cataloging Workshop Session one
FRBR and FRAD as Implemented in RDA
Presentation transcript:

Module 4: Persons, Families, and Corporate Bodies -- Authorized access points and authority records Library of Congress RDA Seminar, University of Florence, May 29-June 2, 2011

RDA Seminar, University of Florence2 FRBR Group 2 entities RDA chapters –8 = General guidelines... –9 = Identifying persons –10 = Identifying families –11 = Identifying corporate bodies Group 2 entities have relationships –To works, expressions, manifestations, and items (FRBR Group 1 entities) –To other Group 2 entities (module 5)

RDA Seminar, University of Florence3 Authorized access points Forms created according to RDA ch Forms recorded in authority records (NARs) in LC/NACO Authority File Used in: –bibliographic records to express relationships to resources being cataloged –other authority records as 5XX fields or as part of name/title 4XX fields

RDA Seminar, University of Florence4 Context of this module Data elements that identify persons, families, and corporate bodies Forms of authorized access points you will see in bibliographic records New fields for some of the data elements you might see in authority records Not how to create authority records –See training materials on LC site

RDA Seminar, University of Florence5 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 , etc.), can also give variant access points in original language/script Other elements: if instructions in ch don’t specify language, give element in English.

RDA Seminar, University of Florence6 Chapter 9: Identifying persons

RDA Seminar, University of Florence7 Scope of “person” Definition (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 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 –During US RDA Test: also real non-humans

RDA Seminar, University of Florence8 Examples of expanded scope in RDA and during Test 100 0# $a Miss Piggy $a Miss Piggy’s guide to life / $c by Miss Piggy as told to Henry Beard # $a Beard, Henry # $a Lassie # $a Stories of Hollywood / $c told by Lassie.

RDA Seminar, University of Florence9 Preferred name (RDA 9.2.2) Form to be used when constructing the authorized access point –Variant name used in variant access points If individual has more than one identity, a preferred name for each identity (RDA ) –No time period restrictions Choose the form most commonly known Variant spellings: choose the form found on the first resource received (RDA )

RDA Seminar, University of Florence10 Surnames: words, etc., indicating relationships Include words, etc., (e.g., Jr., Sr., IV) in preferred name – not just to break conflict MARC: still encode title/term in subfield $c of authorized access point 100 1# $a Rogers, Roy, $c Jr., $d ## $a Growing up with Roy and Dale, 1986: $b t.p.(Roy Rogers, Jr.) p. 16 (born 1946)

RDA Seminar, University of Florence11 Terms of address not as additions But may be needed as part of the preferred name: –When the name consists only of the surname (RDA : Seuss, Dr.) –For a married person identified only by a partner’s name and a term of address (RDA : Davis, Maxwell, Mrs.) –If part of a phrase consisting of a forename(s) preceded by a term of address (RDA : Sam, Cousin)

RDA Seminar, University of Florence12 Date associated with the person Three dates: –Date of birth (RDA 9.3.2) -- core –Date of death (RDA 9.3.3) -- core –Period of activity of the person – no restrictions on time period (RDA 9.3.4) – core if... Guidelines for probable dates (RDA 9.3.1) Recorded in MARC X00 $d

RDA Seminar, University of Florence13 Changes when giving dates for persons Abbreviations “cent.,” “ca.,” “b.,” “d.,” and “fl.” not in appendix B –“cent.” becomes “century” –“approximately” replaces “ca.” –“b.” and “d.” dates: use hyphens instead of spelling out the abbreviations –Use “active” for “fl.”

RDA Seminar, University of Florence14 Title of the person (RDA 9.4) Limited scope: –Royalty, nobility, or ecclesiastical rank or office –Person of religious vocation MARC X00 $c – no change 100 0# $a Carl $b XVI Gustaf, $c King of Sweden, $d # $a Benedict $b XVI, $c Pope, $d 1927-

RDA Seminar, University of Florence15 Fuller form of name (RDA 9.5) 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) MARC X00 $q: no change LC: included whenever available during the US RDA Test; will need a PCC policy

RDA Seminar, University of Florence16 Examples: Fuller form of name 100 1# $a Smith, Nancy E. $q (Nancy Elizabeth) 100 1# $a Williams, John $q (John Dudley) 100 1# $a King, $c Mrs. $q (Annie Liddon)

RDA Seminar, University of Florence17 Other designation associated with the person (RDA 9.6) Limited scope: Christian saints; spirits MARC X00 $c – no change –“Saint” preceded by comma –“Spirit” enclosed in parentheses at end of access point 100 0# $a Joan, $c of Arc, Saint, $d $c (Spirit)

RDA Seminar, University of Florence18 Field of activity of person (RDA 9.15) Scope = “field of endeavour, area of expertise, etc., in which a person is or was engaged” Core: –for a person whose name consists of a phrase or appellation not conveying the idea of a person, or –if needed to distinguish one person from another with the same name MARC X00 $c – always enclosed in parentheses 100 0# $a Spotted Horse $c (Crow Indian chief)

RDA Seminar, University of Florence19 Profession or occupation (RDA 9.16) Core: –for a person whose name consists of a phrase or appellation not conveying the idea of a person, or –if needed to distinguish one person from another with the same name Overlap with “field of activity” MARC X00 $c – always enclosed in parentheses 100 1# $a Watt, James $c (Gardener)

RDA Seminar, University of Florence20 Chapter 10: Identifying families

RDA Seminar, University of Florence21 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” Not in AACR2

RDA Seminar, University of Florence22 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)) –Also possible for general library materials: genealogy newsletters, family reunion publications, etc.

RDA Seminar, University of Florence23 Name authority records vs. subject headings Ch. 10 applies to distinctive family entities Continue the current subject cataloging policy for general family groupings Separate authority records will exist in the LC/NACO Authority File and LCSH

RDA Seminar, University of Florence24 Preferred name (RDA ) Form to be used when constructing the authorized access point –Variant name used in variant access points (not LC core) Choose the form most commonly known –Surname or equivalent –Royal house, dynasty, clan, etc. MARC X00 3# $a

RDA Seminar, University of Florence25 Type of family (RDA 10.3) 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 Seminar, University of Florence26 Date associated with the family (RDA 10.4) Scope = “a significant date associated with a family,” e.g., – –202 B.C.-220 A.D. –4th-9th centuries MARC X00 $d 100 3# $a Pahlavi (Dynasty : $d )

RDA Seminar, University of Florence27 Place associated with family (RDA 10.5) Scope = “place where a family resides or has resided or has some connection” Include in access point if needed to distinguish one family from another with the same name or would help identify Give place in form as an authorized access point (ch. 16) in subfield $c 100 3# $a Nayak (Dynasty : $d 1529–1739 : $c Madurai, India)

RDA Seminar, University of Florence28 Prominent member of family (RDA 10.6) Scope = “a well-known individual who is a member of a family” Include in access point if needed to distinguish one family from another with the same name or would help identify Give name in form as an authorized access point (ch. 9) in subfield $g 100 3# $a Medici (Royal house : $g Medici, Lorenzo de’, )

RDA Seminar, University of Florence29 Chapter 11: Identifying corporate bodies

RDA Seminar, University of Florence30 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)

RDA Seminar, University of Florence31 Preferred name for the corporate body (RDA ) Choose the form most commonly known Variant spellings: choose the form found in the first resource received (RDA ) –LC will keep its policy to change to the later spelling in cases of orthographic reform Not abbreviating “Department” (should not have abbreviated in AACR2 headings)

RDA Seminar, University of Florence32 Change in form for conferences, etc. A merged instruction for preferred name of a conference, congress, meeting, exhibition, fair, festival, etc. - changes from AACR2: –Retain frequency in the name of a conference, congress, or meeting –Omit year of convocation from the name of an exhibition, fair, or festival

RDA Seminar, University of Florence33 Location of conference, etc. (RDA ) 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 appendix E.2.2.4) If conference held online, location is “Online” MARC X11 $c – no change

RDA Seminar, University of Florence34 Date of conference, etc. (RDA ) Scope = date or range of dates, given as year or years, in which a conference, etc., was held Not given in access point if publications of a conference, etc., cataloged as a serial MARC X11 $d – no change

RDA Seminar, University of Florence35 Date of establishment (RDA ) or termination (RDA ) Scope = year in which a corporate body was established or terminated Give if needed to differentiate the name of one corporate body from another MARC X10: add, with hyphen in parentheses, to the preferred name – no change

RDA Seminar, University of Florence36 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 In the form and language recorded as the preferred name for the institution (not the authorized access point for the institution)

RDA Seminar, University of Florence37 MARC for Associated institution For access point: –Conference: subfield $c –Other corporate bodies: add to the preferred name of the corporate body (subfielding and punctuation will vary) 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)

RDA Seminar, University of Florence38 Elements for Corporate body Associated institution (subfielding varies) 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)

RDA Seminar, University of Florence39 Number of a conference, etc. (RDA 11.6) Scope = “designation of the sequencing of a conference, etc., within a series of conferences, etc.” Use English ordinal numerals 1st, 2nd, 3rd, etc. Not given in access point if publications of a conference, etc., cataloged as a serial MARC: X11 $n

RDA Seminar, University of Florence40 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. 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

RDA Seminar, University of Florence41 MARC for Other designation... In access point: add, in parentheses, to the preferred name of the corporate body (subfielding may vary) 111 2# $a Beanpot (Hockey tournament) 151 ## $a Korea (South)

RDA Seminar, University of Florence42 Assembling elements to create authorized access points

RDA Seminar, University of Florence43 Access points 9.19: Constructing access points to represent persons 10.10: Constructing access points to represent families 11.13: Constructing access points to represent corporate bodies See RDA appendix E and LCPS for punctuation, etc. (AACR2 style carried forward)

RDA Seminar, University of Florence44 MARC changes for RDA authority records Two clues that the authority record is an RDA record: –008/10: value “z” (Other) –040 $a ___ $b ___ $c ___ $e rda Examples of RDA authority records for persons, families, and corporate bodies in separate handout

RDA Seminar, University of Florence45 New fields in MARC 21 authority format for persons 046: Special coded dates 370: Associated place 371: Address 372: Field of activity 373: Affiliation 374: Occupation 375: Gender 377: Associated language

RDA Seminar, University of Florence46 New fields in MARC 21 authority format for families 046: Special coded dates 370: Associated place 376: Family information

RDA Seminar, University of Florence47 New fields in MARC 21 authority format for corporate bodies 046: Special coded dates 370: Associated place 371: Address 377: Associated language

RDA Seminar, University of Florence48 More information on new fields in the MARC 21 authority format LC’s practice for the RDA Test html Examples folder for authority records on PSD site s.html LC Network Development and MARC Standards Office site: