The ResourceBase model at the moment handles the two date fields (related to data, not to metadata):
date
date_type (creation|revision|publication)
Since CSW ISO AP defines "CreationDate", "RevisionDate", "PublicationDate" as queriables, we may replace the fields date and date_type with:
csw_data_creation_date
csw_data_revision_date
csw_data_publication_date
where
csw because they are only used in CSW output
data because they refer to data, and not to the metadata document (there are other fields for that purpose)
The migration should populate the new fields using the date and date_type fields:
- if
date_type=='creation' --> set csw_data_creation_date = date
- if
date_type=='revision' --> set csw_data_revision_date = date
- if
date_type=='publication' --> set csw_data_publication_date = date
Once the migrations are done,
- change the pyCSW mappings to point to the new fields
- change the ISO XML template to use the new fields
The ResourceBase model at the moment handles the two date fields (related to data, not to metadata):
datedate_type(creation|revision|publication)Since CSW ISO AP defines "CreationDate", "RevisionDate", "PublicationDate" as queriables, we may replace the fields
dateanddate_typewith:csw_data_creation_datecsw_data_revision_datecsw_data_publication_datewhere
cswbecause they are only used in CSW outputdatabecause they refer to data, and not to the metadata document (there are other fields for that purpose)The migration should populate the new fields using the
dateanddate_typefields:date_type=='creation'--> setcsw_data_creation_date=datedate_type=='revision'--> setcsw_data_revision_date=datedate_type=='publication'--> setcsw_data_publication_date=dateOnce the migrations are done,