How do we document qc (inferred/derived values) in datasets when QC by nodes?

[migrate from meeting notes 2022-07-20/09-15]

How do we document when decimalLongitude, decimalLatitude derived from footprintWKT linestring or eventDate is inferred?

Ruben: It makes sense to keep record of the data that us, OBIS data managers, infer from the original data. We need to find a field that we can use to document these cases. Free text fields can be used but are maybe not the best place, since I would like users to have a way to filter out these inferred records.
John: Is there scope to use the Chronometric extensions to adequately describe the eventDate?
Pieter: georeference remarks, eventDateRemarks/eventRemarks(?); but not sure if there is an option at all. GBIF has a custom non-DwC field too
eventRemarks? → might become a bit of a dump
Pieter: there is a project to add provenance to EOVs will have guidelines in the future
Ruben: Can we agree on a field with some standardized terms? So at least internally in the OBIS community and temporarily we have a solution and then we can easily adapt to whatever change is required while we keep on documenting things
Pieter: a structured field like dynamicProperties would be better than something like eventRemarks because we may want to put something else under eventRemarks {“flags_added_by_nodes”: [arrays of flags]}
Ruben: best practices to document cleaning processes with use cases?
Ruben: Some data is inferred from metadata, users need to be informed about this.

Team decided to wait for recommendations from data provenance model

iobis / quality-taskteam