<div dir="ltr">I think the new model makes sense, but the migration will be onerous for a lot of people depending on the state of their existing data. Alex Duryee at NYPL (I think he's still there) published some Ruby code (which I also contributed to during my time there) that could be useful in the migration process:<div><a href="https://github.com/alexduryee/timetwister">https://github.com/alexduryee/timetwister</a><br></div><div>He also ported it into an AS plugin:</div><div><a href="https://github.com/alexduryee/timewalk">https://github.com/alexduryee/timewalk</a></div><div><br></div><div>It parses date expressions into one or more normalized dates based on regex patterns and corresponding rules for parsing each pattern. I ran an earlier version of it over a fairly large corpus for dates from NYPL archival collections with very good results, and it's been improved upon since then.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 14, 2018 at 2:49 PM, Cory Nimer <span dir="ltr"><<a href="mailto:cory_nimer@byu.edu" target="_blank">cory_nimer@byu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_3010386674179263139WordSection1">
<p class="MsoNormal">Colleagues,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The Development Prioritization Team is seeking community input on a feature request for revisions to the Date subrecord in ArchivesSpace (ANW-380;
<a href="https://archivesspace.atlassian.net/browse/ANW-380" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/ANW-380</a>). The Date subrecord is used in multiple ArchivesSpace modules, including those for Accession, Resource, and Digital Object records. Changes
to the Date subrecord to support the EAC-CPF <dateRange> model were previously included in the Agents revision project specifications (ANW-429;
<a href="https://archivesspace.atlassian.net/browse/ANW-429" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/ANW-429</a>), and the new model would support either EAD2002/EAD3 <unitdate> or EAD3 <unitdatestructured> exports.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The primary change planned is the separation of begin and end date expressions in the application. For example, currently a single date expression is used with separate normalized begin and end date entries for date spans:
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u>Date subrecord<u></u><u></u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Date Expression: circa 1950-1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Begin: 1950<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">End: 1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Certainty: Approximate<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The revised model would include a separate date expression field entry for each part of the date span:
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u>Date subrecord<u></u><u></u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Begin Date Expression: circa 1950<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Begin Date Standardized: 1950<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in">End Date Expression: 1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">End Date Standardized: 1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Certainty: Approximate<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The concern has been raised that institutions may not have sufficiently consistent data entry practices to allow a single migration script to parse existing Date Expression values into separate Begin and End date expression fields. One
proposed path has been to move the entire existing Date Expression value to the new Begin Date Expression, while moving the normalized dates to their appropriate standardized value fields. This would appear as:
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u>Date subrecord<u></u><u></u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Begin Date Expression: circa 1950-1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Begin Date Standardized: 1950<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<p class="MsoNormal" style="margin-left:.5in">End Date Expression: <u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">End Date Standardized: 1960<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">…<u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Certainty: Approximate<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">The Development Prioritization Team would like to obtain feedback from the community regarding preferences for migrating existing Date subrecord content, or other concerns. Comments may be submitted through JIRA on the ticket for ANW-380
(<a href="https://archivesspace.atlassian.net/browse/ANW-380" target="_blank">https://archivesspace.<wbr>atlassian.net/browse/ANW-380</a>).
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Sincerely,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Cory Nimer<u></u><u></u></p>
<p class="MsoNormal">University Archivist<u></u><u></u></p>
<p class="MsoNormal">Brigham Young University<u></u><u></u></p>
<p class="MsoNormal">801-422-6091<u></u><u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><font size="2" style="background-color:rgb(255,255,255)" color="#666666">Trevor Thornton</font><div><font size="2" style="background-color:rgb(255,255,255)" color="#666666">Applications Developer, Digital Library Initiatives</font></div><div><font size="2" style="background-color:rgb(255,255,255)" color="#666666">North Carolina State University Libraries</font></div></div></div></div></div></div></div>
</div>