[ENH] Add RECOMMENDED DatasetType key to dataset description #494
Conversation
This file contains 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
5 tasks
|
Hey, it's 4pm and there's a thumbs up! Thanks @emdupre! In it goes, and may history judge us justly. |
nicholst
changed the title
Merged
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.
Last-minute addition to #265 (Common Derivatives).
This allows for unambiguous identification of raw or derivatives datasets by parsing a single file. This is needed because any feature of derivatives has the potential to be incorporated back into raw, unless it breaks backwards compatibility. In the extreme, it may only be possible to distinguish the two by determining whether a dataset validates as raw or as derivative.
cc @bids-standard/derivatives