Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for more data repositories - with a shared library? #48

Open
remram44 opened this issue Apr 15, 2021 · 1 comment
Open

Support for more data repositories - with a shared library? #48

remram44 opened this issue Apr 15, 2021 · 1 comment
Labels
C-repositories Component: Repository integrations T-task Type: Something to be done, neither a bugfix nor an enhancement of the code

Comments

@remram44
Copy link
Member

Originally opened 2019-12-20 07:11 EST by @nuest

In the ReproServer-preprint you mention you want to support more data repositories. 馃挴 !

Looking at reproserver's code to download data from Zenodo and the one that repo2docker uses in its "contentprovider", I see a lot of similarities!

suppdata is a "DOI to data" package for R, which so far focused on supplemental data for papers' DOIs, but I'd like to extend it towards data repositories.

A background discussion is also here: ropensci-archive/doidata#1

What do you think about a generic "data download from DOI" package in Python that both ReproServer and repo2docker could use?

@remram44 remram44 added T-task Type: Something to be done, neither a bugfix nor an enhancement of the code C-repositories Component: Repository integrations labels Apr 15, 2021
@remram44
Copy link
Member Author

Originally posted by @remram44

I'm in favor, though we might want to support more than DOIs?


Originally posted by @nuest

Do you mean other handles?

git URLs (git://) and Git{Hub/Lab} URLs of course.

Maybe also files from Git LFS?

repo2docker also has an open issue for plain URLs (zip files).

--

Thanks for the interest. We could sketch this out a bit further and then reach out to the r2d folks if this is feasible for them. It simply feels like something that should be done once, and right, and put on PyPI for everyone to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-repositories Component: Repository integrations T-task Type: Something to be done, neither a bugfix nor an enhancement of the code
Projects
None yet
Development

No branches or pull requests

1 participant