<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'><br><br><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;"><b>From: </b>"Paul Frank" <pfrank@LOC.GOV><br><b>To: </b>PCCLIST@LISTSERV.LOC.GOV<br><b>Sent: </b>Thursday, June 6, 2013 7:29:16 AM<br><b>Subject: </b>Re: [PCCLIST] Incomplete dates in personal name access points<br><br><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: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;}
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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.hithighlite
{mso-style-name:hithighlite;
color:red;
font-weight:bold;}
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">Mary Charles, </span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">For the same reason(s) you might optionally add a death date to an open birth date in an authorized access point, you can optionally add a birth date to an open death date in an authorized access point. These are two exceptions to the general NACO principle that changes are not made to an authorized access points unless the authorized access point contains an error. </span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">The LC-PCC PS to document this will be published on July 9, but it is ok to apply the option now. </span><span style="color:#1F497D"></span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">Paul</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div><p class="MsoNormal"><span style="color:#1F497D">Paul Frank</span></p><p class="MsoNormal"><span style="color:#1F497D">Cooperative Programs Section</span></p><p class="MsoNormal"><span style="color:#1F497D">Cooperative and Instructional Programs Division</span></p><p class="MsoNormal"><span style="color:#1F497D">Library of Congress</span></p><p class="MsoNormal"><span style="color:#1F497D">101 Independence Ave., SE</span></p><p class="MsoNormal"><span style="color:#1F497D">Washington, DC 20540-4230</span></p><p class="MsoNormal"><span style="color:#1F497D">202-707-1570</span></p><p class="MsoNormal"><span style="color:#1F497D"><a href="mailto:pfrank@loc.gov" target="_blank">pfrank@loc.gov</a></span></p></div><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div><div 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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Program for Cooperative Cataloging [<a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">mailto:PCCLIST@LISTSERV.LOC.GOV</a>] <b>On Behalf Of </b>Lasater, Mary Charles<br><b>Sent:</b> Wednesday, June 05, 2013 10:28 AM<br><b>To:</b> <a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">PCCLIST@LISTSERV.LOC.GOV</a><br><b>Subject:</b> Re: [PCCLIST] Incomplete dates in personal name access points</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:#1F497D">Has there been any further discussion on this?</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><p class="MsoNormal"><span style="color:#1F497D">I just ran into the authority record for </span><span class="hithighlite"><span lang="EN">Breece</span></span><span lang="EN"> D'J <span class="hithighlite">Pancake</span> who died in 1979. I added his birth info to the 046 field, but would really like to ‘complete’ his dates in the 100 field of the authority record. The information was readily available. I am currently reviewing the loads of the modified Phase 2 records and ‘running into’ many records that could be changed. I am sure others are as well. By delaying a decision to add birth and well as death dates, we are missing an opportunity to make our AAPs more complete.</span></p><p class="MsoNormal"><span lang="EN"> </span></p><p class="MsoNormal"><span lang="EN">Mary Charles Lasater</span><span style="color:#1F497D"></span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div><div 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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Program for Cooperative Cataloging [<a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">mailto:PCCLIST@LISTSERV.LOC.GOV</a>] <b>On Behalf Of </b>Reser, Dave<br><b>Sent:</b> Thursday, May 02, 2013 5:28 PM<br><b>To:</b> <a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">PCCLIST@LISTSERV.LOC.GOV</a><br><b>Subject:</b> Re: [PCCLIST] Incomplete dates in personal name access points</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:#1F497D">That's an excellent question, Ryan-- we were talking about that very question here at LC yesterday! We decided it was time to move that question on to a consultation stage with the PCC/SCS and OCLC, but with the PCC Operations Committee meeting here today and tomorrow, we just haven't had a chance. </span></p><p class="MsoNormal"><span style="color:#1F497D">Thanks for raising it,</span></p><p class="MsoNormal"><span style="color:#1F497D">Dave Reser</span></p><p class="MsoNormal"><span style="color:#1F497D">LC PSD</span></p><p class="MsoNormal"><span style="color:#1F497D"> </span></p><div><div 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"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Program for Cooperative Cataloging [<a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">mailto:PCCLIST@LISTSERV.LOC.GOV</a>] <b>On Behalf Of </b>Finnerty, Ryan<br><b>Sent:</b> Thursday, May 02, 2013 5:15 PM<br><b>To:</b> <a href="mailto:PCCLIST@LISTSERV.LOC.GOV" target="_blank">PCCLIST@LISTSERV.LOC.GOV</a><br><b>Subject:</b> Incomplete dates in personal name access points</span></p></div></div><p class="MsoNormal"> </p><p class="MsoNormal">Hi PCC-List,</p><p class="MsoNormal"> </p><p class="MsoNormal">We’ve been allowed for some time to add death dates to access points that only have an open birth date (there are tons more of these now that “b.” has been eliminated), so are we allowed to extend this thinking further and add the birth year to an access point if it only has the death year? (there are also tons of these now with the elimination of “d.”)</p><p class="MsoNormal"> </p><p class="MsoNormal">In this example the birth year is already right there in the 670. I’d like to add it because the authorized access point just looks incomplete to me, but I realize that this would have ramifications for data management, OCLC’s closed dates list (would it catch these?), etc. </p><p class="MsoNormal"> </p><p class="MsoNormal">010 n 81104301 </p><p class="MsoNormal">040 DLC <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>b eng <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>e rda <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>c DLC <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d OCoLC <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d DLC</p><p class="MsoNormal">046 <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>g 1654</p><p class="MsoNormal">1001 Fabritius, Carel, <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d -1654</p><p class="MsoNormal">4001 Fabricius, Karel, <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d -1654</p><p class="MsoNormal">4001 Fabritius, Carel, <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d d. 1654 <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>w nnea</p><p class="MsoNormal">4001 Fabritius, Carolus, <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d -1654</p><p class="MsoNormal">4001 Fabritius, Karel, <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>d -1654</p><p class="MsoNormal">670 Encyc. brit., 1972 <span style="font-family:"Lucida Sans Unicode","sans-serif"">ǂ</span>b (hdg.: Fabritius, Carel (Carel [Carolus] Pietersz) 1622-1654)</p><p class="MsoNormal"> </p><p class="MsoNormal">What do you all think?</p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:gray">Ryan J. Finnerty </span><span style="color:black">|</span><span style="color:gray"> Head, Database Management & NACO Coordinator</span></p><p class="MsoNormal"><span style="color:#4F6228">UC San Diego Library </span><span style="color:#1F497D">|</span><span style="color:#4F6228"> Metadata Services Department</span></p><p class="MsoNormal"><span style="color:#4F81BD"><a href="mailto:rfinnerty@ucsd.edu" target="_blank">rfinnerty@ucsd.edu</a></span><span style="color:#1F497D"> | </span><span style="color:#4F81BD">(858) 822-3138</span></p><p class="MsoNormal"> </p><p class="MsoNormal"> </p></div></div><br></div></body></html>