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'd like to add a new dataset from the Baby Connectome Project (covering subjects aged 0–5 years) to our data server. Access should be limited to Alexia, Benjamin, Eva, and me. Initially, I'll only upload the anat (T1w and T2w) folders due to storage constraints, but we may include fMRI, rfMRI, and dMRI data later on.
Could you please initialize the dataset and grant write access to both me and @amahlig? Thank you!
The text was updated successfully, but these errors were encountered:
To have a private repository (visible to only some lab members), you'll have to create it under your account, rather than inside the "NeuroPoly datasets" organization, similar to what we did in #344. I can do it with you tomorrow if you want, or you can ask @amahlig how to do it.
Sorry for only hopping on this issue now. Glad that you got everything sorted in the meantime.
Access should be limited to Alexia, Benjamin, Eva, and me.
I just wanted to add that if the above is a consistent group of people who will need to access numerous restricted datasets, something we could consider is creating a private organization within NeuroGitea to centralize and manage them all.
It's definitely not necessary and probably doesn't make sense if it's only a couple of these datasets, but it maybe it would be convenient if there are going to be many of them with the same people who need access each time?
Hi,
I'd like to add a new dataset from the Baby Connectome Project (covering subjects aged 0–5 years) to our data server. Access should be limited to Alexia, Benjamin, Eva, and me. Initially, I'll only upload the anat (T1w and T2w) folders due to storage constraints, but we may include fMRI, rfMRI, and dMRI data later on.
Could you please initialize the dataset and grant write access to both me and @amahlig? Thank you!
The text was updated successfully, but these errors were encountered: