| Line 116: | 
Line 116: | 
|   | === General ===    |   | === General ===    | 
|   |  |   |  | 
| − | When creating an NAR for a family name, assign value “n” in 008/32.
  | + | <span style="color:red>Do not use 008/32 code “b” (undifferentiated) in an RDA name authority record. Assign 008/32 value “a” for personal name NARs. Use code “n” for families, corporate bodies, and places. For works and expressions, assign value “a” if the access point begins with a personal name, otherwise assign value “n”.</span>  | 
|   |  |   |  | 
| − | As LC and the PCC, PFAN has agreed to the following guidelines for persons whose preferred names are identical:
  | + | <span style="color:red>In the past, personal name NARs could be coded as undifferentiated using 008/32 value “b” when the cataloger had no acceptable way of differentiating multiple persons with the same preferred name. Since then, PFAN have followed these guidelines for personal name NARs:</span>  | 
| − | * Do not use code “b” in an RDA name authority record; all personal name authority records coded RDA should be differentiated.  | + | * <span style="color:red>Do not create new undifferentiated records coded 008/32 “b”.</span> All personal name authority records <span style="color:red>coded RDA</span> should be differentiated.  | 
|   | * Do not add a new identity to an existing personal name authority record coded 008/32 “b.”  |   | * Do not add a new identity to an existing personal name authority record coded 008/32 “b.”  | 
| − |    | + | * Instead, apply [http://original.rdatoolkit.org/rdachp9-fr_rda9-5465.html RDA 9.19.1] to create a unique authorized access point for the person, using suitable additional elements.  | 
| − | Instead, apply [http://original.rdatoolkit.org/rdachp9-fr_rda9-5465.html RDA 9.19.1] to create a unique authorized access point for the person, using suitable additional elements.  |   | 
|   |  |   |  | 
|   | === Maintenance of existing undifferentiated records: ===  |   | === Maintenance of existing undifferentiated records: ===  |