Reviewing non-RDA NARs with (and without) 667
For background and examples, see Summary of Programmatic Changes to the LC/NACO Authority File: What LC-PCC RDA Catalogers Need to Know
- Keep in mind that computer processing of Phase one could not catch all non-RDA elements in the AACR2 AAP [authorized access point]; some NARs [Name Authority Records] invalid as RDA AAPs may lack 667. See, in the next section, Personal names, item 1., an example where the NAR would lack a 667 because it would require human intervention to identify the problem.
- IMPORTANT: Did you remember to change Desc from a to z? Did you remember to insert $e rda into the 040?
- Did you remember to delete the 667 Do not use until reviewed note? Keep in mind that the presence of a 667 does not mean that the AAP requires updating automatically. The preferred name can be reinvestigated for conflict, but reinvestigation is not required (PCC-at-large 2013 Annual).
- Local policy. If an AACR2 AAP had to be updated to a different RDA form upon review, make the update and report it to Rick to notify LC for BFM [bibliographic file maintenance]. For local maintenance, notify Eva Bolkovac if there are too many headings to update manually in Orbis.
- Updating AAPs. General principle: as long as the preferred name/qualifier combination is consistent with RDA, leave the AAP as is, even if the qualifier would be unnecessary when establishing a new AAP. For example, if the AAP has a fuller form qualifier but the unqualified name has no conflict, leave the AAP form as is and re-code the NAR as rda.
- Be sure to review 4xxs.
- The reference may need to be qualified or revised to RDA form.
- A new reference added at the time of updating might conflict with an established AAP. It’s possible the OCLC software will catch the conflict, but you will still need to update the 4xx to break it.
- Don’t remove 4xxs already in the record, even though most 4xxs are no longer mandatory. But keep in mind that you will still need to evaluate existing references for consistency with RDA.
- If there are non-latin script 4xxs, be sure the ref code is “b” and there is a 667 Non-Latin script reference(s) not evaluated. Just to be clear: use the plural form if there is more than one non-Latin script reference; if there is only one, don’t include (s).
- Phase 2 computer updates made to AACR2 records. Do not assume a record updated under Phase 2 is valid RDA. Do not assume the Phase 2 program fixed all of the elements that conflict with RDA. Correct any oversights. The Phase 2 updates that were made are:
- Addition of 3xx fields: 046, 378. Also, for music: 382, 383, 384
- Deletion of 7xx fields for what testers considered to be the “pure” RDA form (which now conflicts with some of the LC PCC Policy Statement guidelines)
- Abbreviations spelled out and/or substituted by English language equivalents: Dept., cent., fl. [RDA: active], ca. [RDA: approximately], Jan., Feb., etc. For music: acc., arr., unacc., violoncello.
- b. and d. replaced by hyphens (this was probably also applied to pcc RDA NARs created prior to Day One)
- Occupation qualifiers capitalized with parentheses added: Oyster, $c poet becomes Oyster $c (Poet)
- Old Testament, New Testament spelled out; O.T./N.T. removed from AAPs for individual books; Koran replaced by Qu’ran.
- Selections converted to Works. Selections. Subfield $f for date of Work or Selections was removed if there.
- Local policy. New MARC Authority Fields. When updating a previously established AACR2 NAR, add 046 information for birth/death or founding/ending if readily available. The other new fields are not mandatory as long as the core information has been recorded somewhere in the NAR. Include any information that could be used to identify or differentiate the person or other entity. Follow current Z1 and PCC guidelines for entry conventions. See also the Short Checklist site for examples and current instructions.
- Local policy. Get a second opinion:
- Music AAPs
- Treaty AAPs