Open jyucsiro opened 5 years ago
I assume this will be an aspect of the dataset metadata - see https://github.com/CSIRO-enviro-informatics/asgs-dataset/issues/8 https://github.com/CSIRO-enviro-informatics/geofabric-dataset/issues/14 https://github.com/CSIRO-enviro-informatics/gnaf-dataset/issues/2
In that context, there are a few ways to indicate version information:
prov:wasGeneratedBy/prov:endedAtTime
dct:modified
- time-stamp will be needed if there is more than one update per daypav:version
where pav:
is http://purl.org/pav/
My general assumption would be that
dct:modified
element. This should be automatically updated when the ETL process is runprov:wasGeneratedBy
and prov:wasDerivedFrom
) The link to the source data should be to a specific version.
@shaneseaton @ashleysommer @benjaminleighton Could I see an example of what the run-time parameters are, so that I can suggest how these could be recorded in a provenance record?
@benjaminleighton wrote on Slack:
On minimalist provenance for https://github.com/CSIRO-enviro-informatics/loci.cat/issues/16 I think getting this completely right first time is going to be tricky. Would sticking a pav:version in that we manually increment be sufficient for now?
How do we describe version information in each of the Loc-I datasets (e.g. ASGS, Geofabric, GNAF)?
2nd part - implement for each Loc-I enabled dataset.
Add details to this issue ticket. Will need to document this somewhere for consistent communication to users