Stephan Heunis

Thanks for everyone's input! FYI @CPernet there is already a standard BIDS config that does the above process to an extent. See here for an update: https://github.com/datalad/datalad-neuroimaging/pull/115.

Also tagging @surchs and @CPernet based on likely shared interest.

Oh wow, didn't know about [datalad-fuse](https://github.com/datalad/datalad-fuse) and now I do, great! I'm guessing that functionality (check whether possible to get partial content via fuse, otherwise `datalad get`) would probably live...

Here's a sample of output from the [BOLD5000 dataset](https://github.com/OpenNeuroDatasets/ds001499) that I ran locally: ``` datalad clone https://github.com/OpenNeuroDatasets/ds001499 cd ds001499 datalad -f json_pp meta-extract -d . bids_dataset ``` yields: ``` {...

New `bids_dataset` extractor that works with next generation metalad has been added here in the `update-bids-extractor` branch: https://github.com/datalad/datalad-neuroimaging/tree/update-bids-extractor No PR yet since I am uncertain about: - This update adds...

TODO for @jsheunis: - merge updated master - Create WIP PR

Thanks. AFAIK it probably still makes sense to keep the `bids_dataset` extractor as part of `datalad-neuroimaging`, but happy to hear arguments for the alternative.