Dates: years to fully featured rico:Date entities

[paveljee]

Probably needs to be parsed from descriptions or sourced from Linked Open Data.

Issues with dates identified so far:

• Beginning and end date are separate entities in RiC-O but are stored in one field in ADD
• Various conventions for approximate dates (e.g., question marks, 19– like dates with a dash, “ca.”, etc. - these are specified in RAD but probably not used consistently)
• Make it a class or a literal? - Following a discussion on June 7th, likely a class (rico:Date)
• Formatting dates in the ISO format is recommended in RiC-O but difficult to achieve due to the aforementioned issues with missing data
• occurredDate - keep in mind that this is new information that is added by the archivist at the mapping stage; no uniform precursor in the existing data

[paveljee]

Re: rico:accumulationDate:

it is not defined in RiC-O yet. I raised the need for such a property here: ICA-EGAD/RiC-O#109 and it seems that the lead developer agrees in principle that it should be created in future. Meanwhile, we can use rico:date but will need to insert a label before the data to make clear what it is (e.g. “Accumulation date: 1972-1994”).

[paveljee]

This is more or less done now as original CSV columns were lightly preprocessed, so rico:Date are generated. However, deep parsing of dates has not been done yet, so I am keeping this issue open just to be sure.