<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Yes, you are right. Will be fixed in next release: https://github.com/archivesspace/archivesspace/pull/173</div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from my T-Mobile 4G LTE Device</div></div><br><br><div>-------- Original message --------</div><div>From: carrie.daniels@louisville.edu </div><div>Date:04/09/2015 3:04 PM (GMT-05:00) </div><div>To: archivesspace_users_group@lyralists.lyrasis.org </div><div>Cc: </div><div>Subject: [Archivesspace_Users_Group] Dates issue </div><div><br></div>
<div class="WordSection1">
<p class="MsoNormal">I’m working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin
and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter “2010” in the Begin field. Am I missing something? If not, is this intentional? <o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Carrie<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Carrie Daniels<o:p></o:p></p>
<p class="MsoNormal">University Archivist<o:p></o:p></p>
<p class="MsoNormal">Director, Archives and Special Collections<o:p></o:p></p>
<p class="MsoNormal">University of Louisville<o:p></o:p></p>
<p class="MsoNormal">(502) 852-6676<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>