Is your feature request related to a problem? Please describe.
We currently have both dataset import and export capabilities to 3rd party providers, but we only store source URL/DOI (in the dataset's metadata.yml and also in the commit message) for dataset imports.
If we also store the DOI generated by the 3rd party providers for dataset exports, it would be easier for users to:
save the link to their exported data, and be able to check where they exported the data to later
potentially support a workflow to be able to visualize the lineage via the KG for: (a) user exports dataset to zenodo with DOI A, (b) different user imports DOI A to a new renku project.
Describe the solution you'd like
Add the generated DOI to the metadata.yml or wherever the KG can find it
And/or tag the dataset at the exported commit with the DOI/URL
create a commit message that contains the export command & the DOI so users can use the commit log as a workaround
As a corollary, i realized while writing this issue, I can't find the source URL/DOI for datasets that were imported without looking directly at the DOI -- i think this should be a parameter added to renku dataset -c
Is your feature request related to a problem? Please describe.
We currently have both dataset import and export capabilities to 3rd party providers, but we only store source URL/DOI (in the dataset's
metadata.yml
and also in the commit message) for dataset imports.If we also store the DOI generated by the 3rd party providers for dataset exports, it would be easier for users to:
Describe the solution you'd like
As a corollary, i realized while writing this issue, I can't find the source URL/DOI for datasets that were imported without looking directly at the DOI -- i think this should be a parameter added to
renku dataset -c