Closed josephrife closed 1 year ago
Note to self:
Ended up handling this slightly differently. I just ran the origDate update script on records whose origDate elements began with a 0. #167 will need a bit more work than previously planned as the post-processor will also need an update to handle origDate processing triggered by the attribute values, rather than the text node, which is the current functionality. I'll track all of this in that issue, however. For now, the display version of the orig dates should all be working.
There is something wrong with the dates in that content-area in the following records: 43, 46, 48, 220, 329 (there could be more). The website is showing the dates as entered in xml files (e.g. 0419 0420) and not converted into the standard format for viewing (i.e. 419 - 420 CE).