<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>Some NACO remeinders:<br></div><div><br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Paul Frank" <pfrank@LOC.GOV><br><b>To: </b>PCCLIST@LISTSERV.LOC.GOV<br><b>Sent: </b>Thursday, April 3, 2014 7:47:56 AM<br><b>Subject: </b>Re: [PCCLIST] Guidelines for updating personal names with 667 note<br><div><br></div><style><!--
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Lucida Sans Unicode";
panose-1:2 11 6 2 3 5 4 2 2 4;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.italic
{mso-style-name:italic;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><div class="WordSection1"><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Hi Vicki,</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">You are doing the right thing. </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">The presence of a 667 note </span><span style="color:#1F497D" data-mce-style="color: #1f497d;">“THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED” in a NACO record means, at the time of re-coding to RDA, that you should evaluate the usages recorded in the 670 field(s) of the record and verify that the preferred name is based on the predominant usage according to the RDA instructions 9.2.2, Preferred name of the person. </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">In fact, this evaluation applies to all headings being re-coded to RDA. See the <a href="http://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html" target="_blank" data-mce-href="http://www.loc.gov/aba/pcc/rda/PCC%20Post%20RDA%20Test%20Guidelines.html">PCC Post RDA Test Guidelines,</a> Updates to Existing Records, 3): </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">“</span><span style="color:#1F497D" data-mce-style="color: #1f497d;">If using an RDA acceptable heading in PCC cataloging, PCC catalogers are <strong><span style="font-family:"Calibri","sans-serif"" data-mce-style="font-family: 'Calibri','sans-serif';">strongly encouraged</span></strong> to evaluate and recode the authority record to RDA whenever possible. “Evaluate” means you should check the usage(s) of the entity as recorded in the 670 field(s) of the authority record and assess the correctness of the heading based on the usages recorded.” </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">LC-PCC PS 9.19.1.4 applies only to a fuller form of name, not to the preferred name itself. </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Evaluation of the usages of a name and any resultant change to the 1XX would fall under the “unless otherwise changing an existing heading” clause in the LC-PCC PS. </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Paul</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Paul Frank</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Acting Coordinator, NACO and SACO Programs</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Cooperative Programs Section</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Cooperative and Instructional Programs Division</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Library of Congress</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">101 Independence Ave., SE</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">Washington, DC 20540-4230</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;">202-707-1570</span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"><a href="mailto:pfrank@loc.gov" target="_blank" data-mce-href="mailto:pfrank@loc.gov">pfrank@loc.gov</a></span><br data-mce-bogus="1"></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><br></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><p class="MsoNormal"><span style="color:#1F497D" data-mce-style="color: #1f497d;"> </span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in" data-mce-style="border: none; border-top: solid #B5C4DF 1.0pt; padding: 3.0pt 0in 0in 0in;"><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" data-mce-style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"" data-mce-style="font-size: 10.0pt; font-family: 'Tahoma','sans-serif';"> Program for Cooperative Cataloging [mailto:PCCLIST@LISTSERV.LOC.GOV] <b>On Behalf Of </b>Brueck, Vicki<br><b>Sent:</b> Thursday, April 03, 2014 9:11 AM<br><b>To:</b> PCCLIST@LISTSERV.LOC.GOV<br><b>Subject:</b> [PCCLIST] Guidelines for updating personal names with 667 note</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal">Hi all,</p><p class="MsoNormal"> </p><p class="MsoNormal">In addition to the rest of my colleagues answers, I would like to hear Robert Maxwell and Paul Frank’s answer on this question.</p><p class="MsoNormal"> </p><p class="MsoNormal">There still seems to be considerable confusion about how to deal with updating personal name authority records that have the 667 note “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED” particularly those where the heading does not reflect the usages. In the document: Summary of Programmatic changes to the LC/NACO authority file: what LC-PCC RDA catalogers need to know, page 2 is the following statement regarding authority records with that note:</p><p class="MsoNormal"> </p><p class="MsoNormal">“RDA-trained PCC catalogers encountering a name authority record (NAR) with</p><p class="MsoNormal">this 667 field should evaluate the 1XX field, and the remainder of the authority</p><p class="MsoNormal">record. If the evaluation determines that the existing 1XX field can be used</p><p class="MsoNormal">under RDA as given, the cataloger should remove the 667 field, add any</p><p class="MsoNormal">additional non-heading fields, and re-code the record to RDA. If the evaluation</p><p class="MsoNormal">determines that the existing 1XX needs to be updated to be made acceptable for</p><p class="MsoNormal">use under RDA, the cataloger should revise the heading, make a reference from</p><p class="MsoNormal">the former heading when applicable, remove the 667 field, add any additional</p><p class="MsoNormal">non-heading fields of their choosing, and re-code the record to RDA.”</p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="text-decoration: underline;" data-mce-style="text-decoration: underline;">However LC-PCC PS for RDA 9.19.1.4 states</span></p><p class="MsoNormal">Existing authority records</p><p class="MsoNormal"><span class="italic"><i><span style="font-size:11.5pt;font-family:"Arial Unicode MS","sans-serif";color:black;background:#EFF1EA" data-mce-style="font-size: 11.5pt; font-family: 'Arial Unicode MS','sans-serif'; color: black; background: #EFF1EA;">LC practice/PCC practice for Optional addition:</span></i></span><span class="apple-converted-space"><span style="font-size:11.5pt;font-family:"Arial Unicode MS","sans-serif";color:black;background:#EFF1EA" data-mce-style="font-size: 11.5pt; font-family: 'Arial Unicode MS','sans-serif'; color: black; background: #EFF1EA;"> </span></span><span style="font-size:11.5pt;font-family:"Arial Unicode MS","sans-serif";color:black;background:#EFF1EA" data-mce-style="font-size: 11.5pt; font-family: 'Arial Unicode MS','sans-serif'; color: black; background: #EFF1EA;">Unless otherwise changing an existing heading (e.g., conflict), do not change an existing AACR2 or RDA heading merely to add or remove a fuller form of name.</span></p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">I’ve read the documentation and asked questions at ALA annual in PCC meetings, but the confusion still seems to exist. So I am hoping that this email and its responses can give some further guidance. When I am confronted by a personal name authority record with this 667 note should I check all usages of a personal name in OCLC (in my case) and if the 100 does not match the usages should I revise it to reflect the actual usages on bib records? Or should I instead follow the LC-PCC PS which says not to change an existing record merely to add or remove a fuller form of name? Does the presence of that 667 note mean that I should pretend that I am establishing this name for the first time and make the 100 match the usages and if that means changing the 100 field I should do so? Or follow the more conservative bent of the Policy statement and not change the 100 to add or remove a fuller form of name?</p><p class="MsoNormal"> </p><p class="MsoNormal">To give a concrete example, I recently updated the following AACR2 compatible authority record (Rules d) with that 667 note:</p><p class="MsoNormal">LCCN: n 79021770. </p><p class="MsoNormal">Originally: 100 1_Burlage, Henry Matthew, <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d 1897-1978</p><p class="MsoNormal"> </p><p class="MsoNormal">There are 71 bib records in OCLC and here are the usages:</p><p class="MsoNormal">Henry M. Burlage: 52</p><p class="MsoNormal">H. M. Burlage: 7</p><p class="MsoNormal">Henry Matthew Burlage: 2</p><p class="MsoNormal">No usage: 10</p><p class="MsoNormal"> </p><p class="MsoNormal">Overwhelmingly his preference is Henry M. Burlage, and so following my understanding of the Programmatic changes document I changed the 100.</p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="text-decoration: underline;" data-mce-style="text-decoration: underline;">Here’s the current authority record</span>:</p><p class="MsoNormal">010 n 79021770</p><p class="MsoNormal">040 DLC <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>b eng <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>e rda <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>c DLC <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d NmU <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d NcU <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d DLC <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d Nc</p><p class="MsoNormal">046 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>f 18970523 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>g 19781006</p><p class="MsoNormal">1001 Burlage, Henry M., <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d 1897-1978</p><p class="MsoNormal">370 Rensselaer (Ind.) <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>2 naf</p><p class="MsoNormal">372 Pharmacy <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>2 lcsh</p><p class="MsoNormal">374 College teachers <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>2 lcsh</p><p class="MsoNormal">375 male</p><p class="MsoNormal">377 eng</p><p class="MsoNormal">378 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>q Henry Matthew</p><p class="MsoNormal">4001 Burlage, H. M., <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d 1897-1978 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>w nne</p><p class="MsoNormal">4001 Burlage, Henry Matthew, <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>d 1897-1978 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>w nne</p><p class="MsoNormal">670 His Fundamental principles and processes of pharmacy, 1944.</p><p class="MsoNormal">670 Pharmacy's foundation in Texas, c1978: <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>b t.p. (Henry M. Burlage)</p><p class="MsoNormal">670 Marquis who's who WWW site, Jan. 14, 2011 <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>b (Henry Matthew Burlage; b. May 23, 1897, Rensselaer, Ind., d. Oct. 6, 1978; professor of pharmacy)</p><p class="MsoNormal">670 OCLC, April 1, 2014: <span style="font-family:"Lucida Sans Unicode","sans-serif"" data-mce-style="font-family: 'Lucida Sans Unicode','sans-serif';">ǂ</span>b (access points: Burlage, Henry Matthew, 1897-1978; Burlage, Henry Matthew; Burlage, Henry M. (Henry Matthew), 1897-; Burlage, Henry M.; Burlage, H. M.; usages: Henry M. Burlage, Henry Matthew Burlage, H.M. Burlage)</p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">So should I change the 100 to match the usages, or not change it since it only involves a fuller form of name?</p><p class="MsoNormal"> </p><p class="MsoNormal">I greatly appreciate all of your comments,</p><p class="MsoNormal">Vicki</p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal">Vicki Brueck</p><p class="MsoNormal">Senior Cataloger</p><p class="MsoNormal">Resource Management Services Branch</p><p class="MsoNormal">State Library of North Carolina</p><p class="MsoNormal">4641 Mail Service Center</p><p class="MsoNormal">Raleigh, N.C. 27699-4641</p><p class="MsoNormal"><a href="mailto:vicki.brueck@ncdcr.gov" target="_blank" data-mce-href="mailto:vicki.brueck@ncdcr.gov">vicki.brueck@ncdcr.gov</a><br data-mce-bogus="1"></p><p class="MsoNormal">Office: (919) 807-7451 Fax: (919) 733-1843</p><p class="MsoNormal"><i> </i></p><p class="MsoNormal"><i>E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law "NCGS.Ch.132" and may be disclosed to third parties by an authorized state official.</i></p><p class="MsoNormal"><i> </i></p><p class="MsoNormal"><span style="font-family:"Times New Roman","serif";color:black" data-mce-style="font-family: 'Times New Roman','serif'; color: black;"><img id="Picture_x0020_1" src="cid:image001.jpg@01CF4F27.B2376F50" alt="NCDCRlogo319px96dpi" data-mce-src="cid:image001.jpg@01CF4F27.B2376F50" width="319" height="98" border="0"><img id="Picture_x0020_2" src="cid:image002.gif@01CF4F27.B2376F50" alt="slnc-logo-180-wide" data-mce-src="cid:image002.gif@01CF4F27.B2376F50" width="180" height="64" border="0"></span></p><p class="MsoNormal"> </p></div></div><div><br><br></div><div><br></div><div>-- <br></div><div><span name="x"></span>Heidi G. Lerner<br>Metadata Librarian for Hebraica and Judaica<br>Metadata Development Unit<br>Stanford University Libraries<br>Stanford, CA 94305-6004<br>e-mail: lerner@stanford.edu<br>ph: 650-725-9953<br>fax: 650-725-1120<br><span name="x"></span><br></div></div></body></html>