GCRI · Registry
訂正と版管理
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貢献のすべての方法を見る貢献の種類、それぞれの審査方法、受け取るクレジット、ライセンス、決して受け付けないもの。
個人データ、重要インフラの機微な詳細、共有する権利のないものは決して送らないでください。寄稿は利用前にレビューされます。送付によって著作者としての権利や編集上の権利が生じることはなく、スポンサーシップで調査結果を買うことは決してできません。
手法、データセット、または問いを持ち込んでください。
情報提供と問い合わせは本日から受け付けています。問い合わせには参照番号が付き、次の手順が示されます。申請、支払い、計算資源の割り当て、登録は、担当チーム、規約、審査体制が整ってから開始します。
法的文書。
このサイトの地図、データ、図表は、背景と一般的な情報として示すものです。助言、予報、警報ではありません。情報の限界は免責事項とデータに関する注意事項に記載しています。