invite others to submit a pull request to add a derived product (e.g., 3D model) to an existing specimen data package publication

[jhpoelen]

proposed workflow:

1. track DwC-A

e.g.,

preston track https://library.big-bee.net/portal/content/dwca/UCSB-IZC_DwC-A.zip 

2. extract content hashes from records somehow

e.g.,

preston head  | preston cat | preston dwc-stream | grep -E 'hash://[a-zA-Z0-9]+/[a-fA-F0-9]+'  | jq --raw-output '.["http://rs.tdwg.org/dwc/terms/associatedOccurrences"]' | grep -v null

derivedFromSameIndividual: https://zenodo.org/record/7114665 | derivedFromSameIndividual: https://zenodo.org/record/7114665/files/96bfde1efa599e0e8e61de18b14d61dd308737f684950e4079c04e9bc0f33958 | derivedFromSameIndividual: https://linker.bio/hash://md5/4940f68c84cffa4412f7ffb98bb255bd
derivedFromSameIndividual: https://zenodo.org/record/7510912 | derivedFromSameIndividual: https://zenodo.org/record/7510912/files/3a178bd2f588c35eb9729309d1baa769ea819bcd5bb5142c2de208dd8e299d1a

which means that two records had a "associatedOccurrences" value with something "hash://...." in it.

[jhpoelen]

Once you have the content hash, you should be able to discover it

e.g.,

preston ls --anchor hash://md5/4940f68c84cffa4412f7ffb98bb255bd --remote https://linker.bio

[jhpoelen]

Also, you can extend it, by adding tracked content:

e.g.,

preston track "donald duck"

or you can make statements:

echo " hash://sha256/abcd

"a pretty cool ASCII animation of a spinning bee" . " | preston append to extend the specimen data package. Optionally, you can submit the extension for review with Katja via tool XYZ (e.g., github, reference to a zenodo publication, os just a hash). E.g., Hey, I looked at your publication A (hash://sha256/abcdef.....) , and I've annotated and extended your bee data package through my publication B (hash://sha256/xyz123... ) . Now, publicatoin B (hash://sha256/xyz123...) contains a reference to publication A (hash://sha256/abcdef.....) in their provenance (or origin log).

[jhpoelen]

To make specific claims on how pub A and pub B are related, you can used . . . provenance logs! with specific claims on how, who, what and where, when, pub A and pub B were related.

[jhpoelen]

an in DwC-A you can make shortcuts like:

hasExtension: hash://sha256/abcdef

hash://sha256/abcdef: datapackage hash://sha256/abcdef: application/otn-traits

[jhpoelen]

suggest to borrow relations from Provenance Ontology (aka Prov-O) or its related Provenance Authoring and Versioning (PAV) ontology.