Clarify child Dataset relationships - #155
Merged
NicolasCARPi merged 1 commit intoAug 12, 2026
Merged
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
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.
What changed
Datasetreferences with the relationship described in issue Property to link parent with child experiments #116./import listWhy
The current specification first says that child datasets can be referenced and must also appear in the root import list, then says that datasets must not contain other datasets in
hasPart. This makes the intended parent/child representation impossible to follow. The new wording keeps both roles explicit: nestedhasPartrecords the relationship, while direct root membership marks a dataset for import.Closes #116.
Validation
git diff --checkpython -m pytest— 6 passed