-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataverse data access module #124
base: dev
Are you sure you want to change the base?
Conversation
cc @amva13 |
Hi Abe, this is great work, thank you! I'm pretty busy right now but I'll try to start merging asap. I just have two thoughts at the moment:
|
Hi Laura,
I'll think about and add more commits asap.
That's true. I think this can work with dataverse DOI and/or just I made this a draft PR while I'm adding more commits. |
Oops sorry didn't mean to close this |
Oh no worries, I also didn't get chance to finish what we discussed before. I have the changes in a fork so I'll open another PR in the future. Thanks :) |
No need, I'll reopen this one as soon as the unit tests are passing and I can make a new dev branch |
Aim
Including a draft dataverse data collector as part of
gget
tool boxes.e.g.
Tasks
History
As part of GilbertLabUCSF/CanDI#34, related to #121, I draft a module to collect data from dataverse. Then I thought data collection from dataverse can be a more general functionality here as part of
gget
.I mostly borrowed codes from gears/utils.py or TDC/load.py. However, there are other efforts such as pyDataverse and easyDataverse.
References