<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
I'd like to add, as someone previously on the Dev-Pri group, if you have interest in the feature that Benn pointed to which he submitted, clicking on Watch, and Voting for the ticket (available after logging into Jira near the upper right portion) will greatly
help in getting this ticket completed.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
I can see that the ticket was already passed into ready for implementation back in February and is waiting to be picked up but with more activity, a developer might pick it up faster.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);" class="elementToProof">
Regards,
<div>Edgar</div>
</div>
<div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div id="Signature">
<div>
<div></div>
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div style="font-family:Tahoma; font-size:13px">
<p class="p1"><span class="s1" style="font-size:10pt; font-family:Calibri,Helvetica,sans-serif"><b style="">Edgar Garcia</b></span></p>
<p class="p1"><span class="s1" style="font-size:10pt; font-family:Calibri,Helvetica,sans-serif">Senior Software Developer</span></p>
<p class="p1"><span style="font-size:10pt; font-family:Calibri,Helvetica,sans-serif">IT Infrastructure</span></p>
<p class="p1"><span class="s1" style="color: rgb(118, 62, 155); font-size: 10pt; font-family: Calibri, Helvetica, sans-serif;">Northwestern University Libraries</span></p>
<p class="p1"></p>
<span style="font-size:10pt; font-family:Calibri,Helvetica,sans-serif"></span>
<p class="p1"><span class="s1" style="font-size:10pt; font-family:Calibri,Helvetica,sans-serif">Evanston, IL</span></p>
</div>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Benn Joseph
<benn.joseph@northwestern.edu><br>
<b>Sent:</b> Thursday, October 13, 2022 1:09 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:"Segoe UI Symbol"}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle21
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:70.85pt 70.85pt 70.85pt 70.85pt}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal">We’re largely trying to avoid using date expressions too, for the same reasons—and
<a href="https://urldefense.com/v3/__https://archivesspace.atlassian.net/browse/ANW-1273__;!!Dq0X2DkFhyF93HkjWTBQKhk!WYkOLHT2VKrv8grDaKj41Y0CRoQkRla7LnwKYEaQrJ8HBuB81B7cQ6wDh-poRPhf5N4BaPuSh-AR6akjNgcdy1tTqFfJxjCgj2UlWp4$">
this ticket</a> is something we’re hoping will be approved at some point to make the normalized dates a little easier to read for users.</p>
<p class="x_MsoNormal">--Benn</p>
<p class="x_MsoNormal"> </p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Ron Van den Branden<br>
<b>Sent:</b> Thursday, October 13, 2022 11:02 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?</p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span lang="NL-BE">Hi Jim,</span></p>
<p class="x_MsoNormal"><span lang="NL-BE"> </span></p>
<p class="x_MsoNormal">Thanks for your thoughts. We’re aiming at minimizing the use of date expressions as much as possible, in order to:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">Reduce the workload and avoid the need to record date information twice (once as date expression, once as standardized date)</li><li class="x_MsoListParagraph" style="margin-left:0in">Reduce the amount of possible input error and ambiguity caused by that redundancy</li></ul>
<p class="x_MsoNormal">In other words: if registrants have to enter a date, it would seem most efficient if they could express this as just a standardized date, which is both precise and machine-processable. Also, for exchangeability, a precise standardized
representation of dates would seem preferable over date expressions, wouldn’t it?</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Best,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Ron</p>
<p class="x_MsoNormal"> </p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b><span lang="NL">Van:</span></b><span lang="NL"> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>Namens </b>James E. Cross<br>
<b>Verzonden:</b> donderdag 13 oktober 2022 16:56<br>
<b>Aan:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Onderwerp:</b> Re: [Archivesspace_Users_Group] how to encode open-ended date ranges?</span></p>
</div>
</div>
<p class="x_MsoNormal"><span lang="NL-BE"> </span></p>
<p class="x_MsoNormal">Another thought: use single date in both cases and let the “Date Expression” field indicate that it is open-ended, i.e. single date “1990,” date expression “1990 - ” or single date “1990,” date expression “1990 (end date)” The date expression
is what the user will see in the PUI.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Jim</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal" style=""><b><span style="font-size:14.0pt; font-family:"Arial",sans-serif; color:#F36721">James Cross</span></b><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333"> <br>
</span><b><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#2E1A47">Manuscripts Archivist</span></b><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333"><br>
Special Collections and Archives<br>
Clemson University<br>
<br>
Strom Thurmond Institute Building</span></p>
<p class="x_MsoNormal" style=""><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333">230 Kappa Street</span></p>
<p class="x_MsoNormal" style=""><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333">Clemson, SC 29634</span></p>
<p class="x_MsoNormal" style=""><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333"><a href="mailto:jcross@clemson.edu">jcross@clemson.edu</a>
</span></p>
<p class="x_MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:#333333">864.656.5182<br>
<a href="https://urldefense.com/v3/__http:/library.clemson.edu/specialcollections/__;!!Dq0X2DkFhyF93HkjWTBQKhk!Vhv7kTVtnT65Ea6wvRVHjpJxPAGILvbvp5uxHvgQMY1hz876NvjNUT1ud7NpUoLSyhAbV7lvXsqNxGnMEAdcYXey5ZmTmr7OpUUB0Iiz$">http://library.clemson.edu/specialcollections/</a>
</span></p>
<p class="x_MsoNormal"> </p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Ron Van den Branden<br>
<b>Sent:</b> Thursday, October 13, 2022 10:32 AM<br>
<b>To:</b> <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> [Archivesspace_Users_Group] how to encode open-ended date ranges?</p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal"><span lang="NL-BE">Hi,</span></p>
<p class="x_MsoNormal"><span lang="NL-BE"> </span></p>
<p class="x_MsoNormal">We’re in the process of migrating data to ArchivesSpace, and one thing I’m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">the fact that only a start date is known</li><li class="x_MsoListParagraph" style="margin-left:0in">or the fact that only an end date is known</li></ul>
<p class="x_MsoNormal">…while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see
<a href="https://urldefense.com/v3/__https:/www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUry3C2sr$">
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/msg05341.html</a>), I’ll outline the observations and options I’m seeing.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">[1] Accessions, resources, archival objects, digital objects:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">“Single” date only offers a single date field, labeled “Begin”</li><li class="x_MsoListParagraph" style="margin-left:0in">“Inclusive” date offers both a “Begin” and “End” date field, only one of which is required
</li></ul>
<p class="x_MsoNormal">Would this be a good strategy:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">“singular/punctual” dates: “single” date, one value as “Begin” date</li><li class="x_MsoListParagraph" style="margin-left:0in">date range: “inclusive” date, start and end dates as “Begin” and “End” dates, respectively</li><li class="x_MsoListParagraph" style="margin-left:0in">open-ended date range: “inclusive” date, with known date as either “Begin” or “End” date</li></ul>
<p class="x_MsoNormal">?</p>
<p class="x_MsoNormal">This leads me to the question whether in practice “single” dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects?</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">[2] Agents:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">“Single” date only offers a single date field, which can be labeled as either “Begin” or “End”</li><li class="x_MsoListParagraph" style="margin-left:0in">“Inclusive” date offers both a “Begin” and “End” date field, of which “Begin” is mandatory</li></ul>
<p class="x_MsoNormal">Would this be a good strategy:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">“singular/punctual” dates: “single” date, one value as either “Begin” or “End” date</li></ul>
<p class="x_MsoListParagraph">Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g.
<br>
<date localType="existence" standardDate="2022-10-08">2022-10-08</date></p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">date range: “inclusive” date, start and end dates as “Begin” and “End” dates, respectively</li></ul>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">open-ended date range: ? <br>
<span style="font-family:Wingdings">è</span> problem if only end date is known, since begin date is mandatory</li></ul>
<p class="x_MsoNormal">In other words: how would one differentiate between, e.g.:</p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">birth date of a living person (1990 - )</li><li class="x_MsoListParagraph" style="margin-left:0in">birth date of a deceased person, whose death date is unknown (1800 - ?)</li><li class="x_MsoListParagraph" style="margin-left:0in">death date of a person whose birth date is unknown (? - 1950)</li></ul>
<p class="x_MsoNormal">?</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn’t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended
date ranges. Therefore, any guidance on this matter would be much appreciated!</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Best,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Ron</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal" style="line-height:125%"><b><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis</span></b><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving</span><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif">
<span style="color:#4D4D4D">| Musea en Erfgoed </span></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Minderbroedersstraat 22, 2000 Antwerpen</span></p>
<p class="x_MsoNormal"><span lang="NL-BE" style="font-size:9.0pt; font-family:"Segoe UI Symbol",sans-serif; color:#4D4D4D">✉</span><span lang="NL-BE" style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#4D4D4D"> Grote Markt 1, 2000 Antwerpen</span></p>
<p class="x_MsoNormal"><span lang="NL-BE" style="font-size:9.0pt; font-family:"Arial",sans-serif; color:#4D4D4D">gsm +32 0485 02 80 50 | tel. +32 3 222 93 30</span><span lang="NL-BE" style="font-size:9.0pt; color:black"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span lang="NL-BE"><a href="https://urldefense.com/v3/__http:/www.letterenhuis.be/__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUtO9V0vc$"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">letterenhuis.be</span></a></span><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">
| </span><span lang="NL-BE"><a href="https://urldefense.com/v3/__https:/www.instagram.com/letterenhuis/__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUorJZpFU$"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">instagram</span></a></span><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">
| </span><span lang="NL-BE"><a href="https://urldefense.com/v3/__https:/www.facebook.com/Letterenhuis__;!!PTd7Sdtyuw!QEv9HwNAtu0O8yQ0ApRp7X3OLav3cGzG6U8Z3ZWXiSBU2UtBSlOPNIlB0iboNUhLSJYzbb8_xbHNbELs8h37VQInUsUvzyqI$"><span style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">facebook</span></a></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"> </span></p>
<p class="x_MsoNormal" style="line-height:125%"><b><span lang="NL-BE" style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Proclaimer</span></b><span lang="NL-BE" style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D"></span></p>
<p class="x_MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:7.0pt; line-height:125%; font-family:"Arial",sans-serif; color:#4D4D4D">Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen
we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een
goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopiëren.</span></p>
<p class="x_MsoNormal"><span lang="NL-BE"> </span></p>
<p class="x_MsoNormal"><span lang="NL-BE"> </span></p>
</div>
</div>
</div>
</body>
</html>