You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this case came up a number of times. I do not think we arrived at any facility to address those use-cases. ATM we only have -R|--recursion-limit to limit via hardcoded recursion limit integer. Here I would like to collect use cases which could drive us a solution to tackle
"YODA'ed datasets from above": it is typical to recommend installing some version from the flattened level above, e.g. smth like datalad create -d . derivatives/deriv1 && cd derivatives/deriv1 && datalad clone -d . ../../rawdata sourcedata && ... && cd - && datalad save -m "Finalized deriv1 derivative" -d . derivatives/deriv1 && datalad uninstall derivatives/deriv1/sourcedata. So that later on someone could install the hierarchy of the dataset but without installing those sourcedata/ installations.
note that URL in .gitmodules for sourcedata/ might be replaced with a public URL, not just local one.
I think this case came up a number of times. I do not think we arrived at any facility to address those use-cases. ATM we only have
-R|--recursion-limit
to limit via hardcoded recursion limit integer. Here I would like to collect use cases which could drive us a solution to tackledatalad create -d . derivatives/deriv1 && cd derivatives/deriv1 && datalad clone -d . ../../rawdata sourcedata && ... && cd - && datalad save -m "Finalized deriv1 derivative" -d . derivatives/deriv1 && datalad uninstall derivatives/deriv1/sourcedata
. So that later on someone could install the hierarchy of the dataset but without installing thosesourcedata/
installations.sourcedata/
might be replaced with a public URL, not just local one.-R 1
but might prevent not installing some "ad-hoc" subdatasetmay be could be re-expressed via
.gitmodules
records, and then explicitly allowing to say to not install submodules with specific label/tag.WDYT @datalad/developers and @datalad/contributors -- did you have related use-cases?
The text was updated successfully, but these errors were encountered: