<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:#0563C1;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:#954F72;
text-decoration:underline}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.EmailStyle18
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EmailStyle19
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style><style type="text/css" id="owaParaStyle"></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Brad,
<div><br>
</div>
<div>While there is some overlap in the date of existence element and the name, I am not sure that this will always mean exact duplication. In most cases (though not always) the text string in the LCNAF would be just a year span (e.g., 1801-1877), though repositories
may want to record more specific dates for the <existDates> life span (e.g., 1801 June 1 - 1877 August 29). Even if repositories were required to simplify the <existDates> entry to allow its inclusion in the heading, there would still need to be some mechanism
to indicate whether is should be included in the exports--such as a "Include in heading?" checkbox in either the <nameEntry> or <existDates> section of the record. Of these two, having the checkbox in the <nameEntry> section would probably work better in most
cases, since there is some variability between vocabularies whether the dates should be included. Looking at Mark Twain, for example, if you were adding the full VIAF record content (<a href="http://viaf.org/viaf/50566653/#Twain,_Mark,_1835-1910" target="_blank">http://viaf.org/viaf/50566653/#Twain,_Mark,_1835-1910</a>)
to an ArchivesSpace Agent record you would need to distinguish which <nameEntry>s needed to include the dates in the heading and which did not. However, even this possibility can break down since not all controlled lists use the same form of dates for the
same entity. Looking at the record for Peter Williams (<a href="http://viaf.org/viaf/282239842/#Williams,_Peter,_1935_April_7-" target="_blank">http://viaf.org/viaf/282239842/#Williams,_Peter,_1935_April_7-</a>) you can see that the date component of the different
headings varies to include "1937-", "1937.g. 14.maijs-", "1937, 14 maig-", and "1935 April 7", in addition to the many cases of no date being recorded. </div>
<div><br>
</div>
<div>In order to ensure that the exports will be correct on a consistent basis, it would seem that the simplest approach would to maintain the date qualifier field in the <nameEntry> section of the Agent record. While the <nameEntry> and <existDates> elements
maintain similar data, they are not always the same and have slightly different functions. For EAC-CPF exports, depending on the needs of the community one could either not include the date qualifiers as part of the <nameEntry> (though again this might break
the authorized form of the name), or develop a <nameEntry><part> @localType value of "date" or "dateQualifier" (if it does not already exist in best practices) so that the date qualifier could be retained. </div>
<div><br>
</div>
<div>Cory Nimer</div>
<div>Manuscripts Cataloger/Metadata Specialist</div>
<div>Brigham Young University</div>
<div>801-422-6091 <br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF720894" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org [archivesspace_users_group-bounces@lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook@lyrasis.org]<br>
<b>Sent:</b> Wednesday, June 11, 2014 6:14 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Dates in Agent record<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Good morning.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The changes Cory describes were made for several reasons, of which one was to reduce redundant data entry in the agent / name record. In our understanding the values that would be recorded in <existDates> are
analogous to the values recorded in the date qualifier in an LCNAF record and, thus, both fields could be supported by a single Dates of Existence field in the ArchivesSpace agent/name record. Is our understanding totally incorrect? If so, is restoring the
date field in the name record the only option for supporting both EAC and LCNAF?
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Brad W.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D">Bradley D. Westbrook</span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D">Program Manager</span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D"><a href="mailto:brad@archivesspace.org" target="_blank"><span style="color:#1F497D">brad.westbrook@lyrasis.org</span></a></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D">800.999.8558 x2910</span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D">678.235.2910</span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:#1F497D">bradley_d_westbrook (Skype) </span><span style="color:#1F497D"></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"; color:black"><img id="Picture_x0020_1" src="cid:image002.png@01CF854C.F205D170" alt="cid:image003.png@01CE734E.FD759D30" height="55" width="199" border="0"></span><span style="color:black"></span></p>
<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>
<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""> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>Cory Nimer<br>
<b>Sent:</b> Tuesday, June 10, 2014 8:04 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Dates in Agent record</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1F497D">Based on the EAC-CPF tag library, <useDates> is a subelement of <nameEntry> but is not considered to be part of the name itself. Rather, it is meant to indicate "the dates when the name or names were used by
the entity being described." This would allow someone to create an aggregate name record, as in allowed in the optional provisions of DACS 2<sup>nd</sup> ed. 10.3.5, while recording usage dates for the different names (though this is not compatible with LC
Name Authority File entries). Presumably, one might do the same with names recorded as variants. The <existDates> element, on the other hand, is nested in <description> and is meant to record the existence dates of the entity (e.g., date of birth, death, organization,
abolishment, etc.). The <existDates> is paralleled in MARC and the LCNAF with the 046 field, but there is currently no equivalent element for <useDates>.
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">However, neither of the date options above provide a way of recording the date qualifiers that may be part of an LCNAF authorized access point. It was possible to record this data as part of the name entry up
to release ArchivesSpace 1.0.7, but one of the changes in 1.0.9 appears to have been moving this data to a separate field from the name—to an EAC-CPF <existDates>/MARC 046 equivalent. This has also appears to have resulted in the removal of the date component
of authorized access points in exported EAD, EAC-CPF, and MARC files. </span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">While it might be possible to have the system display/export the date as part of the name, this may not produce the authorized access point as not all include date qualifiers. In order to support LCNAF name entries,
the date qualifier field from 1.0.7 would need to be restored and the moved entries copied back into the name entry for existing users. This could potentially duplicate data in some Agent records, but would ensure that the display/exports would be accurate.
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Cory Nimer</span></p>
<p class="MsoNormal"><span style="color:#1F497D">Manuscripts Cataloger/Metadata Specialist</span></p>
<p class="MsoNormal"><span style="color:#1F497D">Brigham Young University</span></p>
<p class="MsoNormal"><span style="color:#1F497D">1108 HBLL</span></p>
<p class="MsoNormal"><span style="color:#1F497D">(801) 422-6091</span></p>
</div>
<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"">
<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> [<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org</a>]
<b>On Behalf Of </b>Kottman, Miloche<br>
<b>Sent:</b> Tuesday, June 10, 2014 8:36 AM<br>
<b>To:</b> Archivesspace Users Group (<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>)<br>
<b>Subject:</b> [Archivesspace_Users_Group] Dates in Agent record</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">What is the difference between “Dates of Existence” and “Date(s) of Name Use” in a Person Agent record? In other words, which section do I but the birth and death dates needed to differentiate the heading.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">In addition, could a future version of ArchivesSpace include the date as part of the display of the name?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks,</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">--Miloche Kottman</p>
<p class="MsoNormal">University of Kansas Libraries</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>