testing datalad

Jump to bottom

Julien Cohen-Adad edited this page Apr 3, 2020 · 3 revisions

Procedure for testing datalad

Speed

run commands remotely via VPN.

https://github.com/neuropoly/datalad/issues/2

Sensitivity/Specificity to changes

https://github.com/neuropoly/datalad/issues/3

Permissions

Size limitations

The git repository will likely grow as we keep changing data. We need to understand how fast it grows: if files are moved? renamed? What is the best practice here?

Sharing data

Scenario: we decide to share with the public an internal dataset. How to do this?

Testing

how does it work
who can connect to it
how to fetch data from another station
how to add data
who can add data
what is the versioning strategy/convention
how is duke windows file system dealing with data fetching (we’ve seen errors in the past)
how is duke/grappelli backuping dealing with git-annex