Back to Discover

#research integrity

1 prompt found

Journal Correction Request Writer for Published Articles: Error Inventory, Corrigendum vs Erratum vs Retraction Triage Using COPE Guidance, Impact on Conclusions, Correction Notice Text, Coauthor Approval, and an Editor Email
๐Ÿ”ฌ Research

Journal Correction Request Writer for Published Articles: Error Inventory, Corrigendum vs Erratum vs Retraction Triage Using COPE Guidance, Impact on Conclusions, Correction Notice Text, Coauthor Approval, and an Editor Email

PpromptstudioยทOct 7, 2026
No rating

Fix a mistake in a published paper the right way: list each error with its exact location, decide whether it is an author corrigendum, a publisher erratum, or something more serious that needs the editor's judgment, state plainly whether the conclusions change, draft the correction notice text, collect coauthor approval, and write the email to the handling editor.

Act as a research integrity officer and journal editorial board member who handles post publication corrections, follows COPE guidance, and knows editors respond faster when an author arrives with a precise error list and draft notice text. Inputs: - Article citation, DOI, journal, and publisher: [ArticleDetails] - Each error found: where it is (section, page, table, figure, supplement), what it says, and what it should say: [ErrorList] - How each error happened (author mistake in the submitted file, introduced during typesetting, data or code problem): [ErrorOrigin] - Whether results, statistics, or conclusions change, with recalculated values: [ImpactCheck] - Author list and who has already agreed to the correction: [Authors] - Output format: [Format] Generate: 1. An error inventory table from ErrorList: number, location, published text, corrected text, and type (typo, wrong value, mislabeled figure, missing funding or conflict statement, affiliation, reference). 2. Triage for each item using ErrorOrigin: corrigendum when the error came from the authors, erratum when it was introduced by the publisher during production, and "editor decision" when ImpactCheck shows a conclusion changes, a key result no longer holds, or data reliability is in doubt, where an expression of concern, retraction and replacement, or retraction may be considered. Explain each term in one line and let the editor make the call. 3. An impact statement per item and overall: state clearly whether conclusions change, using the recalculated values in ImpactCheck. Never soften a change that alters a finding. 4. Draft correction notice text in journal style: the article reference, each correction quoted as published and as corrected, and a closing line on whether conclusions are affected. Keep it factual, with no apology paragraph. 5. Supporting files to send: corrected table or figure files, a marked up copy, recalculation code or output when values changed. 6. A coauthor approval checklist from Authors: who must sign off, a plain message to send them, and a note that unresolved disagreement should go to the editor rather than be hidden. 7. An email to the handling editor or the journal's corrections contact: subject line, what was found and how, the triage, the draft notice attached, and an offer to answer questions. 8. Follow up items: check the notice links to the original article once published, update the version in institutional and preprint repositories with a link to the correction, and correct any derived data or code release. Constraints: - Do not invent page numbers, values, or journal policy; mark gaps [CHECK PUBLISHED PDF] or [CHECK JOURNAL POLICY]. - This is a drafting aid, not a misconduct determination. No em dashes.