Latest blog posts
Martyn Rittman
2024 November 15

Research Integrity Roundtable 2024

For the third year in a row, Crossref hosted a roundtable on research integrity prior to the Frankfurt book fair. This year the event looked at Crossmark, our tool to display retractions and other post-publication updates to readers. Since the start of 2024, we have been carrying out a consultation on Crossmark, gathering feedback and input from a range of members. The roundtable discussion was a chance to check and refine some of the conclusions we’ve come to, and gather more suggestions on the way forward.

...Find out more
Dominika Tkaczyk
2024 November 06

How good is your matching?

In our previous blog post in this series, we explained why no metadata matching strategy can return perfect results. Thankfully, however, this does not mean that it’s impossible to know anything about the quality of matching. Indeed, we can (and should!) measure how close (or far) we are from achieving perfection with our matching. Read on to learn how this can be done! How about we start with a quiz? Imagine a database of scholarly metadata that needs to be enriched with identifiers, such as ORCIDs or ROR IDs.

...Find out more
Kornelia Korzec
2024 October 28

Update on the Resourcing Crossref for Future Sustainability research

We’re in year two of the Resourcing Crossref for Future Sustainability (RCFS) research. This report provides an update on progress to date, specifically on research we’ve conducted to better understand the impact of our fees and possible changes. Crossref is in a good financial position with our current fees, which haven’t increased in 20 years. This project is seeking to future-proof our fees by: Making fees more equitable Simplifying our complex fee schedule Rebalancing revenue sources In order to review all aspects of our fees, we’ve planned five projects to look into specific aspects of our current fees that may need to change to achieve the goals above.

...Find out more
Lucy Ofiesh
2024 September 24

Meet the candidates and vote in our 2024 Board elections

On behalf of the Nominating Committee, I’m pleased to share the slate of candidates for the 2024 board election. Each year we do an open call for board interest. This year, the Nominating Committee received 53 submissions from members worldwide to fill four open board seats. We maintain a balanced board of 8 large member seats and 8 small member seats. Size is determined based on the organization’s membership tier (small members fall in the $0-$1,650 tiers and large members in the $3,900 - $50,000 tiers).

...Find out more
  • Menu
search

Documentation

How can I use Event Data?

The main way to access events created by Event Data is via the API, which returns data in JSON format. For example, the following finds the first 500 events:

https://0-api-eventdata-crossref-org.libus.csd.mu.edu/v1/events?rows=500

It is not required, but we recommend that you include your email address. We will not share this information, but can use it to contact you if a problem arises, for example:

https://0-api-eventdata-crossref-org.libus.csd.mu.edu/v1/events?mailto=anon@test.com&rows=500

Full documentation for the API is available. Briefly, the results can be filtered by various parameters based on time, source, and object.

The results can also include facets of the data: summary counts of a certain characteristic. For example, to see the 10 news websites that have produced the most events, use the query:

https://0-api-eventdata-crossref-org.libus.csd.mu.edu/v1/events?rows=0&source=newsfeed&facet=subj-id.domain:10

If you want to make regular and extensive use of the API, we highly recommend reading the full documentation.

Developers are welcome to build applications based on Event Data, however Crossref doesn’t offer a dashboard or plugin to provide Event Data results. Some Jupyter notebooks are available that demonstrate possible uses of Event Data, including accessing all events about a single DOI.

What is the current status of Event Data?

The Crossref status page shows stability of the Event Data service and query response times. You can also track the latest development tasks.

A list of the current agents is available on our Gitlab pages.

Who uses Event Data?

There are a large number of uses for Event Data and it is intended as a free and transparent data source for third parties. Some examples of how the data can be used are the following:

  • Building links between scholarly outputs, such as Scholix
  • Raw data for bibliometrics research, such as COKI
  • Tracking the impact of research outputs, such as HIRMEOS from OPERAS; Atypon; PaperBuzz
  • Input for scholarly information services, such as H1insights

This list is not exhaustive and we are interested to find out how you are using or would like to use Event Data. Please get in touch if you have an interesting use case.

Page owner: Martyn Rittman   |   Last updated 2020-October-06