review DC import for dates

[pvgenuchten]

Description

• for many of my imported DC records, the date field contains the resource date, but in iso it is the insert date and modified is empty

dct:date vs dct:temporal and pycsw:time_begin/time_end

From docs:
pycsw:date maps to dc:date (and pycsw:date indicates no mapping for iso; however record-timestamp seems used)
however reading dc:docs dc:date seems a very generic lifecycle event, can even have begin/end; dct:temporal is much more suited for begin/end.
my impression from assessing some catalogues, is that dc:date is mostly used as record.datestamp

Suggestions

• capture and advertise dc:date as pycsw:date_modified
• remove the pycsw:date property or duplicate the content from pycsw:date_modified
• capture and advertise dct:temporal as pycsw:time_begin/_end
• capture and advertise dct:issued as pycsw:date_published
• related to updated modified date in iso19139 import #1043, do not advertise pycsw:insert_date in records

Links

pycsw/pycsw/core/metadata.py

Line 1645 in 4a27826

def _parse_dc(context, repos, exml):