GCRI · Registry
Koreksi dan pembuatan versi
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.
Bagaimana pekerjaan berjalan.
Interoperability console
Correction and versioning · Crosswalk · Profile v3
Field mappings
| identifier | id | copy | Lintasan |
| evidence_label | quality.label | enum map | Lintasan |
| licence | rights.licence | SPDX id | Ambiguous |
| version | version | semver | Lintasan |
Kesesuaian
Gbr.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.
Model, asumsi, data, dan ketidakpastiannya, dalam bentuk yang akan diperiksa ilmuwan atau insinyur. Strukturnya mengikuti metode yang dipublikasikan. Nilai yang digambar bersifat ilustratif, bukan temuan.
Set data dan asal-usul
The data classes behind correction and versioning and what is recorded about each before it is used.
| Kelas data | Asal-usul tercatat | Resolusi dinyatakan | Lisensi diperiksa |
|---|---|---|---|
| Citra satelit, optik dan radar | sensor, tingkat pemrosesan, tanggal akuisisi | ukuran piksel dan kunjungan ulang | per adegan |
| Reanalisis dan keluaran model iklim | model, eksperimen, anggota, versi | grid dan langkah waktu | per rilis |
| Sensor dan alat ukur in situ | stasiun, instrumen, catatan kalibrasi | titik dan laju pengambilan sampel | per jaringan |
| Keterpaparan penduduk dan aset | metode, tahun terbit, sumber masukan | ukuran sel dan satuan | per rilis |
| Batas dan geografi acuan | produsen, edisi, tanggal | skala | per edisi |
- Garis keturunan
- Catatan W3C PROV dari sumber hingga gambar
- Prinsip
- FAIR: dapat ditemukan, dapat diakses, interoperabel, dapat digunakan ulang
- Kesenjangan
- ditampilkan sebagai hilang, tidak pernah diisi diam-diam
Corrections in one domain must reach every product that used the data.
- AirDalam praktikA revised rainfall series changes drought indices.What a reader can checkProducts re-run after revision
- KesehatanDalam praktikRevised case counts change outbreak analyses.What a reader can checkRiwayat versi
- PanganDalam praktikRevised survey weights change estimates.What a reader can checkCorrection notes
Corrections are published with every edition of Laporan 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.
Apa yang diukur, dan seberapa baik.
Setiap indikator membawa satuan, frekuensi, jenis sumber di baliknya, dan label bukti yang akan dibawa suatu nilai. Tidak ada nilai yang ditampilkan: sebuah program menyediakannya berdasarkan wewenangnya sendiri.
| Indikator | Unit | Kadensi | Jenis sumber | Label |
|---|---|---|---|---|
| Corrections issued | count by type per period | setiap bulan | Correction trail | TERAMATI |
| Time from report to correction notice | hari | per case | Case records | TERAMATI |
| Content changes without a version increment | jumlah | setiap minggu | Content hash comparison | TERAMATI |
| Version chain completeness | share of versions linked to a predecessor | setiap bulan | Relation metadata | TERAMATI |
| Retracted items linked to their notice | share of retracted items | setiap bulan | Crossmark and retraction records | TERAMATI |
| Superseded records still cited as current | count of citing works | setiap kuartal | Citation graph | ESTIMASI |
| Corrections reflected by downstream aggregators | share of sampled aggregators | setiap kuartal | Aggregator sampling | ESTIMASI |
Asal bukti.
Set data publik bernama dan catatan kelembagaan, masing-masing dengan kelas lisensinya. Sumber berdasarkan perjanjian hanya digunakan sesuai ketentuannya dan tidak pernah diterbitkan ulang.
| Sumber | Apa yang diberikannya | Kelas lisensi |
|---|---|---|
| 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 |
Siapa yang memutuskan, dan apa yang dilayani bukti.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Siapa yang memutuskan | Pertanyaannya | Bukti yang dilayani halaman ini |
|---|---|---|
| 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 |
Keluaran yang dihasilkan topik ini
- 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 sistem 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
Batasan
No registry can recall copies it does not control. Notices help only sistem 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.
Cara hal ini dikaji, dan apa yang tidak dapat dinyatakan metodenya.
- 01Rekayasa data, interoperabilitas, dan pengelolaan dataPenyerapan data tervalidasi skema · Rekonsiliasi pengenal persisten · Perekaman silsilah dalam alur pemrosesanDiterapkan di sini
- 02Keamanan siber dan kriptografiRiwayat catatan yang menunjukkan perubahan · Ekspor dan rilis yang ditandatangani · Pemodelan ancaman pada jalur penyuntinganDiterapkan di sini
- 03Identitas digital dan sistem digital publikAutentikasi dan kewenangan penerbit · Disambiguasi kontributor oleh yang bersangkutanDiterapkan di sini
Where this page’s references lead.
Badan dan dokumen yang menjadi acuan halaman ini. Status dan edisi berubah; setiap tautan menuju badan penerbitnya.
Tanya jawab.
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?
Kontribusikan bukti dari halaman ini.
Laporan 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.
- SurelGerbang GW-GCRIKirim dari halaman iniBukti, koreksi, kasus, metode, tinjauan, terjemahan, atau masukan profil. Kiriman tiba dengan label halaman ini, sehingga editor pemiliknya menerimanya.
- ZenodoDeposit terbukaDeposit dan ajukan ke komunitasTerbitkan catatan Anda sendiri di Zenodo dengan ORCID iD Anda, lalu ajukan ke komunitas Reports di sana. Kurator meninjaunya; DOI tetap milik Anda.
- LaporanGCRILihat semua cara berkontribusiJenis kontribusi, cara masing-masing ditinjau, kredit yang Anda terima, lisensinya, dan apa yang tidak pernah diterima.
Jangan pernah mengirim data pribadi, rincian infrastruktur sensitif, atau apa pun yang tidak berhak Anda bagikan. Kontribusi ditinjau sebelum digunakan. Mengirimkannya tidak memberikan hak kepenulisan atau editorial, dan sponsor tidak pernah membeli sebuah temuan.
Bawa metode, dataset, atau pertanyaan.
Informasi dan pertanyaan sudah terbuka hari ini. Sebuah pertanyaan menerima nomor referensi dan menyebutkan langkah berikutnya; lamaran, pembayaran, alokasi komputasi, dan pendaftaran hanya dibuka ketika tim, ketentuan, dan kapasitas tinjauannya tersedia.
Dokumen hukum.
Peta, data, dan gambar di situs ini ditampilkan untuk konteks dan informasi umum. Semua itu bukan nasihat, prakiraan, atau peringatan; batasan informasinya dijelaskan dalam Penafian dan Pemberitahuan Data.