You are correct: you can continue to contribute new AACR2 NARs or updated AACR2 NARs through March 31, 2013, PCC Day One for RDA Authority Records, the point after which all new authority records entering the LC/NACO Authority File must be coded RDA, and all access points on bibliographic records coded “pcc” must be RDA.
Between now and then, or between now and the time you take the RDA in NACO training and begin creating and updating RDA NARs, please continue doing what you have been doing all along with AACR2 NARs: you may add 670s, add or revise 4XX and 5XX fields, and revise 1xx fields (but only if allowed under current NACO AACR2 policies -- keeping in mind DCM Z1 1XX section: "In order to minimize the impact of database maintenance with associated bibliographic records and/or name/title authority records catalogers are urged to refrain from making unnecessary changes to 1XXs."
Thanks for asking-- I am sure others have the same questions.
Cooperative Programs Section
Cooperative and Instructional Programs Division
Library of Congress
101 Independence Ave., SE
Washington, DC 20540-4230
Thanks for posting this information, Paul. I’ve read through the “Summary of Programmatic Changes…” document, and I’m still puzzled. We’re not yet trained for RDA NACO, so we’re still contributing NARs using AACR2. It’s my understanding that we can continue to contribute new AACR2 NARs until the March 31, 2013 change-over date. After reading “Summary of Programmatic changes…” what’s not as clear is what sorts of changes we should be making to existing AACR2 (or AACR1) NARs during this interim period. I presume it’s okay to add 670 information. Is it also okay to add/revise 4xx and 5xx fields? What about revising 1xx fields?
David Procházka | Music/Special Materials Cataloger | The University of Akron | Bierce Library 261C | Akron, Ohio 44325-1712 | [log in to unmask] | 330-972-6260
There have been a lot of questions on PCC RDA NACO issues lately – thanks for being so careful in your NACO work. Your conscientious approach helps to facilitate the RDA transition of the LC/NACO Authority File.
But along with so many changes – and with all of them taking place simultaneously -- it is very easy to become confused about what can and cannot be done in the LC/NACO Authority File.
I hope this message helps to eliminate some of that confusion.
I am not a policeman and I am not the reassuring voice of reason (alas), but I do receive a lot of questions and comments about what is going on in the NACO Authority File, and it makes me think that perhaps some sort of clarification on multiple topics is needed.
In March 2012, the PCC Task Group to Formulate or Recommend PCC/NACO RDA Policy on Authority Issues recommended NACO policies and best practices on authority issues in the RDA environment. These policies and best practice recommendations were reviewed by the PCC Policy Committee and either approved as submitted, or approved with revisions. All the approved policies are in force right now. The RDA Toolkit, the LC-PCC Policy Statements, and the Descriptive Cataloging Manual (DCM) Z1 are on track to be updated in October to reflect the final PCC-approved decisions on the recommended NACO policies and best practices.
Until official NACO documentation is updated, PCC NACO catalogers should consult the Post RDA Test Guidelines and consider the information on this page official PCC NACO documentation in the interim period.
· You may re-code an AACR2 authority record to RDA if the NAR does NOT contain a 667 note reading: “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED” and if the 1XX is already acceptable under RDA instructions and current PCC policy (see Post RDA Test Guidelines). At the time of the re-coding, you may optionally add additional fields (046, 37X, etc.) or 670 citations to the authority record.
· You may reevaluate and re-code an AACR2 authority record to RDA if the NAR DOES contain a 667 note reading: “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED” The 1XX may need to be adjusted to conform to RDA instructions and current PCC policy (see Post RDA Test Guidelines). At the time of the reevaluation and the re-coding, please remember that many of the records with 667 notes are coded pre-AACR2 or AACR2 compatible, or are coded AACR2 but the RDA preferred form of name may be different. These 1xx’s should be analyzed to determine the RDA preferred form of name before re-coding the authority record to RDA. This means that you may need to search in your database of entry, and/or you may need to evaluate the existing 670 citations to determine the preferred name. It is not enough to take a quick glance at the 1xx, accept what you see, and then re-code to RDA. At the time of the re-coding, you may optionally add additional fields (046, 37X, etc.) or 670 citations to the authority record.
· Some AACR2 authority records whose 1XX is NOT suitable for use under RDA will NOT include a 667 field reading “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED” These records will be mechanically reevaluated and re-coded to RDA in 2013. Please exercise restraint in reevaluating and re-coding these records to RDA now. Many of these records reside in large hierarchies that will need to be re-coded together— let’s let the machine take care of these and save us all some time.