Skip to content

Instantly share code, notes, and snippets.

@K-Felk
Last active October 12, 2018 19:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save K-Felk/2a7787109f3cc336182af2751321a303 to your computer and use it in GitHub Desktop.
Save K-Felk/2a7787109f3cc336182af2751321a303 to your computer and use it in GitHub Desktop.

Scholarly Submissions Editor, Weave

To apply for this position

Send an email with your CV, a letter of interest, and an academic writing sample (in word or PDF format) attached to felkerk@gvsu.edu.

Timeline

Applications are due by November 5th 2018, with interviews hopefully scheduled the week of the 12th, and a new editor selected by end of November/beginning of December.

Overview

The scholarly submissions editor manages the process of receiving, reviewing, accepting, and editing peer-reviewed submissions for Weave, the Journal of Library User Experience. The editor spends anywhere from 10-20 hours a month on publishing-related tasks. Like all positions at Weave, editors are volunteers and can work remotely from anywhere in the world.

Qualifications

  • An interest in and dedication to improving user experience within libraries
  • A commitment to open access and sustainable models of open scholarship
  • Previous experience participating in and/or managing scholarly peer review processes
  • A very high degree of demonstrated writing proficiency
  • Previous experience with scholarly publishing, either as an author or an editor
  • Creativity, ingenuity, and a knack for problem solving

Responsibilities

General responsibilities

  • Attending monthly virtual meetings with the rest of the Weave team
  • Participating in communication between meetings (e.g. Slack, Google Drive, email)
  • As needed, serving on search teams for new editors
  • As needed, voting for board member appointments

Oversight of peer-reviewed submissions

  • Works directly with the other editors and the board to shape upcoming issues and help set editorial direction
  • Keeps other editors (and editorial board) updated on the status of current scholarly submissions overall and the status of individual pieces as they move through the process
  • Develops and refines editorial style guide and requirements for pieces, in consultation with other editors

Working directly with authors

  • Reads and responds to incoming pitches for scholarly pieces, makes the initial decision on whether a pitch merits a draft or not, communicates decisions (and rationale) to pitch submitters. When required, also helps to determine if a pitch should result in a peer review or Dialog Box piece.
  • Reviews drafts, determines whether submissions should be rejected outright; require some pre-review editing; or pass directly on to peer reviewers.
  • Works directly with authors in a mentoring role when requested or required, reading and responding to outlines, partial drafts, samples, or complete drafts.
  • Communicates with authors about the status of their piece as it moves through the peer review, editing, and publication process.

Working with reviewers

  • Manages, recruits, and trains, and manages a network of peer reviewers, and creates and updates documentation on the peer review process to assist in training.
  • Weave uses a double-blind peer review process, which requires two reviewers for each scholarly piece. At our current rate of submissions, that requires a network of approximately 10-15 people.
  • Consolidates, communicates, and finalizes peer-review feedback, including the decision to accept or reject, often in concert with the other editors
  • Assigns articles to peer reviewers based on qualifications and background. This includes making sure the article has had identifying information removed beforehand, and ensuring the double-blind process isn’t compromised (and reassigning pieces when the process is compromised), as well as ensuring the review is completed on time.
  • Handles most of the post-review editing of accepted scholarly pieces for content, clarity, organization, and tone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment