<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">For some reason I appear to unable to add a comment to AS-102 in Jira, so posting it here: </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">
<h1 id="summary-val" style="margin: 0px 0px 0px -5px; padding: 2px 30px 2px 5px; color: rgb(51, 51, 51); font-size: 24px; font-weight: normal; line-height: 1.25; z-index: 1; font-family: Arial, sans-serif;" class="">
PDF export not only inclusive dates and include “Approximate,” “Inferred,” and “Questionable" labels</h1>
<div class=""><br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class=""><a href="https://archivesspace.atlassian.net/browse/AS-102" class="">https://archivesspace.atlassian.net/browse/AS-102</a></div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Although DACS model and ArchivesSpace describes more types of dates, the only allowed values for EAD unitdate/@type are “bulk” and “inclusive” . But @type is not required, so would it not be better to not include a @type attribute for date type
“single” instead of mapping it to “inclusive” , which some people are finding confusing. </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">+1 for including unitdate/@certainty in EAD export and passing it thru to PDF output. </div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">— Steve Majewski</div>
<div class=""><br class="">
</div>
</body>
</html>