-
Notifications
You must be signed in to change notification settings - Fork 1
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
Use api.crossref.org/works/doi/agency route to test Crossref indexing status #152
Comments
agreed, it'd be good to use an existing function for this purpose, rather than reinventing the wheel. Questions:
Above all, of course, metacheck should remain small but very reliable. |
The benchmark looks like doi.org even without any bells/whistles is much faster than crossref with bells/whistles: some_dois <- c(tu_dois(), "10.1000/IDONOTEXIST")
is_doi_cr <- function(x) {
res <- purrr::map_chr(
suppressWarnings(rcrossref::cr_agency(some_dois)),
c("agency", "id"),
.default = "foo"
)
unname(res == "crossref")
}
bench::mark(
biblids::is_doi_found(some_dois),
is_doi_cr(some_dois)
)
The raw speed alone is less of a concern though. The bigger problem is that I can't get multithreaded cr calls to work via rcrossref, though I am not entirely sure why. |
closing in favor of Notice that above benchmarks are, somewhat off the mark, about |
Crossref API provides an API route to obtain DOI agencies per DOI. It is implemented in rcrossref,
rcrossref::cr_agency
so there's no need to use api.doi.org to check DOI indexing status. #147 https://github.com/subugoe/biblids/issues/38Another advantage is that we can call the API as metadata plus members, which likely improves performance #133 https://github.com/subugoe/biblids/issues/37.
Here's a reprex
Created on 2021-02-22 by the reprex package (v0.3.0)
The text was updated successfully, but these errors were encountered: