RDA Changes to the LC/NACO Name Authority File

Transcription

1 RDA Changes to the LC/NACO Name Authority File Tina Gross Jessica Schomberg PALS Acquisitions/Serials and Cataloging Workday - April 25, 2013

2 Overview/Intro Changes to authority work in RDA LC/NACO s process of updating the national authority file and the resulting process/changes in MnPALS/Aleph

3 New MARC fields 046 Special Coded dates (R) 336 Type of Content (R) 368 Other corporate body attributes (R) 370 Associated place (R) 371 Address (R) 372 Field of Activity (R) 373 Associated Groups (R) 374 Occupation (R) 375 Gender (R) 376 Family Information (R) 377 Associated Language (R) 378 Fuller form of name (NR) 380 Form of Work [used only for works] (R) 381 Other Distinguishing Characteristics of Work or Expression (R) 382 Medium of Performance (R) 383 Numeric Designation of Musical Work (R) 384 Key (NR) 678 Public Note (Was available before but discouraged, now encouraged instead)

4 Major Heading changes Violoncello -> Cello Dept. -> Department Koran -> Qur an Selections as a conventional collective title will no longer be valid under RDA as the preferred title for a work, only as the preferred title for parts of a work. The program will identify headings that use Selections and change to Works. Selections as appropriate.

5 Bible heading changes Authority records for parts of the Bible containing the abbreviations O.T. or N.T. will be modified to spell out the abbreviations Old Testament or New Testament unless the heading represents an individual book of the Bible (when Old Testament or New Testament will be omitted under RDA). The change will apply to the sacred work itself, and relevant parts, not titles that merely refer to the Bible. 130 #0 $a Bible. $p Old Testament 130 #0 $a Bible. $p Genesis

6 Changes to Dates Date subfields in various types of headings (mostly $d in personal name headings and treaties) contain abbreviations that are to be spelled out under RDA. Examples include abbreviations for century and months of the year. Some abbreviations found in pre- RDA records will be replaced with words (for example, approximately for ca. and active for fl. ). A hyphen before or after the date will be used instead of the abbreviations b. and d # $a Smith, John, $d active 1631

7 Changes to Music AACR2 considered librettos musical works, RDA considers them textual works (with an optional variant access point for the composer). 040 ## $a DLC $b eng $c DLC $e rda 046 ## $k 1727? $2 edtf 110 1# $a Cassini, Vincenzo, $d 1677?- $t Arianna 370 ## $g Venice, Italy 380 ## $a libretto 410 1# $a Marcello, Benedetto, $d $t Arianna. $s Libretto 670 ## $a New Grove dictionary of music WWW site, July 19, 2010 $b (under Marcello, Benedetto: Arianna (intreccia scenico musicale), Cassani, Venice, about 1727)

8 More Music changes this could go on forever If the access point representing a musical work with a distinctive title is the same as or similar to an access point representing a different work, or to an access point representing a person, family, corporate body, or place, add: either a) a term indicating medium of performance (see 6.15) or b) another distinguishing characteristic of the work (see 6.6) 110 1# $a Debussy, Claude, $d $t Images, $m piano not 110 1# $a Debussy, Claude, $d $t Images (Piano work)

9 Changes to Treaties AACR2 made distinctions between treaties of 1-3 parties and treaties of 4+ parties. RDA does not Bilateral, trilateral and multilateral treaties have authorized access points for the signatory named first and the preferred title, using Treaties, etc. (Additional signatories optional.) 110 1# $a Canada. t Treaties, etc. d 1992 October ## $a Treaty 410 1# $a Mexico. t Treaties, etc. d 1992 October # $a United States. t Treaties, etc. d 1992 October #0 $a North American Free Trade Agreement d (1992 October 7)

10 LC/NACO process for updating the national authority file

11 Preparation AACR2 & RDA Acceptable Heading Categories and Acceptable Headings Implementation PCC task groups reviewed LC/NACO authority file and devised implementation plan for changes. Over 95% of existing authority records found acceptable for use under RDA (about 7.6 million) About 5% needed some kind of action Some require review by a cataloger (Phase 1) Some could be made acceptable by automated processes (Phase 2)

12 Phase 1 July 30 - Aug 20, field THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED was added to authority records requiring review by a cataloger (ones that may or may not be RDA-acceptable, or need some kind of change that could not be done mechanically).

13 Phase 2 March 2013 Authority records that could be mechanically changed to make them RDA-acceptable were updated automatically with a series of scripts and macros. Dept. Department Koran Qur an ca approximately 1535

14 Phase 3??? The 95% of authority records found to be RDAacceptable that were not touched in Phases 1-2 are still coded AACR2 (can be identified by their lack of the 667 THIS 1XX FIELD CANNOT BE USED UNDER RDA ) will eventually be recoded as RDA. It is most likely that this change will occur over the span of multiple years in order to make the processing of these records acceptable to NACO nodes and local authority files. PCC , 3/5/13

15 Three types of records currently in LC/NACO authority file AACR2 and pre-aacr2 authority records that are not acceptable for use under RDA with 667 THIS 1XX FIELD CANNOT BE USED UNDER RDA added in Phase 1 (need to be reviewed and updated to RDA by catalogers) Authority records that are explicitly coded as RDA (newly created RDA authority records; authority records updated to RDA by catalogers or Phase 2 mechanical processes) AACR2 authority records that are acceptable for use under RDA (will eventually be recoded as RDA in Phase 3)

16 Bibliographic record changes (BFM) ongoing now (April 2013) On April 8, 2013, LC began to make changes to access points in bibliographic records that were affected by the Phase Two changes to the LC/NACO Authority File. All 1XX, 6XX, , or 8XX access points will be changed according to the Phase Two specifications for name authority records (spelling out Dept., N.T., O.T., arr., etc.). PCC 4/11/13

17 LCSH revisions due to RDA ongoing now (April 2013) The RDA Phase 2 changes to the name authority file were completed on March 27, 2013, so the Library of Congress Policy and Standards Division will now begin to update LCSH authority records. PSD expects to complete the project by the end of April LC PSD , 3/29/2013 Includes phrase headings & subdivisions based on names/titles: Medicine in the Koran Medicine in the Qurʼan Families Koranic teaching Families Qurʼanic teaching Does not include other LCSH authority records containing elements that deviate from RDA practice: United States History Colonial period, ca

18 Undifferentiated names Undifferentiated name headings can exist under RDA, but need to be phased out because we need to change our paradigm from name headings/records defined by unique text strings to unique identities. PCC Task Group on the Creation and Function of Name Authorities in a Non-MARC Environment is exploring the issue - report to appear soon.

19 Update process and changes in MnPALS/Aleph

20 Preparation Updates to bib tables and indexes Installing Aleph service packs containing fixes Support Incidents (SIs) submitted to Ex Libris

21 Loading Phase 1 Records Done nothing much to do or report since the headings (1XX fields) in these authority records had not been changed.

22 Loading Phase 2 Records Authority records updated in Phase 2 were distributed over a period of four weeks. As of right now, 2 weeks worth of these records have been loaded and indexed in the Aleph development server (none in production yet).

23 Loading Phase 2 Records Spot-checking headings in development server to identify problems Headings that should have flipped but didn t Headings that should not have flipped but did Headings that flipped incorrectly Waiting for Ex Libris to respond to SIs

24 Problems We re Looking For Some RDA-updated headings that might not flip correctly spot-checking in process Selections Works. Selections Koran Qur an Bible (O.T., N.T.) Violincello Cello fl. active d

25 Spot-checking

26 Spot-checking

27 Problems Identified (Sometimes) when an author/title heading includes a subfield $d as part of the author's name heading, it gets moved to after the subfield $t for the title PALS investigating Many incorrectly formatted Bible and Qu ran headings that do not flip may require clean-up

28 Problems Identified RDA descriptive access point: Brown (Family : $g Brown, John Harrison, ) LCSH: Brown family When a bib with a family name descriptive access point in RDA form is saved, Aleph flips it to the LCSH form (even though LCSH authority record fixed field settings should prevent them from flipping descriptive access points). PALS investigating, SI submitted to Ex Libris

29 When to Change AACR(2) authority records to RDA

30 If you re not in NACO Whether you re creating or updating a bibliographic record in AACR2 or RDA, always use the authorized forms found in 1XX fields of the authority records corresponding to your access points. (Whether those authority records are coded as AACR2 or RDA, and even if they have a 667 field saying THIS 1XX FIELD CANNOT BE USED UNDER RDA )

31 If you re in NACO If you use an access point in an RDA bibliographic record with an authority record that has an 667 field saying THIS 1XX FIELD CANNOT BE USED UNDER RDA (from Phase 1), update that authority record to RDA and recode it. (PCC catalogers must do this.) If you use an access point in an RDA bibliographic record with an AACR2 RDAacceptable authority record, you are strongly encouraged (but not required) to evaluate and recode it to RDA.

32 If you re in NACO When using an AACR2 1XX heading as the base element in an extended RDA authorized access point (such as a name-title or subordinate body record), the AACR2 authority record must be recoded to RDA. If the evaluation and re-coding of an existing authority record results in a change to the 1XX field, and that 1XX is also used as a 5XX field in another record, the 5XX field in the other record must be changed per NACO Normalization rules and vice versa.

33 Additional Resources Summary of Programmatic Changes to the LC/NACO Authority File PCC Post RDA Test Guidelines %20Test%20Guidelines.html Changes from AACR2 to RDA: A Comparison of Examples Program for Cooperative Cataloging and RDA FAQ (April 1, 2013 update) RDA-FAQ%20Update% doc