-
Notifications
You must be signed in to change notification settings - Fork 6
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
EEG: multiple dataset files can be submitted with different extension #22
Comments
Relates to bids-standard/bids-specification#1487 Unless I am mistaken enforcing this would depend on updating the schema (see bids-standard/bids-specification#1492) for the deno based validator. I doubt the legacy validator will enforce this. |
I don't think we have a rule in BIDS that the data format chosen for a dataset must be consistent 🤔 although it is a bit weird to mix them in a single dataset. |
We do check whether someone has both bids-validator/bids-validator/validators/nifti/duplicateFiles.js Lines 3 to 34 in 932c782
A similar thing could be written for other formats, although it would be more complicated, because EEG has multi-file formats and files sharing the same stem isn't in itself an error. |
but does it say in the spec, that these shouldn't be mixed? |
No, but it does create ambiguity about the data and frequently problems for tools expecting to retrieve a unique data file for a collection of entities. I would support making it an explicit part of the spec, though I would not complain if it happened after @Remi-Gau's schema changes were incorporated and supported by the schema validator. |
I think we had added this section in the spec, no? https://bids-specification.readthedocs.io/en/stable/common-principles.html#uniqueness-of-data-files But I need to get back to finishing the schema pr. |
what we added there was:
However, here we have |
This dataset contains both .set and .vhdr files
https://nemar.org/dataexplorer/detail?dataset_id=ds003190
This should not be possible. There should be either one or the other.
The text was updated successfully, but these errors were encountered: