Latest blog posts
Martyn Rittman
2021 November 10

Event Data now with added references

Event Data is our service to capture online mentions of Crossref records. We monitor data archives, Wikipedia, social media, blogs, news, and other sources. Our main focus has been on gathering data from external sources, however we know that there is a great deal of Crossref metadata that can be made available as events. Earlier this year we started adding relationship metadata, and over the last few months we have been working on bringing in citations between records.

...Find out more
Rachael Lammey
2021 November 03

Come and get your grant metadata!

Tl;dr: Metadata for the (currently 26,000) grants that have been registered by our funder members is now available via the REST API. This is quite a milestone in our program to include funding in Crossref infrastructure and a step forward in our mission to connect all.the.things. This post gives you all the queries you might need to satisfy your curiosity and start to see what’s possible with deeper analysis. So have the look and see what useful things you can discover.

...Find out more
Geoffrey Bilder
2021 October 27

Update on the outage of October 6, 2021

Update on the outage of October 6th. In my blog post on October 6th, I promised an update on what caused the outage and what we are doing to avoid it happening again. This is that update. Crossref hosts its services in a hybrid environment. Our original services are all hosted in a data center in Massachusetts, but we host new services with a cloud provider. We also have a few R&D systems hosted with Hetzner.

...Find out more
Lindsay Russell
2021 October 21

More new faces at Crossref

Looking at the road ahead, we’ve set some ambitious goals for ourselves and continue to see new members join from around the world, now numbering 16,000. To help achieve all that we plan in the years to come, we’ve grown our teams quite a bit over the last couple of years, and we are happy to welcome Carlos, Evans, Fabienne, Mike, Panos, and Patrick.

...Find out more
  • Menu
search

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 &lt; and right bracket (or greater than) > as &gt; 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