If you want to make code/data “available”, GitHub isn’t enough.
You must deposit at a DOI-issuing data repository @figshare & @ZENODO_org are both free & awesome; can be synced w/ a GitHub repo
Why GitHub not enough? 1/4
#OpenAccess #OpenData
You must deposit at a DOI-issuing data repository @figshare & @ZENODO_org are both free & awesome; can be synced w/ a GitHub repo
Why GitHub not enough? 1/4
#OpenAccess #OpenData
GitHub is a place for things to be worked on, not for them to live forever.
- Links are fragile (username, repo name)
- Users can delete repos
- GitHub could make your code/data unavailable in the future.
DOI-issuing data repositories preserve your stuff for the future 2/4
- Links are fragile (username, repo name)
- Users can delete repos
- GitHub could make your code/data unavailable in the future.
DOI-issuing data repositories preserve your stuff for the future 2/4
Depositing on @KaggleDatasets isn’t good enough for #OpenAccess #OpenData either.
- No API for accessing files without an account
- Fragile URLs
- Kaggle Datasets is a commercial thing.
Do all three! GitHub repo, Kaggle Dataset and @figshare or @ZENODO_ORG 3/4
- No API for accessing files without an account
- Fragile URLs
- Kaggle Datasets is a commercial thing.
Do all three! GitHub repo, Kaggle Dataset and @figshare or @ZENODO_ORG 3/4
I’ve rarely seen the prominent voices in #rstats or CODE #reproducibility talk about DOI.
Are you hearing about DOI and data repositories for the first time here? 4/4
HT @drob @juliasilge @hadleywickham @MeganRisdal
Are you hearing about DOI and data repositories for the first time here? 4/4
HT @drob @juliasilge @hadleywickham @MeganRisdal
