Design document to refactor access to JSONSchema serialization of dandi-schema's dandiset.json #2381
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Metadata lifecycle inspired by the one we created for BIDS: see bids-standard/bids-website#626
yarikoptic
added
documentation
yarikoptic
commented
May 15, 2025
yarikoptic
changed the title
This was referenced May 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Metadata life-cycle inspired by the one we created for BIDS: see bids-standard/bids-website#626
Even if we decide to not anyhow proceed with this design doc, might be worth clarifying and extracting the mermaid diagram to be embedded in the docs for the developers.
You can see the diagram rendered at https://github.com/dandi/dandi-archive/blob/doc-design-jsonschema-runtime/doc/design/vendored-schema-1.md . Here is a preview which might get outdated
TODOs
claude code)