Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helper API to provide metadata item for capturing provenance of a derived data file #190

Open
yarikoptic opened this issue Aug 21, 2023 · 1 comment

Comments

@yarikoptic
Copy link
Member

E.g. as now came up in the context of the spike sorted data in dandi/dandi-cli#1314 but also is to be used in the use case of @vandermeerlab (attn @TheChymera @manimoh) . I guess it should take a metadata record, original asset(s) information, and return enhanced metadata record. @satra you have mentioned that we had worked that out that somewhere.

Then with that helper in mind, we should provide documentation for https://github.com/dandi/handbook/ .

@satra
Copy link
Member

satra commented Sep 10, 2023

yes, we worked that out for publishing dandisets. it takes the metadata adds the provenannce: https://github.com/dandi/dandi-archive/blob/6cc74347458f1e12a434ac95ccd417ef48fbe4da/dandiapi/api/services/publish/__init__.py#L90

in the context of dandi-schema, one could use the schema library itself to inject derived from: asset_meta.wasDerivedFrom = [other_asset.id] if the field is blank or append if not.

however, right now the wasDerivedFrom is only supporting Biosample derivations to assets (

wasDerivedFrom: Optional[List[BioSample]] = Field(None, nskey="prov")
). we should add URI as an option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants