Skip to content
Colour mode
GRIx home

Nexus Reports

Incident response for publication errors

ReportsThe Global Risks Index (NXS-GRX)Charters
Operations · version 0.1.0

Incident response for publication errors

What to do when a published item contains an error, a rights problem or a harmful disclosure.

Incident response for publication errorsCharters
  1. Version0.1.0
  2. StatusDraft pending owner and counsel review
  3. EffectiveOn adoption by the owner through nexus-governance
  4. Applies toall on all networks
  5. Text hash (sha256)04b957f0342344be…
  6. JurisdictionProposal: laws of Ontario and the federal laws of Canada applicable therein; for counsel review

Reports · the Global Centre for Risk and Innovation (GCRI Canada), publisher of record

01Status

Draft. Not in force.

This document is a draft. It is not legal advice and it is not in force. It becomes required only when the owner adopts it by a recorded decision in nexus-governance. Until then nothing here blocks anyone’s work.

02Operations

What counts

A factual or data error, a wrong figure, a broken or missing licence, third-party material without rights, personal data published in error, an information hazard published by mistake, a wrong author or credit line, or a release that skipped a required gate.

03Operations

Severity

  • S1: harm to a person, personal data exposed, or an information hazard. Act within hours.
  • S2: material error, rights problem, missing gate. Act within 2 days.
  • S3: minor error or typo. Fix in the next version.
04Operations

Steps

1. Report. Anyone writes to the contact form with subject "Publication error". The managing editor logs it and names an incident lead. 2. Contain. For S1 and S2 the incident lead may restrict the item on the network site while it is assessed. Restriction is shown on the page. Zenodo records cannot be deleted; contact the Zenodo community curators through the owner account if restriction is needed there. 3. Assess. What is wrong, since when, who is affected, what the effect on findings is. Check the agreements snapshot and licence manifest for the release. 4. Decide. Correct, express concern, retract, or withdraw. A correction is a new version with a note. Retractions are board decisions. 5. Fix. Build the new version through the normal pipeline and checks. No edits in place. 6. Notify. Authors, affected people, the Privacy Officer for personal data, the Secretariat, and where needed the funder or regulator. Notices follow PIPEDA, Quebec Law 25 and GDPR where they apply. 7. Publish the notice. Add an entry to the corrections log. 8. Review. Within 14 days, write what failed and what changes. Update the checklist or the gate if a rule was missed.

05Operations

Roles

  • Incident lead: managing editor or delegate.
  • Decision: collection editor, with the board for retractions.
  • Technical: hosting lead and the production editor.
  • Legal and privacy: counsel and the Privacy Officer, to be named by the owner.
06Operations

Records

Keep the report, timeline, decision, notices and review. Keep personal data to the minimum. Retain under the privacy notice.

07Operations

Do not

Do not delete evidence. Do not edit a published version. Do not discuss the incident publicly before the notice. Do not blame individuals in public notices.

CC BY 4.0 Free to read. Text and figures: CC BY 4.0. Data: CC0 1.0. Authors keep copyright. Published by GCRI Canada.