A Retraction Is Not a Delete Button: How Journal Platforms Should Handle Corrections, Expressions of Concern and Article Versions

Designing transparent post-publication workflows that preserve the scholarly record

A Retraction Is Not a Delete Button: How Journal Platforms Should Handle Corrections, Expressions of Concern and Article Versions

The publication record must change without disappearing

Journal retractions and corrections do not erase an article’s place in the scholarly record. It may need a correction, an expression of concern, a partial retraction or a full retraction. The platform’s job is not to erase the article and pretend it never existed. Instead, it must make the current editorial status unmistakable, preserve the history needed to understand what happened, and communicate the change to readers, indexing services, libraries and other systems.

This is a technology and workflow challenge as much as an editorial one. The National Information Standards Organization’s NISO RP-45-2024, Communication of Retractions, Removals, and Expressions of Concern (CREC), recommends good practice for creating, transferring and displaying metadata for both the original publication and the related notice. It stresses that unclear or inconsistent status information can lead to continued uncritical use of invalidated research. [1] Journal management platforms should therefore treat post-publication updates as first-class workflow objects, not as exceptional website edits handled by email.

Journal retractions and other editorial actions

A correction addresses an error in a published work while leaving the article’s main conclusions usable, depending on the circumstances. An expression of concern alerts readers that an issue is under investigation or that the available evidence is not yet conclusive. A retraction signals that the work should no longer be relied upon as part of the valid scholarly record, though it remains visible for transparency and citation context. Removal is different again and should be exceptional, justified and handled under applicable policy. These actions are not interchangeable labels for ‘something changed.’

The platform should not decide which action is appropriate. That is an editorial and publisher-governance decision, guided by journal policy and publication-ethics standards. COPE’s 2025 retraction guidance addresses when retraction should be considered, what a notice should contain, who should issue it, timing, inconclusive evidence and batch cases. [2] Software should support the decision, record its authorization and implement the resulting status consistently.

Model the article and the notice as linked records

A robust workflow treats the original article, the update notice and each relevant version as connected records. The correction or retraction notice receives its own publication record and identifier where appropriate, and metadata explicitly states which work it updates. Crossref documentation explains that an editorially significant update is typically issued as a separate document with its own DOI and metadata, linked to the original through update relationships. It cautions that silently replacing the original in situ can obscure the scholarly record. [3]

The platform data model should include the relationship type, affected DOI, notice DOI, update date, decision date where appropriate, status, responsible editor or authorized publisher role, notice text, and any links to supporting records. It should also distinguish an early online version, accepted manuscript, version of record and later updated versions. Crossref’s version-control guidance explains the importance of identifying publication stages and linking significant updates so users can understand which version they are viewing. [3]

Make status visible wherever the article travels

For journal retractions, a status label on one page is not enough. Readers may reach an article through a PDF download, search engine, citation manager, library discovery layer, indexing service, aggregator, repository or a third-party reference. Search results and article metadata should not continue to present a retracted work as an ordinary current article.

Crossref’s Crossmark service is designed to help readers discover status updates. It also explains how update metadata connects the notice to the work being updated. [4] Platforms should support correct deposits and display, but also expose status in APIs, metadata feeds, XML exports, sitemaps and repository deposits. Machine-readable status matters because downstream systems cannot reliably act on a warning that exists only as a graphic in a browser.

Design the workflow from concern to resolution

A platform workflow for journal retractions and other editorial notices can begin when a concern is received from an author, reader, institution, reviewer, editor or research-integrity office. Access controls are essential: allegations may contain personal information, sensitive correspondence or material that must not be disclosed prematurely. The system should distinguish a confidential investigation record from public notices.

The editorial team then triages the concern under policy, requests information where appropriate, records conflicts of interest and decides whether an interim expression of concern is warranted. Once the decision is authorized, it creates or updates the public status record and dispatches metadata to Crossref and other downstream services. Avoid designing a system that automatically retracts articles based on similarity scores or automated flags; human editorial and publisher authority must remain explicit.

Preserve version history and the audit trail

Version management becomes important when an article is corrected, republished or linked to an expression of concern. The platform should retain the originally published file, the updated file, a clear list of changes, timestamps, responsible roles, notices and persistent relationships. Readers should be able to tell whether the current HTML or PDF contains the original text, a corrected version or a retraction statement. Staff should be able to reconstruct the state of the record at a previous date.

Not every typo needs a separate notice or DOI. Crossref distinguishes editorially significant changes—those likely to affect the interpretation or crediting of the work—from minor spelling or formatting changes. [4] The journal’s policy should define which changes can be corrected in place and which require a formal notice. The platform can use that policy to route requests, but it should not infer significance from text diffs alone. A one-character change in a chemical formula could matter greatly; a paragraph reflow may not.

Illustrative scenario: a figure is questioned

Suppose a reader reports that a figure in a published paper appears to duplicate an image from another article. The journal manager logs the concern, assigns it to an authorized editor and restricts case documents to the investigation team. Because the concern is serious but not yet resolved, the editor approves an expression of concern.

The platform creates a linked notice record, assigns the correct publication metadata, displays a prominent status on the article page, adds the relationship to Crossref metadata and updates the PDF with a reader-facing notice or link. If the investigation establishes that a correction is appropriate, the editor authorizes it. The correction receives a linked record; the earlier expression of concern is clearly superseded or resolved according to policy. This scenario is illustrative, but it shows why a platform needs linked notices, workflow states, controlled publication and version history.

Support batch journal retractions without losing individual context

Publishers managing many journals may face a group of related updates—for example, a compromised image source, a duplicated dataset, a paper-mill investigation or an issue affecting a special issue. Batch workflows can reduce repetitive administrative effort, but they must not flatten important differences between articles. A shared cause can be referenced across the group, while each article’s individual status remains clear.

The system should provide queue dashboards for overdue cases, pending approvals, failed metadata deposits, unresolved notices and broken links. For multi-journal publishers, templates can standardize the notice structure while preserving journal-specific policy and branding. Audit reports should show both operational performance and record integrity: how quickly statuses reached the article pages, whether DOI relationships were deposited, and whether the public PDF and HTML match the approved state.

A platform checklist for trustworthy journal retractions and updates

Before implementing or upgrading, check for configurable case intake; role-based permissions; conflict-of-interest records; approval and audit trails; versioned notice templates; linked article and notice records; DOI relationships; Crossref/Crossmark support; visible status indicators; PDF and HTML updates; APIs; notifications; and preserved prior versions. Status must reach readers and downstream systems.

Test edge cases: a concern followed by retraction; a correction to supplementary data; multiple article versions; group notices; repository copies; and platform migration. The goal is not simply workflow speed. Readers should be able to identify the current status and reconstruct the record.

Frequently Asked Questions

Should a journal delete a retracted article?

Usually no. The article should remain discoverable with a clear retraction status and a linked notice, unless a justified removal is required under policy or law. The scholarly record needs transparency.

What is the difference between a correction and a retraction?

A correction fixes an error while the work may remain usable. A retraction indicates the work should no longer be relied upon. The appropriate action is an editorial decision based on evidence and policy.

When should an expression of concern be used?

It can alert readers while a serious concern is investigated or when the available evidence is inconclusive. It should be reviewed and resolved or superseded when the investigation reaches a decision.

Does a correction or retraction need a new DOI?

For editorially significant updates, best practice is generally to issue a separate notice with its own DOI and link it to the original record. Minor changes may be handled differently under publisher policy and Crossref guidance.

What should a journal management platform automate?

It can manage intake, permissions, approvals, notice templates, linked records, metadata deposits, notifications, audit trails and status display. It should not make the editorial decision to correct or retract automatically.

How can publishers ensure databases show the updated status?

Deposit accurate Crossref update relationships, use Crossmark where appropriate, expose machine-readable metadata through APIs and feeds, and verify that repositories, aggregators and indexing partners receive the notice.

References and Further Reading

1. NISO, RP-45-2024: Communication of Retractions, Removals, and Expressions of Concern

2. COPE Council, Retraction Guidelines, version 3, August 2025

3. Crossref, Version Control, Corrections and Retractions

4. Crossref, Participating in Crossmark

5. Crossref, Crossmark Documentation

From the digital desk

Make room for a useful publishing read.

Email updates on digital editions, connected workflows and the journeys readers take.

Confirm your email to join. Updates only from this publication.