It would be good to produce artifacts from any mapping run that support provenance, auditability, or reproducibility of mapped outputs.
One path could include writing profiling outputs to file.
Other metrics of interest include reporting versions and hashes (datetime of run, libtokamap tag, reported mapping file version, hash of mapping file, versions of datasources and any queryable version/config info from the servers they connect to and of the underlying files that were mapped from). Clearly any changes in this chain could change the actual data coming out of the mapping process so resulting data objects probably need to be understood within that context. Would be good for libtokamap to actively support this.
output would ideally (ultimately) be a standard format such as .prov or an RO crate I assume, but anything better than nothing to start.
It would be good to produce artifacts from any mapping run that support provenance, auditability, or reproducibility of mapped outputs.
One path could include writing profiling outputs to file.
Other metrics of interest include reporting versions and hashes (datetime of run, libtokamap tag, reported mapping file version, hash of mapping file, versions of datasources and any queryable version/config info from the servers they connect to and of the underlying files that were mapped from). Clearly any changes in this chain could change the actual data coming out of the mapping process so resulting data objects probably need to be understood within that context. Would be good for libtokamap to actively support this.
output would ideally (ultimately) be a standard format such as .prov or an RO crate I assume, but anything better than nothing to start.