Skip to content

Separate publishing from other communication (Ch8, #21)#36

Open
LukasWallrich wants to merge 2 commits into
mainfrom
content/issue-21-publishing-communication
Open

Separate publishing from other communication (Ch8, #21)#36
LukasWallrich wants to merge 2 commits into
mainfrom
content/issue-21-publishing-communication

Conversation

@LukasWallrich

Copy link
Copy Markdown
Contributor

Addresses the two R1 points in #21.

What changed (only publishing.qmd)

  1. Separated traditional journal publishing from other communication channels. Added a framing paragraph after the intro that distinguishes (a) making a replication visible and citable through channels that require no journal (FORRT Replication Database, PubPeer, preprints) from (b) formally publishing in a peer-reviewed journal. The journal-specific material (pottery-barn rule, journals rejecting replications for lack of novelty, dedicated replication journals, discontinued journals, PCI peer review) is now collected into its own paragraph after the reporting-options table, leading into the dedicated-journals table.

  2. Made explicit that the two are not mutually exclusive. The framing paragraph states that researchers can make findings public without a traditional journal, pursue journal publication, or do both, and that posting a preprint and submitting to a journal are complementary rather than competing choices.

Both existing tables (reporting options and dedicated replication journals) are kept intact; no new citations, journals, or facts were introduced. Renders cleanly with no broken citations.

Out of scope

The Ch8 -> Ch5/6 structural move (relocating/splitting this chapter) is not done here; that is deferred to #27.

Addresses the two R1 points in #21: (1) reframe the chapter so traditional peer-reviewed journal publishing is discussed separately from other ways of communicating results (FORRT Replication Database, PubPeer, preprints, PCIs), and (2) state explicitly that communicating and formally publishing are not mutually exclusive, so researchers can do either or both. All content stays in publishing.qmd and both tables are kept intact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant