Latest blog posts
Martyn Rittman
2021 June 11

Event Data: Help us fill in the gaps

To date, we have collected around 740 million from 12 different source since we launched our Event Data service service in 2017. Each event is an online mention of the research associated with a DOI, either via the DOI directly or using the associated URL. However, we know that there is much more out there. Because of this, we would like to explore where we could expand. We invite proposals to conduct a gap analysis for Event Data sources, looking at what we currently collect and seeing what more could be added.

...Find out more
Martyn Rittman
2021 June 09

An Advisory Group for Preprints

We are delighted to announce the formation of a new Advisory Group to support us in improving preprint metadata. Preprints have grown in popularity over the last few years, with increasing focus brought by the need to rapidly disseminate knowledge in the midst of a global pandemic. We have supported metadata deposits for preprints under the content type ‘posted content’ since 2016, and members currently register a total of around 17,000 new preprints metadata records each month.

...Find out more
Geoffrey Bilder
2021 June 07

Time to put the "R" back in "R&D"

It is time to put the ‘R’ back into R&D. The Crossref R&D team was originally created to focus on the kinds of research projects that have allowed Crossref to make transformational technology changes, launch innovative new services, and engage with entirely new constituencies. Some Illustrious projects that had their origins in the R&D group include: DOI Content Negotiation Similarity Check (originally CrossCheck) ORCID (originally Author DOIs) Crossmark The Open Funder Registry The Crossref REST API Linked Clinical Trials Event Data Grant registration ROR And for each project that has graduated, there have been several that have not.

...Find out more
Ginny Hendricks
2021 June 03

The road ahead: our strategy through 2025

This announcement has been in the works for some time, but everything seems to take longer when there is a pandemic going on, including finding time and headspace to plan out our strategy for the next few years. Over the last year or so we have had our heads down addressing how to scale our 20-yr-old system and operation – and adapting to new ways of working. But we’ve also spent time talking to people, forging alliances, looking ahead, and making plans.

...Find out more
  • Menu
search

Documentation

XML query results and errors

Query results may be requested in three different formats: XSD_XML, UNIXREF, and UNIXSD.

UNIXSD is the recommended and most robust format, but XSD_XML is the default for many services for legacy reasons.

Possible errors returned by malformed or insufficient queries include:

  • an invalid XML query will return no result (<body/>)
  • either first page or author must be supplied
  • either ISSN or journal title must be supplied
  • unreasonable DOI found (an unreasonable DOI does not follow the expected DOI format (10.XXXX/yyy...) and/or exceeds 200 characters)
  • piped query must contain either 9 pipes (for journals) or 11 pipes (for books/conference proceedings)
  • either ISSN/ISBN or series/volume title must be supplied.

Page owner: Jennifer Kemp   |   Last updated 2020-April-08