跳到主要内容
知仓学习社ZHICANG

joc-rebuttal

Use when revising a Journal of Communication (JoC) manuscript after a revise-and-resubmit. The hard problem at JoC is that communication is a multi-…

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,5 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

R&R Revision & Response (joc-rebuttal)

Communication is not a single-paradigm discipline, and JoC reviewers reflect that: one referee may

reason as a post-positivist media-effects scholar, another as an interpretive or critical/cultural

scholar, another from computational communication. A JoC R&R therefore is less "satisfy everyone" and

more "broker across paradigms without breaking the paper" — and you must do it inside JoC's **hard

~35-page limit** (text, references, tables, figures, and endnotes all count). This skill is about that

brokering and the page budget, not about inventing data.

When to trigger

  • A JoC R&R arrived and you are scoping the revision before touching the manuscript
  • Two reviewers want changes that come from different epistemologies and partly conflict
  • Required additions threaten to push the paper over the 35-page cap
  • You are writing the cover memo to the Editor-in-Chief

Step 1 — Map the reviewers by paradigm before you write anything

For each reviewer, label the stance their comments come from (post-positivist / interpretive /

critical / computational / mixed) and what "convincing" means to them — more controls and robustness,

richer interpretive warrant, sharper theoretical/critical stakes, or stronger validation and code.

A demand that looks unreasonable usually makes sense once you name the paradigm behind it. The

Editor-in-Chief's letter tells you which demands are load-bearing vs. optional.

Step 2 — Decide each comment with the page budget in view

Every comment resolves to one of four moves, and three of them cost pages:

| Move | When | Page-budget effect |

|------|------|--------------------|

| Do in main text | load-bearing; the editor flagged it | costs pages — find offsets |

| Do in supplement | adds rigor but not the core argument | frees main-text pages (DAS/Appendix) |

| Reframe, don't add | the concern is about framing, not missing analysis | cheap; often the best move |

| Decline, with a reason | the request breaks the paper or comes from a paradigm the paper isn't written in | costs nothing; must be argued, not dodged |

When you add, say what you cut or moved to stay under 35 pages — reviewers and the editor see the

tradeoff and trust it more than a paper that silently bloats.

Step 3 — Broker the cross-paradigm conflicts in the open

When a quantitative reviewer and an interpretive/critical reviewer pull opposite ways, do not

quietly side with one. State the tension, choose a principled path that keeps the paper coherent in

its own paradigm, and explain to the editor why that path serves the contribution. A paper that

tries to be all paradigms at once usually loses its argument; defend what the study is.

Step 4 — Keep the revision submittable

  • Double-anonymous integrity: the revised main document and supplements stay de-identified;

keep self-citations in the third person.

  • Transparency: update the Data Availability Statement and any Open Science Badge claims so

new analyses, data, or materials are covered (see joc-open-science-and-transparency).

  • Format: still APA 7th, .docx, within ~35 pages; the JoC Forum reply path is for shorter

exchanges, not full R&Rs.

Response memo structure (per reviewer, then a global note)

Lead with a short note to the editor: the 2–3 changes that matter most, and how you kept the paper

under the page cap. Then, per reviewer, a compact entry:

R# (paradigm: post-positivist / interpretive / critical / computational)
• Comment → [paraphrase]
  Action: did-in-text / did-in-supplement / reframed / declined(reason)
  Where: §/p./Table/Fig./Supplement S#   |  Pages: +/- vs. prior draft

Anti-patterns

  • Treating a different-paradigm comment as "wrong" instead of naming the stance and answering it on its terms
  • Quietly satisfying one reviewer while ignoring a conflicting one
  • Adding analyses until the paper busts the 35-page cap, with no statement of what moved
  • Letting the Data Availability Statement / badges fall out of sync with the new analyses
  • Re-identifying the authors in the revised file or supplements (breaks double-anonymity)
  • Diluting the paper's own paradigm to look agreeable to every reviewer

Output format

【Reviewer paradigm map】R1/R2/R3 → stance + what "convincing" means to each
【Editor's load-bearing points】listed and solved first?
【Per-comment moves】in-text / supplement / reframe / decline — each with location
【Page budget】revised length ≤ ~35 pp; what was cut or moved to supplement
【Cross-paradigm conflicts】brokered in the open, paper's paradigm protected? [Y/N]
【Anonymity + DAS/badges】third-person self-cites + transparency updated? [Y/N]
【Next】resubmit via Manuscript Central

Supplementary resources

  • [../../resources/official-source-map.md](../../resources/official-source-map.md) — review model, referee recommendations, page limit, and transparency policy

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。