1. NACO Updates Since April 2017
CEAL Pre-Conference Workshop
Washington, D.C., March 20, 2018
Jessalyn Zoom
Library of Congress

2. NACO Normalization and SARs (DCM Z1 Introduction)
New information added to NACO Normalization and SARs
This “Introduction” section covers the following topics:
Name authority records (NARs)
Series authority records (SARs)
Justification of access points and elements
NACO normalization
Should an SAR be made?
How many SARs should be made?
Series statement appears only on ECIP data view sheet at galley stage
Searching series

3. 5XX Form (DCM Z1 Introduction)
All access points used in 5XXs fields must also be represented in the authority file. For example, when a cataloger adds a 500 field in a NAR for a work to show a relationship between a work and a person, the access point in the 500 field must also be established.

5. “Undifferentiated” Name Authority Records Coded as Differentiated (DCM Z1 008/32)
Revised to include procedures on “undifferentiated” name authority records coded as differentiated.
NACO catalogers:
Create a new NAR representing only one person, applying the instructions for conflict in new authority records.
Add a 667 field to the new NAR as is done for persons formerly on undifferentiated name records.
667 ## $a Formerly on undifferentiated name record: [LCCN of undifferentiated name record]
Transfer the 670 pertaining to that person from the “undifferentiated” name record to the new NAR and edit as necessary.
In the “undifferentiated” NAR, do not change the 008/10 value, and do not add or remove subfield $e “rda” in the 040 field.

6. “Undifferentiated” Name Authority Records Coded as Differentiated (DCM Z1 008/32)
NACO catalogers (continue):
If the “undifferentiated” NAR still contains multiple identities:
Add a 667 field to the undifferentiated NAR:
667 ## $a Record contains multiple identities; reported to LC for resolution, [date].
Report the undifferentiated NAR for deletion to LC will create new NARs for each remaining identity, delete the “undifferentiated” NAR and add the LCCN of the deleted NAR in field 010 subfield $z of the last newly created NAR.
If the “undifferentiated” NAR now contains one identity:
Add that information in the 667 note on the “undifferentiated” record to assure that a duplicate NAR will not be created:
667 ## $a Last identity on undifferentiated record; reported for deletion.
Report the undifferentiated NAR for deletion to LC will create new replacement NAR and delete the old NAR. In the new NAR, LC will add a 667 note and add the LCCN of the deleted NAR in field 010 subfield $z.

7. “Undifferentiated” Name Authority Records Coded as Differentiated

8. New NAR Created

9. Undifferentiated NAR Reported for Deletion

10. New Replacement NAR created by LC

11. MARC 372 Field – Field of Activity
Revised to clarify how to record a field of activity from LCSH with a subdivision.
If using an LCSH subject heading string for field of activity, replace the subfield coding for the subdivision(s) with two hyphens and close up the spaces between the main heading and subdivision(s).
372 ## $a Japan--History $2 lcsh
If using an entity from the LC/NAF for field of activity, remove any subfield coding not authorized for use in the 372 field.
130 #0 $a Bible. $p New Testament
372 ## $a Bible. New Testament $2 naf

12. MARC 373 Field – Associated Group
Revised to clarify how to record subordinate bodies.
Subfield coding for subordinate bodies is not used in the 373 field.
110 2# $a United States. $b Congress. $b Senate
373 ## $a United States. Congress. Senate $2 naf

13. MARC 373 Field – Associated Group
Subfield $s-Start period and Subfield $t-End period
Best practice: Input dates using the Gregorian calendar in the form yyyy. If more specific dates are necessary, consider recording them in another field (e.g., 670, 678). It is not necessary to reformulate dates in existing NARs to conform to this practice.
373 ## $a Stanford University. Asia-Pacific Research Center $2 naf $s 2018

14. MARC 381 Field – Other Distinguishing Characteristics of Work or Expression
Clarified practice on recording elements applicable to the 381 field and another 3XX field
Some terms recorded for other distinguishing characteristic of work or expression may be appropriate to record in field 381 and another MARC field for which there is no corresponding RDA element.
130 #0 $a Bai nian shu xi (Guangdong ren min chu ban she)
430 #0 $a 百年書系 (Guangdong ren min chu ban she)
373 ## $a Guangdong ren min chu ban she $2 naf
381 ## $a Guangdong ren min chu ban she $2 naf
RDA has no specific element for places associated with expressions, but field 370 field $f (Other associated place) and subfield $g (Place of origin of work or expression) may be used in authority records for expressions. Some places associated with works or expressions would be considered other distinguishing characteristic of work or expression in RDA and could be recorded in the 370 field $f (Other associated place), the 381 field, or both.
130 #0 $a Asahi shinbun (Osaka, Japan)
370 ## $f Osaka (Japan) $2 naf
381 ## $a Osaka (Japan) $2 naf

15. MARC 382 Field – Medium of Performance
Revised to reflect current cataloging policies.
Record the medium of performance using terms from the LCMPT, accessible via Classification Web or LC Linked Data Service, when possible. Record the medium of performance by applying the instructions at RDA and the associated LC-PCC PS.
382 0# $b soprano voice $n 1 $a mixed chorus $2 lcmpt

16. MARC 667 Field (DCM Z1)
Added example of note for author’s request to remove date of birth.
667 ## $a Date of birth removed from all fields per author request, [date updated].

17. Ambiguous Entities (DCM Z1 Appendix 1)
Clarified policy on 667 notes in NARs.
PCC Catalogers:  If a Group 2—Subject Authority Group heading is being used as an access point, create a name authority record according to subject cataloging rules.  Add a 667 note to the NAR with the statement "Subj. Headings Manual/RDA." 
If a Group 2 Subject Heading for the same entity exists in the LCSH File create an NAR (cf. DCM Z1 Appendix 1: Ambiguous Entities, Section, 3.1) and send a notification delete the existing subject authority record.

18. Heading required As a Descriptive Authorized Access Point (DCM Z1, Appendix 1) : Group 2 Entities  

19. Heading required As a Descriptive Authorized Access Point (DCM Z1, Appendix 1) 
‡z sh
‡d DLC

20. Subfield $w Change in Authority Records in Connexion
Library of Congress generates authority records with $w in the first position in fields 4Xx and 5XX. OCLC has long displayed those $w at the end of the field, rather than at the beginning of the field.
As of Sunday, 11 March 2018, when an authority record containing $w in fields 4xx or 5xx is first displayed in OCLC interfaces, the $w will be in the first position of the field.
After the March 11 date, if you edit an existing record to replace it or create a new record to add, and $w is not already in the first position, it will automatically be moved to the first position when the record is redisplayed after being added to the database.
500 1# $w r $i Translator: $a Chōng, So-yōn
-- Info. from OCLC-Cataloging listserv

21. Thanks to the CJK NACO colleagues for their review!