Latest blog posts

2023 September 11

News: Crossref and Retraction Watch

https://doi.org/10.13003/c23rw1d9 Crossref acquires Retraction Watch data and opens it for the scientific community Agreement to combine and publicly distribute data about tens of thousands of retracted research papers, and grow the service together 12th September 2023 —– The Center for Scientific Integrity, the organisation behind the Retraction Watch blog and database, and Crossref, the global infrastructure underpinning research communications, both not-for-profits, announced today that the Retraction Watch database has been acquired by Crossref and made a public resource.

...Find out more

2023 September 07

Open Funder Registry to transition into Research Organization Registry (ROR)

Today, we are announcing a long-term plan to deprecate the Open Funder Registry. For some time, we have understood that there is significant overlap between the Funder Registry and the Research Organization Registry (ROR), and funders and publishers have been asking us whether they should use Funder IDs or ROR IDs to identify funders. It has therefore become clear that merging the two registries will make workflows more efficient and less confusing for all concerned.

...Find out more

2023 September 06

Open funding metadata through Crossref; a workshop to discuss challenges and improving workflows

Ten years on from the launch of the Open Funder Registry (OFR, formerly FundRef), there is renewed interest in the potential of openly available funding metadata through Crossref. And with that: calls to improve the quality and completeness of that data. Currently, about 25% of Crossref records contain some kind of funding information. Over the years, this figure has grown steadily. A number of recent publications have shown, however, that there is considerable variation in the extent to which publishers deposit these data to Crossref.

...Find out more

2023 July 06

Perspectives: My thoughts on starting my new role at Crossref

My name is Johanssen Obanda. I joined Crossref in February 2023 as a Community Engagement Manager to look after the Ambassadors program and help with other outreach activities. I work remotely from Kenya, where there is an increasing interest in improving the exposure of scholarship by Kenyan researchers and ultimately by the wider community of African researchers. In this blog, I’m sharing the experience and insights of my first 4 months in this role.

...Find out more

Documentation

Suffixes containing special characters

You might see (or inherit responsibility for) older DOIs which contain other characters, and require special treatment in a URL:

Encode hash or pound sign # as %23
Do not encode left bracket (or less than) < as < and right bracket (or greater than) > as > when resolving DOIs or retrieving metadata from our REST API to retrieve the metadata (see below)
Do not encode forward slash / when resolving DOIs or retrieving metadata from our REST API

For example, use the following when resolving DOIs with special characters:

https://doi.org/10.1002/(SICI)1521-3951(199911)216:1<135::AID-PSSB135>3.0.CO;2-%23

instead of:

https://doi.org/10.1002/(SICI)1521-3951(199911)216:1<135::AID-PSSB135>3.0.CO;2-#

And, to retrieve the metadata in our REST API, using those same DOI examples use:

https://api.crossref.org/works/10.1002/(SICI)1521-3951(199911)216:1%3C135::AID-PSSB135%3E3.0.CO;2-%23

instead of:

https://api.crossref.org/works/10.1002/(SICI)1521-3951(199911)216:1<135::AID-PSSB135>3.0.CO;2-#

Page owner: Isaac Farley | Last updated 2021-December-03