This document discusses Crossref's metadata infrastructure and event data clearinghouse. It provides an overview of the types of metadata and scholarly activity data that Crossref collects from various sources and makes available through its API. This includes citations, social media engagements, downloads and other "events" related to published works. The document outlines how this centralized infrastructure benefits the research community by enabling use cases like discovery, collaboration and research assessment.

1. Who’s using
your content?

2. Metadata In/Metadata Out
• Cited-by Linking
• Crossref Event Data
• The Crossref Metadata API

3. (coming soon!)

4. In a nutshell…
• open clearinghouse of data on publications
activity online
• tracking events such as shares, mentions,
discussions, recommendations, usage, etc.
• for publishers, funders, institutions, media
outlets, technology providers, etc. to enable
research monitoring, discovery, and
information management

5. Initial DET Sources
BLOGS & REFERENCE
WORKS
SOCIAL
BOOKMARKS
SOCIAL SHARES
& DISCUSSIONS
LINKS TO RESEARCH
ENTITIES
Research Blogging CiteULike Facebook ORCiD
ScienceSeeker Mendeley Reddit DataCite
Wordpress.com Twitter Europe PMC
Database Citations
Wikipedia

6. Clearinghouse as infrastructure
A central point for collecting and propagating data to
the community, benefits of scale and ease of access:
• no need to manage multiple online sources where
scholarly activity occurs
• no need for individual bilateral agreements between
consumer and sources
• comprehensive tracking coverage across publishers

7. Infrastructure transparency & trust
Data is:
• comprehensive - collected for all Crossref
DOIs, regardless of publisher
• open - made openly available to all
• comparable - collected in a standard way
across aggregators
• auditable & portable
• long term data preservation

8. Data, not metrics
Ready to use:
programmatically
available for tool
development & reuse

9. Use cases
• Surface qualitative stories about researcher work
• Report on the reach of research within specific communities &
public at large
• Identify hot, new areas for journal development
• Inform editor and reviewer recruitment efforts
• Discover relevant research
• Discover new collaborators
• Track funding results
• Report on institutions and consortia outputs…

10. This is the
presentatio
n title
Meeting, Location, Date
Presenter
Presenter Title
@twittername
Have you taken a peek inside yet?

11. This is the
presentatio
n title
Meeting, Location, Date
Presenter
Presenter Title
@twittername

12. This is the
presentatio
n title
Meeting, Location, Date
Presenter
Presenter Title
@twittername
Keep an eye on our development
Chicken by anbileru adaleru from the The
Noun Project
We will continue to add new data sources to the early
preview interface as they are developed. Be warned
though, we may break a few eggs from time to time!
So keep an eye on our information page at
http://eventdata.crossref.org/ as well as the Crossref
Blog for regular progress updates.
But if you’re game, why not jump straight on to
http://api.eventdata.crossref.org/ and start your data
discovery journey.

14. • Search, filter, facet, sample Crossref metadata
• Free to use
• Do whatever you want with the data
• Code publicly available: http://github.com/CrossRef

15. Titles, authors, ISSNs, ISBNs
Basic metadata
Journal articles, conference proceedings, data, standards
Funding Information
Funder identifiers, award numbers
License Information
License URIs (NISO ALI)
Full-text locations
URIs direct to full-text articles (used in TDM)
ORCIDs
Significant updates
Retractions, corrections
Publishers Crossref

16. Until recently:
“Tell me which licenses eLife uses”
• Sign up to CrossRef Enhanced Metadata Services
• Download ~1TB of XML via OAI-PMH
• Parse and scan for eLife’s DOIs, record licenses

17. With our REST API
1. Find member ID for eLife:
http://api.crossref.org/members?query=elife
2. Ask for their licenses
http://api.crossref.org/members/4374/works?
facet=license:*&rows=0

18. CC-BY 3.0 and 4.0, a bit of CC0

19. Sample Queries
• GET /works
• GET /works/10.5555/12345678
• GET /funders/123
• GET /members/55/works
• GET /licenses
• GET /journals/1234-567X/works
• Response format is JSON, citeproc JSON for works

20. What are people doing with it?
• Search services (including Crossref’s funding and
metadata searches)
• Bibliography / PDF library management tools
• Reporting on funding activities, publishing
• activities, author activities
• Ingest of scholarly metadata (OAI-PMH replacement)
and metadata lookup
• Locating full-texts for content mining

23. api.crossref.org