A UTHORITY RECORD CREATION ON D AY O NE : W HAT C ATALOGERS N EED TO K NOW PCC P ARTICIPANTS ’ M EETING J ANUARY 27, 2013 Joanna Dyla Stanford University Libraries

RDA AND NACO Both AACR2 and RDA authority records accepted by the NAF New PCC bibliographic records can have either one or both AACR2 and RDA access points Follow the PCC Post RDA Test Guidelines Only RDA authority records accepted by the NAF Access points used in all new PCC bibliographic records will have to be supported by RDA NARs or be RDA- acceptable Prior to March 31, 2013 March 31, 2013 on…

P OST RDA T EST G UIDELINES 0Test%20Guidelines.html

P RIOR TO M ARCH 31, 2013 Authorized form of name and title already established in the NAF Use authorized forms in existing AACR2 or RDA authority records in both AACR2 and RDA bibliographic records

NAR S MODIFIED IN P HASE 1 Authorized form in the NAF and 667: THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED RDA catalogers: Evaluate the NAR to determine if RDA acceptable Follow Summary of Programmatic Changes to the LC/NACO Authority File: What LC-PCC RDA Catalogers need to know:

N EW MARC 21 FIELDS 0Test%20Guidelines.html

P RIOR TO M ARCH 31, 2013 No authorized form of name and/or title in the NAF RDA-trained NACO catalogers Create a new RDA authority record AACR2 NACO catalogers Create a new AACR2 authority record  Contact the PCC Secretariat to arrange for transitioning from AACR2 to RDA  Check RDA in NACO Training at ndex.html ndex.html

P RIOR TO M ARCH 31, 2013 No hybrid AACR2/RDA authorized access points AACR2 headings in extended RDA authorized access points Use an RDA-acceptable 1XX heading as the base element in an extended RDA authorized access point Re-code the AACR2 authority record to RDA

M ARCH 31, 2013 ON … Only RDA authority records will be added to the NAF Access points used in all new PCC bibliographic records must be supported by the RDA authority records or be RDA-acceptable Some guidelines in use now will continue after March 30

U NDIFFERENTIATED P ERSONAL NAR S 0Policies%20and%20Best%20Practices.html RDA catalogersAACR2 catalogers -Do not create new undifferentiated NARs -Do not add entities to existing NARs -May create new undifferentiated NARs -May add entities to existing NARs

E XISTING U NDIFFERENTIATED P ERSONAL NAR S AACR2 undifferentiated NAR in the NAF and Additional data available now for a person to differentiate the name RDA catalogers: Create a new RDA differentiated NAR for that person Remove that person from the AACR2 NAR and make appropriate edits Report BFM

C ONFERENCES Individual occurrence of an ongoing conference: AACR2 heading established and is RDA-acceptable Use it in 1XX of a new RDA NAR Re-code an existing NAR for RDA and add a 667 note per LC-PCC PS : 667 __ See also related access points for individual instances of this conference which include specific information about the number, date, or place of the individual conference.

C ONFERENCES Individual occurrence of an ongoing conference: AACR2 heading established but is not RDA- acceptable Create a new individual NAR following RDA and LC-PCC PSs Upgrade the existing NAR and re-code it for RDA. Delete the 667 note added in Phase 1 and add a 667 note per LC-PCC PS

C ONFERENCES Individual occurrence of an ongoing conference: RDA heading established for another occurrence Create a new individual NAR for the occurrence you need following RDA and LC-PCC PSs If not already in the NAF, also create a new collective NAR with a 667 note per LC-PCC PS

C ONFERENCES Individual occurrence of an ongoing conference: no NAR exists Create a new individual NAR following RDA and LC-PCC PSs Also may create a new collective NAR with a 667 note per LC-PCC PS :

RDA NACO AND C ATALOGING U TILITIES OCLC RDA guidelines: policy.htm policy.htm Prior to March 31, 2013 Both AACR2 and RDA workforms available March 31, 2013 on… Only RDA workforms will be used

RDA NACO AND C ATALOGING U TILITIES SkyRiver RDA statement: Prior to March 31, 2013: AACR2, RDA as well as custom workforms available March 31, 2013 on… Only RDA workforms will be used