Print

Print


Hi Craig,
Here is a different document that explains what is required when we evaluate and re-code:
http://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html
See instruction 3 under Updates to Existing Records.  Essentially, we are to look at the usage(s) and the source(s) (location(s)) recorded in the 670s, then make the 1XX agree with what RDA would have us do based on it/them, with respect to both choice and form of the name.  In many cases, this means there is no need to look beyond the authority record itself.  Just be sure the 1XX to reflects the 670 info in proper RDA fashion.  Ignoring for a minute that there are a couple of other problems that need to be addressed, your 1XX would become Roland Holst, A., 1888-1976  OR Roland Holst, A. ǂq(Adrianus), 1888-1976.  (9.5 says that the fuller form is core if needed to disambiguate, but you can add it if you know it even if there is no conflict.)
However, the legacy record does not do these things:
--justify the notion that Roland is part of a double surname rather than a forename
--justify his birth date
--justify the fuller form, Adrianus
To re-code this NAR as RDA, you do need to take care of these things.  The final result needs to be a record where all the elements of the 1XX are justified (plus any extras you might add in other attribute fields).  So, you will have to go beyond the record & do searching.  If your searching reveals a different pattern of usage than what the legacy record has indicated, you can adjust the 1XX to reflect it.
If you have additional questions, just let me know.
mjc

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Philip Schreur
Sent: Friday, March 01, 2013 12:44 PM
To: [log in to unmask]
Subject: Recoding of RDA Acceptable Headings

Everyone,
Opinion has been strongly divided on the proposal in the Hybrid Records Task Group report that after March 30, 2013 all headings in BIBCO and CONSER records coded RDA must be supported by authority records explicitly coded RDA.  In effect, this proposal would require the evaluation and recoding of headings considered RDA acceptable before they could be used.  After further consideration and with the help of your input, the PCC Policy Committee would like to step back slightly from this position.  Our reasons follow.

By March 30, 2013, Phases 1 and 2 of the automated editing of the LC NAF will be complete.  In Phase 1, those headings that were not RDA acceptable and could not be made so through machine manipulation had a 667 note added stating: THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED.  In Phase 2, those headings that could be made RDA conformant through machine manipulation will have been revised and recoded.  With the completion of this work, there will be three types of headings in the LC NAF: those headings explicitly coded RDA, those headings that are not RDA compliant with the above 667 note added, and those that that are RDA acceptable identifiable by the lack of the 667 note along with the coding for AACR2.  (At one point we envisioned the 95% of records in this category being recoded through automated means.)

Beginning March 31, 2013, PCC catalogers must support headings in new catalog records (or pre-RDA records that are being fully redescribed and recoded as RDA) with RDA authority records.  The debate has been whether these RDA authority records must be explicitly coded RDA or if RDA acceptable authority records can also satisfy the requirement.

In an informal evaluation at the end of 2012, four PCC libraries evaluated and recoded to RDA all RDA acceptable headings needed in their work. Approximately 5% of those headings needed their 1XX altered to become truly RDA compliant.  Although this error rate is within tolerance according to the original Authority File Task Group report, the number is still notable. Because of this, when using an RDA acceptable heading in PCC cataloging, PCC catalogers are strongly encouraged to evaluate and recode the authority record to RDA. Although the number of headings to be evaluated in a single bibliographic record may make this too burdensome, in general, the evaluation and recoding should be done whenever possible. However, if an RDA acceptable authority record is being updated for another reason (for example, to add a reference, or to add other identifying characteristics), the record must be evaluated and recoded to RDA.


Philip

--

Philip E. Schreur

Chair, Program for Cooperative Cataloging

Head, Metadata Department

Stanford University

650-723-2454

650-725-1120 (fax)