Examples
Worked examples
- Is an instance
A publisher's production system tags a retracted article's Crossref deposit with retraction-status metadata following CREC's essential elements at the time the retraction is issued. Crossref, PubMed, and downstream reference managers can then surface the retracted status automatically on any record derived from that metadata, without each downstream system's maintainers having to separately notice and re-key the change.
- Is an instance
A journal platform implements CREC's display recommendations by prepending "RETRACTED:" to both the HTML page title and the PDF watermark of an affected article, and linking a clearly labelled, independently findable retraction notice from the article page itself, rather than only listing the notice in a table of contents or a separate errata page.
Counter-examples
Looks similar, but isn't
- Not an instance
A journal issues a retraction only as a standalone notice — a short paragraph in an upcoming issue or a note buried in an editorial column — without updating the original article's own metadata, webpage, HTML title, or PDF. A careful human reader who happens to find the notice learns the article was retracted; Crossref, PubMed, citation managers, and anyone who lands on the article page directly do not. This is exactly the machine-readability gap CREC's recommended practice was written to close, not an example of CREC in practice.
Editorial commentary
Retraction notices have existed for decades, but for most of that time each publisher represented them differently — or not at all in machine-readable form — which meant a retracted paper could keep circulating, being cited, and being indexed as though nothing had changed, simply because the systems that surface it to readers had no reliable signal to act on. NISO’s CREC Recommended Practice (RP-45-2024) exists to close that gap by standardizing the metadata and display conventions publishers, platforms, and aggregators use to communicate a retraction, removal, or expression of concern.
Why CREC exists
The Recommended Practice responds directly to two converging pressures in scholarly publishing: retraction volume has grown substantially in recent years, including a rise in coordinated “mass retraction” events tied to paper mills and systematic research-integrity investigations, and the representation of retracted status across publishers, indexers, and platforms had been unclear and inconsistent enough that invalidated research kept being read, cited, and built on without readers or downstream systems reliably knowing its status. NISO’s own framing of the problem is that inconsistent representation of retracted status directly enables continued reliance on research that has already been formally withdrawn or flagged.
Development began following the 2021 NISO Plus conference, where the need for a shared standard was raised, and proceeded with support from the Alfred P. Sloan Foundation. The NISO CREC Working Group that produced RP-45-2024 comprised more than two dozen participants representing publishers, technology vendors, researchers, and libraries. The draft went through open public comment before formal publication on June 27, 2024 (ISBN 978-1-950980-26-0; DOI 10.3789/niso-rp-45-2024). The practice has since been endorsed by the Committee on Publication Ethics (COPE) as guidance consistent with its own retraction principles.
What CREC actually specifies
CREC operates on two parallel tracks, and a full implementation addresses both:
Metadata (machine-readable)
The Recommended Practice defines metadata elements for the original publication, for the retraction/removal notice itself, and for expressions of concern — covering things like the type of notice, the date it was issued, and a reason where available — and classifies each element as Essential, Essential if Available, or Recommended. This is the part of CREC that lets a status change propagate automatically: once a publisher deposits corrected metadata (for example, to Crossref), any system that consumes that metadata — a citation database, a reference manager, a library discovery layer, an aggregator — can reflect the retracted or flagged status without a human at each downstream system separately noticing and updating a record. This is the same underlying principle behind CrossMark, which lets a reader check a PDF or web page against the publisher’s record of its current status; CREC standardizes what that status metadata should actually contain for retraction-type events specifically.
Display (human-readable)
CREC also specifies how the status should appear to a reader encountering the content directly, independent of whatever metadata a downstream system may or may not have consumed: prepending “RETRACTED:” to the article’s title, watermarking and clearly labelling both the HTML and PDF versions of the content, and ensuring the retraction, removal, or expression-of-concern notice itself is a distinct, easily located, and properly linked document — not a passing mention in an unrelated editorial note or a change that’s only visible in a table of contents.
How CREC relates to editorial retraction guidance
CREC is deliberately scoped as a communication standard, not an editorial-ethics standard. The decision of whether a paper should be retracted, corrected, or flagged with an expression of concern is governed by editorial-ethics guidance — principally COPE’s retraction guidelines — and remains an editorial judgment made by a journal, publisher, or institution. See CASRAI’s Retraction and Expression of concern entries for that editorial-decision side, and How to Write a Retraction Statement for the mechanics of drafting the notice text itself. CREC picks up only after that editorial decision has been made: it governs how the resulting notice and status get represented in metadata and on-page display so the decision actually reaches readers and systems reliably, rather than existing only as a notice someone has to happen upon.
Why this matters for research administrators and librarians
For anyone responsible for institutional repositories, library discovery layers, or citation-tracking workflows, CREC adoption by a publisher or platform is a practical signal: it indicates that retraction status is likely to propagate into the metadata your own systems ingest, rather than requiring manual cross-checking against retraction-watch-style databases. Conversely, a publisher or repository that has not implemented CREC-consistent metadata is a place where that automatic propagation cannot be assumed, and manual verification of an item’s current status remains necessary.
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="NISO CREC (Communication of Retractions, Removals, and Expressions of Concern)"
vocab-term-identifier="https://casrai.org/dictionary/term/niso-crec" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/niso-crec",
"name": "NISO CREC (Communication of Retractions, Removals, and Expressions of Concern)",
"identifier": "https://casrai.org/dictionary/term/niso-crec",
"description": "<p><strong>NISO CREC</strong> refers to <strong>NISO RP-45-2024</strong>, the <em>Communication of Retractions, Removals, and Expressions of Concern</em> Recommended Practice published by the National Information Standards Organization (NISO) on June 27, 2024 (DOI 10.3789/niso-rp-45-2024). CREC is not a new editorial rule about *when* something should be retracted — that judgment remains the domain of editorial-ethics guidance such as COPE's Retraction Guidelines. It is a communication standard about *how* a retraction, removal, or expression of concern (EoC), once decided, gets represented consistently in metadata and on-page display so that both human readers and machine systems (indexers, citation databases, reference managers, library discovery layers, aggregators) can detect and propagate the status automatically, rather than relying on someone noticing a notice.</p><p>A publisher, platform, or content system is applying CREC when it implements RP-45-2024's paired recommendations: (1) <strong>metadata</strong> — structured, machine-readable status elements attached to the item's record (classified in the Recommended Practice as Essential, Essential if Available, or Recommended), covering the original publication, the retraction/removal/EoC notice itself, dates, and reasons; and (2) <strong>display</strong> — visible, human-facing signals, including prepending “RETRACTED:” to the title, watermarking and labelling the content in both HTML and PDF renderings, and linking a distinct, easily located notice to the affected item rather than burying it in an unrelated editorial page.</p>",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/publishing#set",
"url": "https://casrai.org/dictionary/term/niso-crec",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"dateModified": "2026-07-23T07:34:12",
"inLanguage": "en"
}






