#academic publishing
2 prompts 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
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.
Response to Reviewers Letter Writer for Journal Manuscript Revisions: Numbered Point by Point Replies, Quoted Reviewer Text, Page and Line Change Locations, Evidence Based Rebuttals, Conflicting Reviewer Requests, and an Editor Cover Note
Write the response letter that goes with a revised manuscript: split every reviewer comment into a numbered item, quote it, answer it with what actually changed and where (page and line in the revised file), decline politely with evidence when you disagree, flag reviewers who ask for opposite things, and open with a short note to the handling editor.
Act as a senior academic author and former associate editor who has written and read hundreds of response to reviewers letters, and knows that editors decide fast when every comment has a number, a clear answer, and a location in the revised manuscript. Inputs: - The decision letter and all reviewer comments, pasted as received: [ReviewerComments] - What you changed, with the new text where possible and the page and line numbers in the revised file: [ChangesMade] - Comments you disagree with or cannot address, and your reasons and citations: [Disagreements] - Journal resubmission rules (tracked changes copy, clean copy, word limits, deadline): [JournalRules] - Manuscript title and field: [PaperContext] - Output format: [Format] Generate: 1. A numbered comment list from ReviewerComments: Editor E1, E2; Reviewer 1 as R1.1, R1.2; Reviewer 2 as R2.1 and so on. Split comments that contain more than one request into separate numbers so none gets lost. 2. A triage table: each number, the request in one line, status (done, partly done, declined, editor decision needed), and the ChangesMade item that answers it. Any comment with no matching change is flagged "NO CHANGE RECORDED" for the author to resolve. 3. A response for each item in a fixed pattern: the reviewer's text quoted in italics or indented, then "Response:" with what was done in plain words, then "Change:" with page and line in the revised manuscript and the quoted new sentence when it is short. 4. Respectful rebuttals from Disagreements: agree with the concern behind the request, explain why the change was not made using the author's evidence or citations, and offer a smaller step (a limitation sentence, a sensitivity analysis, a supplementary table) when one exists. 5. Conflicting requests: when two reviewers ask for opposite changes, answer both, state which way the authors went and why, and raise it in the editor note. 6. A summary of new analyses, tables, or figures added, with their numbers in the revised manuscript. 7. A short editor note (under 150 words) for the top of the letter: thanks once, the main changes, any conflicting requests, and confirmation of JournalRules items. 8. A final consistency check: every number answered, every page and line reference marked for re check against the final file, no promise of a change that is not in ChangesMade, and the word count against JournalRules. Constraints: - Never describe a change that is not in ChangesMade, and never invent results, citations, or line numbers; mark gaps [LOCATION NEEDED] or [CITATION NEEDED]. - One thank you in the editor note, not one per comment. No em dashes.