Use "dataset" not "project" for intro description of "Folders and Files" #400
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
Opening statement talks about BIDS dataset, not a project. Initial motivation: Although BIDS dataset CAN (and IMHO SHOULD) be used for "project", or better "study" (following BEP035 entity term) level description, then you might compose components differently. E.g. "sourcedata/raw" would actually include raw BIDS dataset, and this particular "study" level dataset would not contain "sub-*" subfolders, thus potentially breaking analogie introduced by this tutorial. Hence, for consistency, I think we should stay with "dataset" at this level of description for now.
Remi-Gau
approved these changes
Apr 15, 2024
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.
Opening statement talks about BIDS dataset, not a project.
Initial motivation: Although BIDS dataset CAN (and IMHO SHOULD) be used for "project", or better "study" (following BEP035 entity term) level description, then you might compose components differently. E.g. "sourcedata/raw" would actually include raw BIDS dataset, and this particular "study" level dataset would not contain "sub-*" subfolders, thus potentially breaking analogie introduced by this tutorial.
Hence, for consistency, I think we should stay with "dataset" at this level of description for now.
related backref:
rawdata/intosourcedata/rawin alternative structure example, clarify on naming of datasets themselves bids-specification#1741