New Crossref REST API coming soon

Question

New Crossref REST API coming soon

ppolischuk opened this issue 3 years ago · 6 comments

Hi,

Thank you for maintaining one of the documented libraries for using the Crossref REST API.

We’ve been working on a new version of the REST API, replacing the Solr backend with Elasticsearch and moving from our own hardware in a datacenter to a cloud platform.

We plan to cutover to the new version shortly (expect an official announcement on our blog in the next few days with more details), and wanted to invite you to test it out before the official cutover.

Please check it out at https://api.production.crossref.org/

During the cutover phase (expected to last a few weeks), traffic will be redirected to the above domain on a pool by pool basis. Once all traffic is using the new service, we will continue to use the api.crossref.org domain, so please do not update anything to use the temporary domain.

Let me know if you have any questions. Issues can be filed into our GitLab issue repository, or I’ll keep an eye on this thread.

Thanks again,
Patrick

Answer 1 · 2021-07-28T18:56:23.000Z

Hi @ppolischuk can you confirm that returning all facets calling https://api.crossref.org/journals/1803-2427/works?facet=t will be no longer supported?

Answer 2 · 2021-07-29T17:03:06.000Z

Thank you, I can reproduce that issue and will discuss with our team shortly. I'll be tracking that here: https://gitlab.com/crossref/issues/-/issues/1393

Answer 3 · 2021-08-05T20:29:05.000Z

Hi @njahn82,

Presently, returning all facets via your example request does not work in the new API via the public pool, but still works via the polite and plus pools still being served by the old API, eg https://api.crossref.org/journals/1803-2427/works?facet=t&mailto=ppolischuk@crossref.org

However, performance via the polite and plus pools is extremely slow for facet=* requests, and according to our logs it is almost never used. It's unclear what use cases or workflows this feature serves, so we're considering deprecating it and removing it from the list of valid facets in the 400 response.

Did you previously use this feature? If so, how did you use it?

Answer 4 · 2021-08-17T18:33:39.000Z

Hi @ppolischuk,

Thanks for catching up. I am also unsure about how and to which extent it was used. As a fix, I pasted all valid facets together instead of using facet=* and the performance seems to be ok.

https://api.crossref.org/works/10.13039/100000001/works?rows=0&facet=issn%3A%2A%2Ccontainer-title%3A%2A%2Cjournal-issue%3A%2A%2Clink-application%3A%2A%2Caffiliation%3A%2A%2Cassertion%3A%2A%2Cassertion-group%3A%2A%2Corcid%3A%2A%2Cupdate-type%3A%2A%2Cfunder-name%3A%2A%2Carchive%3A%2A%2Ccategory-name%3A%2A%2Crelation-type%3A%2A%2Cpublished%3A%2A%2Csource%3A%2A%2Ctype-name%3A%2A%2Cpublisher-name%3A%2A%2Cjournal-volume%3A%2A%2Clicense%3A%2A%2Cfunder-doi%3A%2A

Answer 5 · 2021-08-18T11:08:20.000Z

{rcrossref} dev version was updated to reflect Crossref's REST API updates for the public and polite pool.

The package will be prepared for CRAN submission in the upcoming weeks.

Answer 6 · 2022-11-12T09:15:13.000Z

The latest version is now also available on CRAN