GCRI · 登记册
更正与版本管理
Every published record will one day need to change: a typing error, a revised figure, a withdrawn claim, a new release of a dataset. What matters is whether the change is visible, linked and propagated, or silent. This page sets out how corrections, retractions and new versions are recorded, why superseded assertions keep circulating after they are corrected, and what editors and stewards need to run a correction route that readers can follow.
工作如何开展。
Interoperability console
Correction and versioning · Crosswalk · Profile v3
Field mappings
| identifier | id | copy | 通过 |
| evidence_label | quality.label | enum map | 通过 |
| licence | rights.licence | SPDX id | Ambiguous |
| version | version | semver | 通过 |
符合性
图Interoperability console: example names and illustrative values, not a record or a live system.
Correction and versioning: how the risk develops.
Superseded assertions and correction routes. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Silent edits
A value is overwritten in place without a version change or a notice. Anyone who downloaded or cited the earlier state now holds a record that no longer matches the source, and nothing tells them so.
Corrections stop at the source
A notice is issued where the record lives, but copies in aggregators, indexes, reference managers and derived datasets are not updated. The superseded assertion keeps circulating downstream and is cited as current.
Version forks
Preprint, accepted manuscript and version of record, or successive dataset releases, are registered without relations between them. Citations split across versions, and a correction made to one never reaches the others.
Reliance compounds
Corrected or retracted findings feed systematic reviews, models, guidelines and funding cases. Each reuse builds on the flawed assertion, so the cost of a late correction grows with every layer that came to depend on it.
How correction and versioning is modelled, measured and tested.
模型、其假设、数据和不确定性，以科学家或工程师会核查的形式呈现。结构遵循已发表的方法。所取数值仅为示意，不是研究发现。
数据集与来源追溯
The data classes behind correction and versioning and what is recorded about each before it is used.
| 数据类别 | 已记录溯源 | 已说明分辨率 | 许可已核查 |
|---|---|---|---|
| 卫星影像，光学与雷达 | 传感器、处理级别、获取日期 | 像元大小和重访周期 | 每景 |
| 再分析与气候模式输出 | 模型、实验、成员、版本 | 格网与时间步长 | 每次发布 |
| 原位传感器和测量站 | 测站、仪器、校准记录 | 点位与采样率 | 每个网络 |
| 人口与资产暴露 | 方法、版本年份、输入来源 | 单元大小和单位 | 每次发布 |
| 边界与参考地理 | 制作者、版本、日期 | 比例尺 | 每个版本 |
- 沿袭
- 从来源到图表的 W3C PROV 记录
- 原则
- FAIR：可查找、可访问、可互操作、可复用
- 缺口
- 显示为缺失，绝不悄然填充
Corrections in one domain must reach every product that used the data.
Corrections are published with every edition of 报告 under COPE guidance. Versions would follow the identifier rules of NS-1 in the proposed Nexus Standards.
- Error reports with evidence.
- Source revisions that need propagating.
衡量什么，以及衡量得如何。
每个指标都注明其单位、频率、背后的来源类型以及数值将附带的证据标签。此处不显示数值：数值由计划依据其自身权限提供。
| 指标 | 单位 | 节奏 | 来源类型 | 标签 |
|---|---|---|---|---|
| 已发布的更正 | count by type per period | 每月 | Correction trail | 观测 |
| Time from report to correction notice | 天 | per case | Case records | 观测 |
| Content changes without a version increment | 计数 | 每周 | Content hash comparison | 观测 |
| Version chain completeness | share of versions linked to a predecessor | 每月 | Relation metadata | 观测 |
| Retracted items linked to their notice | share of retracted items | 每月 | Crossmark and retraction records | 观测 |
| Superseded records still cited as current | count of citing works | 每季度 | Citation graph | 估算 |
| Corrections reflected by downstream aggregators | share of sampled aggregators | 每季度 | Aggregator sampling | 估算 |
证据来自何处。
具名公共数据集与机构记录，各自注明许可类别。依协议获得的来源仅按其条款使用，绝不再次发布。
| 来源 | 它提供什么 | 许可类别 |
|---|---|---|
| Retraction Watch Database | Records of retractions, corrections and expressions of concern across publishers | Open, distributed by Crossref |
| Crossmark | Publisher-deposited update status linking corrections and retractions to the original work | Open metadata via Crossref |
| Crossref and DataCite relation metadata | Relations such as is new version of, is previous version of and is obsoleted by | Open metadata; CC0 for DataCite |
| PubPeer | Post-publication comments that often surface errors before formal notices | Public comments under site terms |
| Internet Archive Wayback Machine via Memento | Time-stamped captures showing what a page said at a given moment | Free access under archive terms |
| Software Heritage | Archived source code with intrinsic identifiers for every version | Open archive, terms per content licence |
由谁决定，以及证据服务于什么。
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| 谁来决定 | 问题 | 本页面服务的证据 |
|---|---|---|
| Journal editors and publishers | Whether an error warrants a correction, an expression of concern or a retraction | COPE guidance, the nature of the error, and the citing and derived works that relied on it |
| Data stewards and repository managers | Whether a change is a correction to the same version or a new version | The versioning policy, the extent of the change and the identifiers already cited |
| Research integrity offices | Whether a pattern of corrections signals possible misconduct needing investigation | Correction history across records by the same contributors, with dates and stated reasons |
| Systematic reviewers and guideline panels | Whether included evidence must be re-examined after a correction | Retraction and correction status of every included item at the review date |
该主题产生的产出
- Correction trails showing each change, its type, author, date and reason
- Version chains linking every release to its predecessor and successor
- Notices for superseded assertions kept visible beside the corrected record
- A published correction route stating whom to contact and how a report is handled
What experts ask about corrections.
- When is a change a correction, an update or a replacement, and how should each be labelled?
- How can a correction reach citations, copies and derived records?
- What must be kept of a superseded version so that past decisions can be understood?
- Who may initiate, review and approve a correction?
- How is a correction itself corrected?
Why uncorrected errors persist.
Studies of retracted research have long shown that flawed papers continue to be cited after retraction, largely because readers meet them through copies, summaries and reference lists that never learn of the change. The same happens with datasets, dashboards and programme descriptions. Silent edits make it worse: when a page changes without notice, readers cannot know that what they cited is no longer what the page says.
Good practice therefore treats records as append-only. A correction creates a new version that points to the one it supersedes, states what changed and why, and is announced through a notice that downstream 系统 can detect. Publishing communities have developed shared guidance for retractions and corrections, and versioned identifiers let citations point to a specific state. The Registry’s procedure is described on corrections and version history.
How versioning works in practice.
- 01
Version chains
Each version records its predecessor and successor, so the full history can be followed.
- 02
Typed changes
A change is labelled as a correction, an update, a supersession or a withdrawal, each with a reason.
- 03
Change notices
Machine-readable notices let copies elsewhere update, a feature discussed under registry interoperability.
- 04
局限
No registry can recall copies it does not control. Notices help only 系统 that read them, and some errors are found too late to change decisions already taken. Correcting a record does not correct the reasoning others built on it.
Where this page’s references lead.
阅读本页时所对照的机构和文件。状态和版本会变化；每个链接都指向发布机构。
问题与解答。
What is the difference between a correction and a new version?
Are retracted records deleted?
How can I tell if a record I cited has changed?
Why do retracted findings keep being cited?
Will an earlier version disappear after a correction?
Can anyone request a correction?
Is a withdrawal the same as a correction?
从本页贡献证据。
报告 is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- 电子邮件网关 GW-GCRI从本页发送证据、更正、案例、方法、审查、翻译或概况投稿。它会带上本页标签送达，由负责的编辑接收。
- Zenodo开放存缴存缴并提交到社区用您的 ORCID iD 在 Zenodo 上发布您自己的记录，然后提交到那里的 Reports 社区。由策展人审核；DOI 仍归您所有。
- 报告GCRI查看所有贡献方式贡献类型、各自的评审方式、您获得的署名、许可协议，以及绝不接受的内容。
切勿发送个人数据、敏感基础设施细节或您无权分享的任何内容。贡献在使用前会经过审查；发送贡献不赋予署名权或编辑权，赞助也绝不能换取研究结论。
法律文件。
本网站上的地图、数据和图表仅作为背景和一般信息展示。它们不是建议、预测或预警；信息的局限见免责声明和数据说明。