Our base model Date allows entering historical dates as a range when the exact data is not known.
A model like Occupation describes a period of time, which is currently also encoded as a single Date. This looks sort of sensible in the admin form, because you can fill in something like "between 450 and 470", but that doesn't allow researchers to encode uncertainty. Are we certain that this person held the office in 451? Or do we just know that they held the office at some point between 450 and 470?
In cases like this, we should really have a DateRange model (which may consist of two Date instances). A researcher should be able to encode something like "this person took this office between 445 and 455, and had that occupation until 470".
Our base model
Dateallows entering historical dates as a range when the exact data is not known.A model like
Occupationdescribes a period of time, which is currently also encoded as a singleDate. This looks sort of sensible in the admin form, because you can fill in something like "between 450 and 470", but that doesn't allow researchers to encode uncertainty. Are we certain that this person held the office in 451? Or do we just know that they held the office at some point between 450 and 470?In cases like this, we should really have a
DateRangemodel (which may consist of twoDateinstances). A researcher should be able to encode something like "this person took this office between 445 and 455, and had that occupation until 470".