Latest blog posts
Ed Pentz
2022 November 17

How funding agencies can meet OSTP (and Open Science) guidance using existing open infrastructure

In August 2022, the United States Office of Science and Technology Policy (OSTP) issued a memo (PDF) on ensuring free, immediate, and equitable access to federally funded research (a.k.a. the “Nelson memo”). Crossref is particularly interested in and relevant for the areas of this guidance that cover metadata and persistent identifiers—and the infrastructure and services that make them useful. Funding bodies worldwide are increasingly involved in research infrastructure for dissemination and discovery.

...Find out more
Martyn Rittman
2022 November 09

Better preprint metadata through community participation

Preprints have become an important tool for rapidly communicating and iterating on research outputs. There is now a range of preprint servers, some subject-specific, some based on a particular geographical area, and others linked to publishers or individual journals in addition to generalist platforms. In 2016 the Crossref schema started to support preprints and since then the number of metadata records has grown to around 16,000 new preprint DOIs per month.

...Find out more
Patrick Vale
2022 October 19

Forming new relationships: Contributing to Open source

TL;DR One of the things that makes me glad to work at Crossref is the principles to which we hold ourselves, and the most public and measurable of those must be the Principles of Open Scholarly Infrastructure, or POSI, for short. These ambitions lay out how we want to operate - to be open in our governance, in our membership and also in our source code and data. And it’s that openness of source code that’s the reason for my post today - on 26th September 2022, our first collaboration with the JSON Forms open-source project was released into the wild.

...Find out more
Rachael Lammey
2022 October 17

ISR part three: Where does Crossref have the most impact on helping the community to assess the trustworthiness of the scholarly record?

Ans: metadata and services are all underpinned by POSI. Leading into a blog post with a question always makes my brain jump ahead to answer that question with the simplest answer possible. I was a nightmare English Literature student. ‘Was Macbeth purely a villain?’ ‘No’. *leaves exam* Just like not giving one-word answers to exam questions, playing our role in the integrity of the scholarly record and helping our members enhance theirs takes thought, explanation, transparency, and work.

...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