-
Notifications
You must be signed in to change notification settings - Fork 194
make inheritance applicability explicit for scan.json #789
Copy link
Copy link
Closed
Labels
Description
@robertoostenveld in #538 (comment) mentions that "using the inheritance principle there can be a scans.json at the top level". Current inheritance principle formulation seems to suggest that too, but documentation nowhere mentions scans.json although it could be quite a common use case.
ATM I see only a single dataset with a (broken) scans.json
(git)smaug:/mnt/datasets/datalad/crawl/openneuro[master]git
$> ls -ls ds00*/*scans.json
4 -rw------- 1 yoh datalad 656 Oct 23 2020 ds003242/scans.jsonand which is
$> cat ds003242/.bidsignore
scans.jsonpossibly likely because prior versions of bids-validator choked on it.
So I wonder if we should add scans.json
- as an explicit example to "Inheritance principle" section
- to https://github.com/bids-standard/bids-specification/blob/master/src/schema/top_level_files.yaml (attn @bids-standard/raw-electrophys-ieeg
?
Reactions are currently unavailable