explore possibilities to allow for flexible/fuzzy dates

[sennierer]

date_of_birth and date_of_death are DateFields and therefore need ISO-Dates: abc_E21_Person
this is not flexible enough for most of the projects. We need a way of allowing people to define fuzzy/inaccurate dates. In vanilla we had written_dates and subsequently tried to parse the chars into dates.

[sennierer]

Maybe use that https://github.com/ixc/python-edtf

[gythaogg]

A JSON field that contains the possibility to store the written form (like 1100-1160 or 11th century) and the start date and end date to represent a range instead of a single date?
Don't feel strongly about it - just thought of it. Not sure if it has an advantage over having the date in several fields as we did in TempEntity.

[sennierer]

Kay: https://github.com/scrapinghub/dateparser

[sennierer]

Richard: we could just add the lower and upper bounds values for the dates in abc classes and leave the implementation to projects

[sennierer]

Birger: there is an API that allows fields to add more fields when they are added to the class (contribute_to_class, apis_core_legacy.entity_relation_field_generator.py)