Corrections, Revisions and Withdrawal Policy

This policy explains how errors are reported and reviewed, the difference among minor correction, material correction, revision, reissue, and withdrawal, and how versions, records, and notifications are managed.

Users may report an incorrect figure, inconsistency, translation problem, broken link, privacy concern, or misleading use. The report should identify the page or file, table or location, and supporting evidence or explanation.

Report a published error

1. Register the report and confirm receipt where contact details exist.
2. Identify material, version, and related files.
3. Assess immediate risk or personal-data exposure.
4. Review source, code, tables, and records.
5. Classify the error, effect, and scope.
6. Decide and escalate where necessary.

A nonmaterial error may be corrected directly, with the page-update date changed where appropriate. Not every punctuation change requires a public notice, although operationally relevant changes remain recorded.

• Publish a notice explaining what changed and why.
• Update every affected format and language.
• Change version number or update date.
• Preserve the earlier version or state that it was superseded.
• Assess effects on summaries, media material, and datasets.
• Notify known clients or users where the effect is significant.

A revision is used where data, methodology, analysis, or interpretation change substantially. The new version has a number, date, and change log and explains whether earlier findings remain wholly or partly valid.

Material may be withdrawn where error or failure prevents reliance, personal information was exposed, publication rights were absent, manipulation or plagiarism is established, or publication creates unacceptable risk. A withdrawal notice and reference may remain rather than deleting every trace.

• Material title and date.
• Withdrawal date.
• Clear general reason where lawful and safe.
• Replacement material, where available.
• Instruction not to rely on the withdrawn item.

• Release a new data and codebook version.
• Identify affected variables, records, or weights.
• Update file hash or identifier.
• Inform restricted users where possible.
• Explain whether analysis should be repeated.
• Do not silently replace the file.

Review whether the issue affects Arabic, English, PDF, HTML, tables, charts, or data. Correcting one format does not establish that every format was corrected.

• Editor or researcher registers the issue.
• Analyst verifies data and code.
• Study lead assesses scientific effect.
• Privacy lead reviews exposure incidents.
• Authorized person approves correction or withdrawal.
• Technical team updates links, files, and indexing.

Honest error reporting is not treated as misconduct or personal failure. Concern for reputation must not prevent staff or users from raising a genuine problem.

A page may show publication date, latest update, version, and correction or withdrawal notice. The Center maintains a more detailed internal record of decisions, reasons, approvals, and affected files.