LISTSERV 16.0 - PCCLIST Archives

On Wednesday, April 25, 2012, the PCC Policy Committee supported a recommendation (Alternate Scenario 3) on the redistribution of records in the LC/NACO Authority File in preparation for PCC Day One for Authority Records, March 31, 2012. The recommendation was drafted by the PCC Acceptable Headings Implementation Task Group, chaired by Gary Strawn.

This decision was announced at the just-concluded PCC Operations Committee meeting, where the Secretariat handed out two explanatory documents, pasted below. Detailed questions should be directed to the Task Group. -- Linda

Head, Metadata Services Department

UC San Diego Libraries and

Chair, Program for Cooperative Cataloging, 2011-12

RDA Recoding of the LC/NACO Authority File:

Recommendations of the PCC Acceptable Headings Implementation Task Group

On Wednesday, April 25, 2012, the PCC Policy Committee supported the recommendation below (“Alternate 3”) on the redistribution of records in the LC/NACO Authority File in preparation for PCC Day One for RDA Authority Records, March 31, 2013. The recommendation was drafted by the PCC Acceptable Headings Implementation Task Group, Gary Strawn, Chair.

Recommendation

After consideration of several alternate schemes (and programmatic experimentation with them), and after consultation with staff at the Library of Congress (some of whom have been in contact with representatives of the NACO nodes), the present task group recommends that PCC consider the adoption of the following alternate implementationscheme (called Alternate 3 in the original document prepared by the task group), instead of the scheme originally proposed by the earlier task group. This scheme consists of two phases:

Records whose 1XX is not suitable for use under RDA without review (pre-AACR2, AACR2-compatible and certain AACR2 records) and which do not contain any field susceptible to an RDA-related mechanical change are reissued with an identifying 667 field. 046/378 fields are added to these records as appropriate. Approximately 313,000 authority records are involved in thisphase; this phase should take 3-4 weeks to complete.

Records containing a field susceptible to an RDA-related mechanical change are reissued as close to Day 1 as possible. Records in this group whose 1XX is not suitable for use under RDA without review (pre-AACR2, AACR2-compatible and certain AACR2 records) are labeled with an identifying 667 field. 046/378 fields are added to these records as appropriate. Approximately 328,000 authority records are involved in this phase; this phase should take 3-4 weeks to complete.

This scheme meets what the task group feels to be the minimum requirements for a successful implementation of RDA, and also satisfies the main points of dissatisfaction with the original scheme (records are only reissued once; records are not reissued solely to re-code them from AACR2 to RDA). This scheme appears to the group to achieve these critical goals while having the least possible impact on consumers of LC/NACO authority records.

The proposed alternate scheme does of course bring with it at least one important compromise: although this scheme eventually achieves the goal of labeling with a 667 field all records whose 1XX is not suitable for use under RDA, it does not achieve this goal until the completion of the second phase. Some records in this category are solabeled in phase 1, and the remaining are so labeled in phase 2. In the interval between phases 1 and 2, those working with records in the LC/NACO Authority File must be aware that some records whose 1XX is not suitable for use under RDA are not yet so labeled, and behave appropriately if the entity represented by the authority record is involved in some aspect of RDA-related work. This scheme does also not involve the addition of 046 and 378 fields to all relevant records; these fields are only added if a record is re-issued for another purpose.

April 27, 2012

RDA Recoding of the LC/NACO Authority File:

Recommendations of the PCC Acceptable Headings Implementation Task Group

•

Late Spring or early Summer 2012:

•

Pre-AACR2 and AACR2-compatible records not requiring a mechanical change to any 1XX, 4XX or 5XX field will be re-distributed to add a 667 field reading “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN REVIEWED INDIVIDUALLY."

•

Any AACR2 record not requiring a mechanical change to any 1XX, 4XX or 5XX field and whose 1XX field contains elements not compatible with RDA are labeled with a 667 field reading "THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL IT HAS BEEN UPDATED." (The exact wording of the 667 fields is not yet settled; suggestions welcome.) Further changes (such as the addition of fields 046, 378 and 382-384) are made to records that are otherwise re-issued.

•

Between Summer 2012 and Spring 2013: Because only some, and not all, records whose 1XX is not suitable for use under RDA will be identified in Summer 2012, PCC NACO catalogers are responsible for deciding on their own whether or not the 1XX field in an authority record is suitable for use in a PCC bibliographic record.

•

Spring 2013: Authority records requiring some mechanical change to any 1XX, 4XX or 5XX field are so changed. Any pre-AACR2 and AACR2-compatible records, and any AACR2 records whose 1XX field contains elements not compatible with RDA even after mechanical changes, are labeled with the 667 fields described above. Further changes (such as the addition of fields 046, 378 and 382-384) are made to records that are otherwise re-issued.

•

RDA-trained NACO catalogers may reformulate non-RDA headings to RDA authorized access points and recode the records to RDA (008/10 = z, 040 $e rda) as needed.

•

AACR2 records whose 1XX is suitable for use under RDA will not be re-coded as RDA. RDA-trained NACO catalogers may optionally re-code these records to RDA.

•

AACR2 1XX fields suitable for use under RDA may be used as the base element in an extended RDA heading.