Skip to content

update MCF record lifecycle dates#342

Merged
tomkralidis merged 2 commits intomasterfrom
mcf-metadata-dates
Apr 27, 2026
Merged

update MCF record lifecycle dates#342
tomkralidis merged 2 commits intomasterfrom
mcf-metadata-dates

Conversation

@tomkralidis
Copy link
Copy Markdown
Member

This PR updates pygeometa's record lifecycle support by moving from metadata.datestamp to metadata.dates, where metadata.dates is the exact same design pattern as identification.dates, but focused on record lifecycle (vs. identification.dates which is based on citation).

Note that this is a breaking change, and that the 0.20.0 release can be used safely until users migrate accordingly against master or when 0.21.0 is released. Summary of changes are as follows:

  • metadata.datestamp is removed (BREAKING)
  • identification.dates is now optional (BREAKING)
  • metadata.dates.creation is added and mandatory (BREAKING)
  • metadata.dates.revision is added and optional

@tomkralidis tomkralidis merged commit fa06849 into master Apr 27, 2026
4 checks passed
@tomkralidis tomkralidis deleted the mcf-metadata-dates branch April 27, 2026 20:52
@pvgenuchten
Copy link
Copy Markdown
Contributor

pvgenuchten commented Apr 29, 2026

this indeed is quite impactfull on existing mcf's

for future changes may be interesting to support a migration automation

if 'datestamp' in mcf['metadata']:
   mcf['metadata']['dates'] = {'revision': mcf['metadata'].pop('datestamp')}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants