Comments (5)
sorry about the confusion, it confuses me too.
So whenever downloading data, I should look at this field, parse it, and take the second one?
yes, that should work
Dryad's architecture is not very clear to me, why would a data archive with a single file would have two DOIs?
it sorta makes sense - the DOI without the end slash and number part leads to the landing page for the data package, and any DOIs with /1
, etc. are for individual data files
So actually the first DOI is only for the data package while all the other ones are for the data files.
right.
I'll try to clarify in the examples how people can do this. maybe even a helper function to get all the DOIs for individual data files for a data package
from rdryad.
in commit 4c9e364 added a new function dryad_package_dois
to fetch the individual file DOIs from a package DOI - adding some examples now
from rdryad.
@Rekyt thanks for the report. thanks for the kind words
I don't know off the top, i'll have a look
from rdryad.
changes in b6819b5
@Rekyt reinstlal from github devtools::install_github("ropensci/rdryad")
-
changed download_url
to take a DOI or a Dryad handle. The function was only correctly dealing with handles before now.
I updated rdryad
to use solrium
instead of solr
in terms of using d_solr_search
, see the dc.identifier
field which gives the DOI for the dataset, actually gives two for your query , or the dc.identifier.uri
field which gives the handle identifiers in a URI format
does that help?
from rdryad.
Ok, I updated the package.
It does work with the good DOI 10.5061/dryad.9t0n8/1
which is the second one in dc.identifier
field. So whenever downloading data, I should look at this field, parse it, and take the second one?
Dryad's architecture is not very clear to me, why would a data archive with a single file would have two DOIs? I'll try to look at other dryad repositories to see if they show the same problem.
It seems to be the same for example for doi:10.5061/dryad.s58qh, doi:10.5061/dryad.855pg has many files to download, each one has a specific DOI.
a = rdryad::d_solr_search(q = "10.5061/dryad.s58qh")
# http://datadryad.org/solr/search/select?q=10.5061/dryad.s58qh&wt=json
a$dc.identifier
# [1] "doi:10.5061/dryad.s58qh,doi:10.5061/dryad.s58qh/1"
a = rdryad::d_solr_search(q = "10.5061/dryad.855pg")
# http://datadryad.org/solr/search/select?q=10.5061/dryad.855pg&wt=json
a$dc.identifier
# [1] "doi:10.5061/dryad.855pg,doi:10.5061/dryad.855pg/1,doi:10.5061/dryad.855pg/2,
# doi:10.5061/dryad.855pg/3,doi:10.5061/dryad.855pg/4,doi:10.5061/dryad.855pg/5,
# doi:10.5061/dryad.855pg/6,doi:10.5061/dryad.855pg/7,doi:10.5061/dryad.855pg/8,
# doi:10.5061/dryad.855pg/9,doi:10.5061/dryad.855pg/10,doi:10.5061/dryad.855pg/11,
# doi:10.5061/dryad.855pg/12,doi:10.5061/dryad.855pg/13,doi:10.5061/dryad.855pg/14"
So actually the first DOI is only for the data package while all the other ones are for the data files. And similarly for the handles. It was unclear to me because looking at the examples I thought a single handle was enough to download all files, but looking back at them they had different handles than their data packages.
from rdryad.
Related Issues (20)
- CC0 to MIT HOT 1
- More tests HOT 1
- Update to new oai::id_entify fxn for oai CRAN push HOT 2
- Update to solrium from solr
- replace httr with crul HOT 1
- Switch to new solrium setup HOT 1
- fxns to get doi from handle and vice versa
- `dryad_fetch`: may need to rethink which URLs to use to fetch files
- solr fxns: add new dspace archived parameter to queries
- new Dryad API HOT 4
- Not able to download files with r dryad HOT 10
- Uploading to Dryad HOT 12
- How to get files' ids? HOT 6
- Unable to download files from dryad HOT 4
- Arg for specifying target directory for files retrieved by dryad_download? HOT 3
- rdryad::dryad_download() cannot be used in a CRAN package HOT 1
- Suggestion: Progress Counter HOT 1
- Can't pass arguments to dryad_datasets HOT 2
- Archive Package HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rdryad.