Closed arcadiafalcone closed 2 years ago
What happens if
<dateCreated qualifier="approximate" point="end">-0099</dateCreated>
also has encoding="edtf"
?
@cbeer I think it should still display the same as the first date.
I've confirmed the date range displays correctly with encoding="edtf"
.
So the issue is that the first date has encoding="edtf"
and the second does not? I know we changed how the modsulator handles encoding for endpoints of date ranges at some point so that may have introduced some inconsistency. I'll look into data remediation to add the encoding to the second date.
Correct. I think any encoding would work, but unencoded dates are too ambiguous to parse 🤷♂️
OK, I'll treat this as a data issue then. Closing.
See also #116 for changing current use of B.C./A.D. to BCE/CE.
In MODS date ranges where the end date is less than 0, the value is not parsed for display. It should be transformed in the same way as the start date.
Example: tw991mx3953 [ca. 250 B.C.--0099] > [ca. 250 BCE-100 BCE]