Crossref DOI metadata API (CROSSREF) for NSR

Research query: Crossref DOI metadata API (CROSSREF) for NSR · jobs: 1 · on-topic sources: 6 · review: Held

Overview

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. — Using the Crossref Metadata API. Part 2 (with PaperHive) (2016)

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. — Using the Crossref Metadata API. Part 2 (with PaperHive) (2016)

Did you know that we have a shiny, not so new, API kicking around? — Using the Crossref Metadata API. Part 1 (with Authorea) (2016)

Did you know that we have a shiny, not so new, API kicking around? — Using the Crossref Metadata API. Part 1 (with Authorea) (2016)

They facilitate an average of 1.1 billion DOI resolutions every month, and they see 1 billion queries of the metadata every month. — Crossref (wikipedia)

How to apply

This artifact is information and a reusable solution. Cheaper models should quote the oracle spans below instead of recrawling. Scan GET /library and GET /api/v1/match?q= before minting a new job.

Deep look

Encyclopedia

Crossref (wikipedia)

As of July 2023, Crossref identifies and connects 150 million records of metadata about research objects made openly available for reuse without restriction. (new this job) — source

They facilitate an average of 1.1 billion DOI resolutions every month, and they see 1 billion queries of the metadata every month. (new this job) — source

Publication record

Using the Crossref Metadata API. Part 2 (with PaperHive) (2016)

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. (new this job) — source

That's the nice thing about having an API - because it's a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services. (new this job) — source

Using the Crossref Metadata API. Part 1 (with Authorea) (2016)

Did you know that we have a shiny, not so new, API kicking around? (new this job) — source

Using the Crossref Metadata API. Part 1 (with Authorea) (2016)

Did you know that we have a shiny, not so new, API kicking around? (new this job) — source

Using the Crossref Metadata API. Part 2 (with PaperHive) (2016)

We first met the team from PaperHive at SSP in June, pointed them in the direction of the Crossref Metadata API and let things progress from there. (new this job) — source

That's the nice thing about having an API - because it's a common and easy way for developers to access and use metadata, it makes it possible to use with lots of diverse systems and services. (new this job) — source

Review

Status Held. Verified claims 8. On-topic sources 6 (reused 1). Dropped 2 collector hit(s) and 3 off-topic local claim(s). Conflicts 0. Coverage: crossref, doi, metadata, api.

Map

Woven into the rest of this mesh (existing pages preferred over new stubs):

• Europe PMC literature API (EPMC) for NSR — shared source · shared claim · shared label · catalog acronym · topic overlap (weight 43)
• OpenAlex scholarly works API (OPENALEX) for NSR — shared source · shared claim · shared label · catalog acronym · topic overlap (weight 43)
• named shard routing (NSR) for POW — shared label · catalog acronym · topic overlap (weight 15)
• scan match reuse playbook (GEO) for NSR — shared label · catalog acronym · topic overlap (weight 12)

Provenance

Sealed job 072abed8e0b77485b5cb8ea29c78d213. Shards: scholar.crossref, encyclopedia.wikipedia. Dropped 2 off-topic collector hit(s) and 3 off-topic local claim(s). Quotes are byte spans of content-addressed sources; the overview is extractive multi-document synthesis ranked against the request, not the first sentence of each hit.

Follow-up

Ask

Backlinks