-
Notifications
You must be signed in to change notification settings - Fork 1
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
Datatype entity is missed #11
Comments
Datatype is not listed as an entity in the schema. Maybe it makes sense to treat it the same way as extension/suffix, i.e. as an additional property of the Artifact class. |
This will require to extend the Artifact's definition:
|
yes, I did notice that its not in the schema. I think we will need to think about whether datatype should be deprecated or added to the schema to minimize "exceptions" |
Datatype is in the schema: |
What I am not sure about yet is how to handle the datatype in derivatives as files are not required to be in a datatype (sub-)folder. |
I don't think the BIDS specs ever defined a 1:1 mapping between It took me several read to understand the It just happens that most modalities define a 1:1:1 between all three so it's easy to make this shortcut. I started to reconsider when I read about events, and then much later when the derivatives specs were refined. |
AFAIK, |
…sted upon loading a dataset
See: bids-standard#863 (comment)
The text was updated successfully, but these errors were encountered: