Skip to content
This repository has been archived by the owner on Nov 2, 2021. It is now read-only.

make datalad-recursiveinstall skip default for sourcedata #157

Open
pvavra opened this issue Apr 22, 2020 · 1 comment
Open

make datalad-recursiveinstall skip default for sourcedata #157

pvavra opened this issue Apr 22, 2020 · 1 comment

Comments

@pvavra
Copy link

pvavra commented Apr 22, 2020

Going through the datalad handbook, I noticed a footnote mentions the option to make sub-datasets to not be installed recursively, unless explicitly requested. I think this should be set to be the default for sourcedata when converting a dataset to bids.

Installing the bids dataset later as input would most likely not need access to the sourcedata along with it.

The simplest solution would be to have the docs mention that option and show how to set it manually.

If possible, automatically setting that option would be preferable. However, I'm not sure which step should be doing that..

@bpoldrack
Copy link

bpoldrack commented Apr 23, 2020

I agree that this config would be good to have in the BIDS dataset whenever it was built the way intended by hirni. However, this

I'm not sure which step should be doing that..

is the problem indeed. The cfg_bids procedure (called by datalad create -c bids mybids_dataset for example) could do that. But: Nobody is required to use hirni to get such a sourcedata. And even if you follow hirni, you are not required to install the raw dataset into sourcedata directly. You could install it somewhere underneath sourcedata and still be BIDS compliant. Leading to: There's no hirni or neuroimaging related command or procedure that at the time of its execution knows for sure what that configuration should look like. Only whoever installs that dataset into the BIDS dataset knows.

So, adding that to the docs - yes. Setting it automatically - I can't see where.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants