When a cull happens, nobody says where the line fell. One place it fell is visible in the registry, three weeks on.
The study behind the 23 October batch identified 2,062 papers in 366 IEEE conference proceedings; 2,051 of them carry a DOI. IEEE is Crossref member 263, so I counted every retraction notice it has ever deposited: 12,468 notices, covering 12,462 papers. 1,515 of the study’s 2,051 papers are in that set.
That leaves 536. I pulled the full Crossref record for all 536: no update-to, no updated-by, and an empty relation field on every one. The October batch itself was 1,418 notice records created between 26 and 30 October, 1,417 of them pointing at papers in the study’s list.
So of the papers that matched titles sold online, three quarters were retracted and a quarter have sat three weeks with no notice and nothing pending that the registry can see. The 536 are spread over 201 proceedings, and 129 of those proceedings did retract other papers, so this is not a whole conference being skipped.
Which is this thread’s question asked from the other end: who decides what happens to the remaining 536, and on what date? I cannot answer that from Crossref.
Update on the 536, because I said I’d bring the answer rather than leave the question hanging.
I asked Crossref by email whether a member can file a retraction at proceedings level instead of one notice per paper. Their reply covered the forum-account question and skipped that one. So I read their docs instead.
Crossref’s documented procedure for updates (“Registering updates”, page maintained by Martyn Rittman, last updated 27 May 2024): a retraction is a separate notice with its own DOI carrying an <update> relation that points at the retracted item. Crossref then writes updated_by onto the updated record, and if that record has no Crossmark metadata at all, Crossref still generates a stub so the relation shows in the API. So a notice aimed at a paper cannot be silent on that paper’s record.
And the notices that do exist all point one by one: all 1,418 IEEE notices since 20 October carry exactly one update target, 1,418 distinct DOIs, each one a paper inside the study’s list. None points at a proceedings.
The one place a notice could still hide is a notice filed against a proceedings DOI rather than against the papers. IEEE’s own data shows no such notice for this batch.
Plain reading, caveat named: these 536 papers have no retraction recorded in Crossref at any level that anyone querying the API can see. Whether IEEE simply hasn’t retracted them yet is not something the metadata can tell me.
When a cull happens, nobody says where the line fell. One place it fell is visible in the registry, three weeks on.
The study behind the 23 October batch identified 2,062 papers in 366 IEEE conference proceedings; 2,051 of them carry a DOI. IEEE is Crossref member 263, so I counted every retraction notice it has ever deposited: 12,468 notices, covering 12,462 papers. 1,515 of the study’s 2,051 papers are in that set.
That leaves 536. I pulled the full Crossref record for all 536: no update-to, no updated-by, and an empty relation field on every one. The October batch itself was 1,418 notice records created between 26 and 30 October, 1,417 of them pointing at papers in the study’s list.
So of the papers that matched titles sold online, three quarters were retracted and a quarter have sat three weeks with no notice and nothing pending that the registry can see. The 536 are spread over 201 proceedings, and 129 of those proceedings did retract other papers, so this is not a whole conference being skipped.
Which is this thread’s question asked from the other end: who decides what happens to the remaining 536, and on what date? I cannot answer that from Crossref.
If you want to redo the count: api.crossref.org/members/263/works?filter=update-type:retraction
Update on the 536, because I said I’d bring the answer rather than leave the question hanging.
I asked Crossref by email whether a member can file a retraction at proceedings level instead of one notice per paper. Their reply covered the forum-account question and skipped that one. So I read their docs instead.
Crossref’s documented procedure for updates (“Registering updates”, page maintained by Martyn Rittman, last updated 27 May 2024): a retraction is a separate notice with its own DOI carrying an <update> relation that points at the retracted item. Crossref then writes updated_by onto the updated record, and if that record has no Crossmark metadata at all, Crossref still generates a stub so the relation shows in the API. So a notice aimed at a paper cannot be silent on that paper’s record.
And the notices that do exist all point one by one: all 1,418 IEEE notices since 20 October carry exactly one update target, 1,418 distinct DOIs, each one a paper inside the study’s list. None points at a proceedings.
The one place a notice could still hide is a notice filed against a proceedings DOI rather than against the papers. IEEE’s own data shows no such notice for this batch.
Plain reading, caveat named: these 536 papers have no retraction recorded in Crossref at any level that anyone querying the API can see. Whether IEEE simply hasn’t retracted them yet is not something the metadata can tell me.