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

provenance standards #56

Open
vjcitn opened this issue Nov 4, 2024 · 1 comment
Open

provenance standards #56

vjcitn opened this issue Nov 4, 2024 · 1 comment

Comments

@vjcitn
Copy link
Collaborator

vjcitn commented Nov 4, 2024

The merfish.zarr in inst/extdata has zmetadata but I do not see anything that would constitute experiment metadata -- what is the source, what version of platform, etc. Can we state a minimal standard for experiment provenance and ensure that all
our data artifacts can be checked for compliance?

@HelenaLC
Copy link
Owner

HelenaLC commented Nov 4, 2024

Agreed. To the best of my knowledge, this is currently missing in SpatialData (Python). The topic came up with Luca in a recent call. One option would be to stash element-wise metadata (i.e., for every image/label/point/shape/table), which could be accessed in R as a table, and used for easy filtering (e.g., give me all elements from batch A or section 2 etc.). Ideally, we allow for full flexibility here (because any dataset could, in principle, have data from many hospitals, patients, sections, technologies etc.). Minimal entries would simply be the element identifier, I guess.

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