I failed to confirm this information at https://retractiondatabase.org: this record is associated to an expression of concern (visible in the JSON above: update-to[1]) but there is no mention of a retraction.
We took a look at the logs for the retraction watch csv file, and the RetractionNature value for record 19937 was changed from "retraction’ to “expression of concern” on 2026-03-26. Prior to that, the retraction watch database did show ‘retraction’ for this item.
But, instead of modifying the existing update in our API, we added a second update assertion with the same record ID, same date/time, same source info, but just the ‘type’ and ‘label’ values changed.
I’ve asked our technical team to look into this behavior and ideally adjust how we handle changes or corrections in retraction watch records to overwrite rather than duplicate the assertion in our API.
Overwriting instead of complementing (the current situation) seems more appropriate indeed, so as to reflect the latest state of the Retraction Watch Database.
Hello @gcabanac . I wanted to note that you may follow our progress on this improvement here: https://crossref.atlassian.net/browse/CR-2746. We have set this issue as a medium priority, so likely not the quickest turnaround. Shayn or I will update you when we have more information.
