RDA Changes Since April 2014 - Phase Three Updates

RDA Changes Since April 2014 - Phase Three Updates
Slide Note
Embed
Share

This document provides information on the changes in RDA (Resource Description and Access) since April 2014, specifically focusing on Phase Three updates related to name authority records. It covers the background, implementation phases, and details of Phase 3A changes, including enhancements to name records and their impact on bibliographic records. The timeline, categories of changes, and examples are also outlined. The document serves as a comprehensive resource for understanding the recent developments in RDA standards related to name authority.

  • RDA Changes
  • Name Authority Records
  • Phase Three Updates
  • Bibliographic Records
  • Information Management

Uploaded on Mar 05, 2025 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

E N D

Presentation Transcript


  1. NACO RDA Changes Since April 2014 Council on East Asian Libraries Annual Meeting March 23, 2015 Jessalyn Zoom Library of Congress 1

  2. Phase Three of RDA Changes to Name Authority Records 2

  3. Background Information April 2013: LC implemented RDA Series of updates to the LC/NACO Authority File (LC/NAF) and to LC bibliographic records Phase One and Phase Two: Summer 2012 March 31, 2013 3

  4. Phase Three Changes PCC RDA Authorities Phase 3 Task Group Several clean-up projects needed prior to final Phase 3 testing and implementation Split project into two distinct phases 3A: Work that involves changes to the authority 1XX field 3B: Work that does not involve changes to the authority 1XX field 4

  5. Phase 3A Changes Timeline: began in December 2014, completed in January 2015 Categories of changes involved in 3A: Changes involving the music medium of performance statement (subfield $m) Changes involving subfield $c of personal names Adding a 667 note to undifferentiated personal names records Re-formulation of any field 678 not suitable for public display, as 670 fields All changes to the 1XX previously defined for Phase 1 and 2 that were created subsequent to those phases Evaluation of the contents of the 370 field (on those records changed for another reason) 5

  6. Phase 3A Changes Additional enhancements to the name records included: Generate the 046 field as appropriate Generate the 382 field from certain music medium of performance statements 6

  7. Phase 3A Changes on Bibliographic Records Increased LC bibliographic record distribution resulting from Phase 3A changes will start in March 2015 LC will issue a follow-up announcement when the changes to bibliographic records have been completed 7

  8. Phase 3A Changes Examples Changes involving the music medium of performance statement (subfield $m) Title ($t or $a) Original $m term Replacement $m term Equivalent authority 382 field Trio or Trios strings violin, viola, cello $a piano $n 1$a violin $n 1$a cello $n 1$ s 3 Trio or Trios piano, strings piano, violin, cello $a piano $n 1 $a violin $n 1 $a cello $n 1 $s 3 Quartet or Quartets strings violins (2), viola, cello $a violin $n 2 $a viola $n 1 $a cello $n 1 $s 4 8

  9. Phase 3A Changes Examples Changes involving the music medium of performance statement (subfield $m) Generating the 382 field containing medium of performance selected from a standard list or supplied without consulting a thesaurus (e.g., lcmpt) Information from authority 1XX field (not all subfields shown): $t Trios, $m piano, clarinet, viola Program-generated 382 field: 382 0# $a piano $n 1 $a clarinet $n 1 $a viola $n 1 $s 3 $2 lcmpt 9

  10. Phase 3A Changes Examples Changes involving subfield $c of personal names 100 1# $a Mason, William, $c Anabaptist 368 ## $c Anabaptist $2 lcsh 100 1# $a Dalton, William, $c Bookseller in York 370 ## $f York (England) $2 naf 100 1# $a Dominguez Diaz, Marta $c (Anthropologist of religion) 372 ## $a Anthropology of religion $2 lcsh 10

  11. Phase 3A Changes Examples Adding a 667 note to undifferentiated personal names records If the record contains the following categories of info.: 008/32 contains code b The record contains a 100 field Also contains at least two 670 fields with square bracket, then a 667 field is being added: THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS UNDIFFERENTIATED RECORD HAS BEEN HANDLED FOLLOWING THE GUIDELINES IN DCM Z1 008/32 11

  12. Phase 3A Changes Examples Re-formulation of any field 678 not suitable for public display, as 670 fields Example of 678 field which appear to be intended for public display: no2012161600 678 0# $a Wende Wagner (1941-1997) was an American actress and stuntwoman Example of re-tagging 678 field as 670 field: n 00063515 670 ## Info. from 678 field, 2014-02-10 $b (Died 1958) 12

  13. Phase 3A Changes Examples All changes to the 1XX previously defined for Phase 1 and 2 that were created subsequent to those phases For example: a formulation such as "b. 1902" in subfield $d will be converted in accordance with RDA to $d 1902 13

  14. Phase 3A(B) Changes Example Re-examining the 370 field Earlier RDA instruction of constructing 370 field: form of name used as if it were used as a qualifier in a corporate name heading Current RDA policy: Use the name exactly as found in the 151 field of the LC/NAF. When available, subfield $2 with code naf or lcsh can be added Kwanggju-Si, Korea vs. Kwangju-si (Ch lla-namdo, Korea) Tokyo vs. Tokyo (Japan) Kunming, China vs. Kunming Shi (China) 14

  15. Phase 3A(B) Changes Examples Pull selected bits of information from 670 field in authority record, build or supplement the authority 046 field in authority records for simple personal names by inspecting 670 fields for birth and death dates. Including consideration of some of the Japanese era dates and similar considerations Taish 15 9/Taish 2 8/6/Taish 7 Minguo 8 15

  16. Phase 3B Changes Re-coding of large numbers of AACR2 records as RDA, with no change to the 1XX field, will not begin before June 2015. Slam Load! LC, working with OCLC, will develop a mechanism for regular updating of these correspondences on LC/NAF following the completion of Phase 3B 16

  17. Phase 3B Changes Integrating ISNI (International Standard Name Identifier) into their respective LC/NACO records Replace obsolete indicators in 4XX and 5XX fields with blanks, and adjust Leader/17 and 008/39 Replacement of obsolete indicators with blanks (1XX), and removal of unnecessary terminal punctuation (part of 3B conversion now) Relator Terms Qualification of 410 fields for initialisms and acronyms in 410 fields Deletion of authority records that represent multiple language expressions is no longer part of the conversion 17

  18. Phase 3B Changes Example 024 Other Standard Identifier 024 7# $a8462832856536435$2isni Subfield $2 MARC code that identifies the source of the number or code. Used only when the first indicator contains value 7 (Source specified in subfield $2) 18

  19. Phase 3B Changes Example Replacement of obsolete indicators with blanks, and removal of unnecessary terminal punctuation Changes made to the 008 field (008/17) Change the value of 008/39, based on the code in 040 subfield $a Change made to access fields Replace obsolete indicators with blanks 100, 400, 500: 110, 410, 510, 111, 411, 511: second indicator should be blank 130, 430, 530: first indicator should be blank 151, 451, 551: both indicators should be blank 19

  20. Phase 3B Changes Example Relator terms Old term: 530 #0 $wr $i contains work New term: 530 #0 $wr $i container of (work) Old term: 700 1# $aSmith, Elsie, $d1900-945, $e editor of compilation. New term: 700 1# $aSmith, Elsie, $d1900-945, $e editor. 20

  21. Phase 3B Changes Example Qualification of 410 fields for initialisms and acronyms 010 $a no 88001548 110 $a American Relief Administration 410 $a A.R.A. (American Relief Administration) 410 $a ARA (American Relief Administration) The program will copy the qualifier "(Statistical Analysis Center)" from the first 410 field for initials to the second. 21

  22. Changes to make when a record is otherwise updated Generate the 046 field for personal names Generate the 382 field from certain music medium of performance statements Generate the 368 $c, $d, 370, 371, 372, 373, 374, and/or 375 fields from information derived from subfield $c of personal names Generate 382, 383 and/or 384 fields for "music" items Generate a 510 field for hierarchical superior Reference evaluation byte when a NAR contains any 4XX or 5XX fields None of these changes involves a change to the authority record s 1XX field 22

  23. Delete Expression Record Representing multiple language Expressions No longer Considered by the Task Group Records bear these characteristics (15,756) Subfield $l in the 1XX field contains an ampersand ( & ) Subfield $l in the 1XX field contains Polyglot 23

  24. NACO Changes Since April 2014 24

  25. New Subfields for 368 (Other Attributes of Person or Corporate Body) $d Title of person $s Start period $t End period $u Uniform Resource Identifier $v Source of information 25

  26. New Subfields for 368 (Other Attributes of Person or Corporate Body) Review of DCM Z1 instruction for $a, $b and $c: Prefer controlled vocabulary for terms, recording the source in subfield $2. For consistency, capitalize the first term in each subfield $a, $b and $c New subfield 368 $d (R) Title of person : Designation indicative of royalty, nobility, or ecclesiastical rank or office, or a term of address for a person of religious vocation. Best practice: Record in 368 subfield $d a title that you have included in either an authorized or variant access point 26

  27. New Subfields for 368 (Other Attributes of Person or Corporate Body) 100 0# Akiko, $c Princess, daughter of Tomohito, Prince of Mikasa, $d 1981- 368 ## $d Princess, daughter of Tomohito, Prince of Mikasa 100 0# Huike,$c da shi, $d 487-573 368 ## $d da shi 100 1# Chu, Tony $c (Fictitious character) 368 ## $c Fictitious characters $2 lcsh 374 Detectives $a Psychics $a Chinese Americans $2 lcsh 100 0# Kiritsubo, $c Emperor of Japan (Fictitious character) 368 ## $c Fictitious characters $2 lcsh 368 ## $d Emperor of Japan 374 ## Emperors $2 lcsh 27

  28. New Subfields for 046 (Special Coded Dates) $o Single or starting date for aggregated content $p - Ending date for aggregated content 046 ## $k1994$o0203$p1486 [Writings created 203-1486 and published as an anthology in 1994] 046 ## $k2006$o1932$p1940 [A DVD set of films originally released 1932-1940 and issued as a collection in 2006] 28

  29. New MARC field for 385 (Audience Characteristics) $a Audience term (R) $b Audience code (R) $m Demographic group term (NR) $n Demographic group code (NR) $0 Authority record control number or standard number (R) $2 Source (NR) 385 and 386 fields are used for Works and Expressions. Do not use them in NARs for persons Guidelines are being developed by PCC SCT Follow guidelines in MARC 21 Authority Format if using them 29

  30. New MARC fields for 385 (Audience Characteristics) 130 #0 $aMy first book of limericks 385 ## $aChildren$2lcsh 130 #0 $aHow beautiful the ordinary 385 ## $mAge group$aYoung adults$2lcsh 130 #0 $aJanet Suzman on acting in Shakespearean comedy 385 ## $aActors$2lcsh$0(DLC)sh 85000744 30

  31. New MARC field for 386 Creator/Contributor Characteristics $a Creator/contributor term (R) $b Creator/contributor code (R) $m Demographic group term (NR) $n Demographic group code (NR) $0 Authority record control number or standard number (R) $2 Source (NR) 385 and 386 fields are used for Works and Expressions. Do not use them in NARs for persons Guidelines are being developed by PCC SCT Follow guidelines in MARC 21 Authority Format if using them 31

  32. New MARC field for 386 Creator/Contributor Characteristics 130 #0 $aShort story masterpieces by American women writers 386 ## $aAmericans$aWomen$2lcsh 386 ## $mGender group$aWomen$2lcsh 386 ## $mNationality/regional group$aAmericans$2lcsh 130 #0 $aSwallowing clouds 386 ## $aChinese Canadians$2cash [An anthology of Chinese-Canadian poetry] 32

  33. New Subfield for 672 (Title Related to the Entity) $a Title (NR) $b Remainder of title (NR) $f Date (NR) $w Bibliographic record control number (R) $0 Authority record control number or standard number Guidelines are being developed by PCC SCT Follow guidelines in MARC 21 Authority Format if using them 33

  34. New Subfield for 672 (Title Related to the Entity) 670 ## $aPhone call to pub., 2/23/88$b(Ronald Fernandez, also author of Social psychology through literature) 672 #0 $aSocial psychology through literature 670 ## $aBerkeleyResearch web site, April 14, 2012$b(David Stern, emeritus professor of education, University of California, Berkeley; joined faculty in 1976; research focused on relationship between education and work, and resource allocation in schools) 672 #0 $aInternational perspectives on the school-to-work transition$f1999 672 #0 $aActive learning for students and teachers$f1997 672 #0 $aSchool to work$bresearch on programs in the United States$f1995 34

  35. New Subfield for 673 (Title Not Related to the Entity) $a Title (NR) $b Remainder of title (NR) $f Date (NR) $w Bibliographic record control number (R) $0 Authority record control number or standard number Guidelines are being developed by PCC SCT Follow guidelines in MARC 21 Authority Format if using them 35

  36. New Subfield for 673 (Title Not Related to the Entity) 100 1# $aWilliams, Cathy$b1953- 670 ## $aE-mail from author, Feb. 16, 2012:$b(Cathy J. Williams, b. July 1953; not author of Fifty years of caring and sharing; 99 easy-to-use speech and language activities; Mathcounts) 673 #0 $aFifty years of caring and sharing 673 #0 $a99 easy-to-use speech and language activities 673 #0 $aMathcounts 36

  37. Undifferentiated Personal Name As of Nov. 2013, LC and the PCC have agreed to cease creating or updating undifferentiated NARs coded under 008/32 b 667 note added in Phase 3 to all undifferentiated NARs THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS UNDIFFERENTIATED RECORD HAS BEEN HANDLED FOLLOWING THE GUIDELINES IN DCM Z1 008/32 Still same maintenance process Create a new NAR with distinguishing info. Add 667 note Formerly on undifferentiated name record: [LCCN of undifferentiated name record] Transfer info. pertaining to that person from the undifferentiated name record If more than one identity remains in the undifferentiated NAR, and there is not sufficient info. in the NAR to create new NARs for each each name, leave the NAR coded AACR2 37

  38. Undifferentiated Personal Name Note: Although names can now be created uniquely per RDA instruction at 9.19, PCC is not requiring catalogers to uniquely identify all names on an undifferentiated NAR except when only one is left as DCM Z1 indicates. 38

  39. Undifferentiated Personal Name If a differentiated NAR has not been created for the last identity: Add a 667 field to the undifferentiated NAR: 667 ## $a Last identity on undifferentiated record; reported for deletion. Report the undifferentiated NAR for deletion to naco@loc.gov; LC will create a new replacement NAR, add a 667 note to the new NAR, and delete the old record 39

  40. Undifferentiated Personal Name If a differentiated NAR has been created for the last identity: Add that information in the 667 note on the differentiated record to assure that a duplicate NAR will not be created: 667 ## $a Last identity on undifferentiated record; reported for deletion in favor of [LCCN of NAR]. Report the undifferentiated NAR for deletion to naco@loc.gov; LC will delete the NAR and add the LCCN of the deleted NAR in field 010 subfield $z of the newly created NAR 40

  41. Undifferentiated Personal Name 41

  42. Giving Parentheses in X00 $c or Not? If the term is being added as an occupation or profession, there should be parentheses. Jacob Johns is a professor at University of Chicago 100 1# Johns, Jacob $c (Professor) On the other hand, if the term appears as part of the person s name itself, there should be no parentheses. 100 0# Catherine, $c Duchess of Cambridge 42

  43. Access Point for a Series of Conference, Etc. (11.13.1.8.2) 11.13.1.8.2: If the access point represents a series of conferences, etc., do not add the number, date, or location of the conferences, etc. Revised to exclude the location of a conference as an addition to an access point for collective conference names. LC-PCC PS: Revised to conform with RDA instruction. Collective conference: 111 2# Blue Ridge Folklife Festival Be careful not to confuse a Place associated with a corporate body added to distinguish different conferences with the same name with a location of a conference. 43

  44. Access Point for a Single Instance of a Conference (11.13.1.8.1) 11.13.1.8.1: Add the following elements to the name of a one-time conference, or a single instance of a series of conferences (number, date, location). 111 2# Olympic Winter Games $n (21st : $d 2010 : $c Vancouver, B.C.) 111 2# Taiwan wen xue yan tao hui $d (2000 : $c Taizhong Xian li wen hua zhong xin) 44

  45. Corporate Bodies Considered to be Creators (19.2.1.1.1) and Participants in a Treaty (19.3.2.13) 19.2.1.1.1: Corporate bodies are considered to be creators when they are responsible for originating, issuing, or causing to be issued, works that fall into one or more of the following categories: g) legal works Treaties and other international agreements were removed from the list, thus signatories to a treaty cannot be treated as creator. 19.3.2.13: For a treaty, record the governments or other corporate bodies participating in the treaty as signatories, ratifiers, etc. Apply the basic instructions on recording other persons, families, and corporate bodies associated with a work at 19.3.1. 45

  46. Corporate Bodies Considered to be Creators (19.2.1.1.1) and Participants in a Treaty (19.3.2.13) 19.3.2.13: For a treaty, record the governments or other corporate bodies participating in the treaty as signatories, ratifiers, etc. Apply the basic instructions on recording other persons, families, and corporate bodies associated with a work at 19.3.1. Participants (signatories) in a treaty are now considered as a type of Other Person, Family, or Corporate Body Associated with a Work at 19.3.2.13 instead of the former practice that treated them as creators. United Nations International Civil Aviation Organization Authorized access points representing the participants in a treaty for: Agreement between the United Nations and the International Civil Aviation Organization 46

  47. Type of Corporate Body (11.7.1.4 and 11.13. 1.2) 11.13.1.2: Add a term designating the type of corporate body (see 11.7.1.4), if needed to distinguish one access point from another (i.e., when two or more bodies have the same name or names so similar that they may be confused). Also add such a term if the preferred name for the body does not convey the idea of a corporate body So, type of corporate body is core when the corporate body name does not convey the idea of a corporate body, or when the designation is needed to distinguish one corporate body from another with the same name. LC practice/PCC practice: Add the designation in English. KBS Ky to (Radio station) Niagara (Passenger ship) Niagara (Whaling ship) 47

  48. 377 Field (Associated Language) MARC 21 Authority Format: language a person uses when writing for publication, broadcasting, etc., a language a corporate body uses in its communications, a language of a family, or a language in which a work is expressed. Note: it is not necessarily a person s native language, and, a non-textual work will not have associated language. 110 2# $a Canadian Standards Association 377 ## $a eng $a fre 377 #7 $a en $a fr $2 iso639-1 48

  49. Questions? 49

More Related Content