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.
- آبIn practiceA revised rainfall series changes drought indices.What a reader can checkProducts re-run after revision
- سلامتIn practiceRevised case counts change outbreak analyses.What a reader can checkتاریخچهٔ نسخهها
- غذاIn practiceRevised survey weights change estimates.What a reader can checkCorrection notes
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.
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | برچسب |
|---|---|---|---|---|
| Corrections issued | count by type per period | monthly | Correction trail | مشاهده‌شده |
| Time from report to correction notice | روز | per case | Case records | مشاهده‌شده |
| Content changes without a version increment | count | weekly | Content hash comparison | مشاهده‌شده |
| Version chain completeness | share of versions linked to a predecessor | monthly | Relation metadata | مشاهده‌شده |
| Retracted items linked to their notice | share of retracted items | monthly | Crossmark and retraction records | مشاهده‌شده |
| Superseded records still cited as current | count of citing works | quarterly | Citation graph | برآوردشده |
| Corrections reflected by downstream aggregators | share of sampled aggregators | quarterly | Aggregator sampling | برآوردشده |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| منبع | What it gives | Licence class |
|---|---|---|
| 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 |
Who decides, and what the evidence serves.
Registry prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| چه کسی تصمیم می‌گیرد | The question | Evidence this page serves |
|---|---|---|
| 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 |
Outputs this topic produces
- 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.
How it is studied, and what the methods cannot say.
- 01مهندسی داده، هم‌کنشی‌پذیری و تولیتSchema-validated ingestion · Persistent identifier reconciliation · Lineage capture in pipelinesApplied here
- 02امنیت سایبری و رمزنگاریTamper-evident record history · Signed exports and releases · Threat modelling of edit pathsApplied here
- 03هویت دیجیتال و نظام‌های دیجیتال عمومیIssuer authentication and authority · Contributor disambiguation by the personApplied here
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 خود در Zenodo منتشر کنید و سپس آن را در همانجا به جامعهٔ Reports ارسال کنید. گزینشگران آن را داوری می‌کنند؛ DOI از آنِ شما میماند.
- گزارش‌هاGCRIهمهٔ راههای مشارکت را ببینیدانواع مشارکت، نحوهٔ بررسی هر یک، اعتباری که دریافت میکنید، مجوز و آنچه هرگز پذیرفته نمی‌شود.
هرگز داده شخصی، جزئیات حساس زیرساخت یا چیزی را که حق اشتراکش را ندارید نفرستید. هر مشارکت پیش از استفاده داوری می‌شود؛ ارسال آن حق مؤلفی یا ویرایشی نمی‌دهد و حمایت مالی هرگز یافته‌ای را نمی‌خرد.
یک روش، یک مجموعه‌داده یا یک پرسش بیاورید.
اطلاعات و درخواست‌ها امروز باز است. هر درخواست یک شمارهٔ پیگیری می‌گیرد و گام بعدی را مشخص می‌کند؛ درخواست‌های عضویت، پرداخت‌ها، تخصیص رایانش و ثبت‌نام‌ها تنها زمانی باز می‌شوند که تیم، شرایط و ظرفیت داوری آن‌ها فراهم باشد.
اسناد حقوقی.
نقشه‌ها، داده‌ها و ارقام این سایت برای زمینه و اطلاعات عمومی نشان داده می‌شوند. توصیه، پیش‌بینی یا هشدار نیستند؛ حدود این اطلاعات در سلب مسئولیت‌ها و اعلامیه‌های داده بیان شده است.