In this guide, we provide an overview of how we envision the OPR process to work, with examples from previous submissions. The guide is directed at reviewers, but serves as a general guide for people that may be curious as to how the process runs.
Our driving philosophy/slogan for the OPR process is:
By this, we mean that all communication should, where possible, occur on the submitted manuscript itself. This keeps the paper trail to a minimum and allows everyone involved access to any discussion: authors, reviews, and editors.
LLP uses OPR to increase and improve communication between writers, reviewers and editors. LLP is part of a very small field, and the field has several issues to overcome.
We want writing and editing to be collaborative and constructive, and for the process to connect people and deepen everyone’s expertise and contribution to the future of the field.
We use Google Documents because the tool lets us all:
- Work on a document at the same time
- Highlight text and leave comments (Leave a comment by highlighting some text and then using “Control + Alt + M” or clicking the comment icon that appears to the right of the margin)
- Reply to comments (have discussions around specific text and ideas)
- Tag specific people in comments (to notify people in certain cases). Tag someone using [email protected]
- Work in “suggestion” mode which lets the author edit the document after review, and this “suggestion text” is in a different color, which draws the reviewers to the changes which they can comment on and “approve/resolve.”
If you aren’t that familiar with Google Docs, check out this overview.
An LLP submission typically has these sections:
- The title page (abstract, author information, etc).
- The main text.
- A style guide.
- Author submission information (similar to a cover letter an author might use when submitting to a journal).
- Review forms for reviewers (scores, comments, confidence, general comments)
- Review timeline
As an LLP reviewer, you can leave comments on:
- The title page
- The main text
- Author submission information
As an LLP reviewer, you can leave detailed feedback (general thoughts, specific suggestions) in:
- Review forms for reviewers
We created a flowchart to help visualize how the OPR process unfolds. Please make yourself aware of your responsibilities at each stage.
Link to flowchart
However, in summary, you will mostly be interaction with the submission in the following ways:
- Use comments directly on the manuscript
- Ask questions
- Make suggestions
- Give praise
- Complete a formal review at the end of the manuscript
- Send messages in the LLP Slack
Reviewers can use comments to highlight sections of the manuscript in the following ways.
To ask questions at specific points
To make suggestions
To give praise
At LLP we are committed to creating a supportive community around teaching with games. The OPR process is a perfect place for us to exercise our support for others. If you find a section of the manuscript that stands out, let the author know!
Authors can highlight areas that need fixing during the revision stage.
Discuss feedback with reviewers
Authors can reply to comments, ask questions, request help, etc and continue a discussion on a certain point
Once you have read the manuscript, please complete a formal review at the bottom of the document. There is a specific section titled “Review Forms” for this task.
We have a Slack group for sharing articles and news, discussions around GBLT, as well as informal chat on games, and, of course, off-topic chat. The main objective for using Slack, however, is for reviewers, authors and editors to be in contact with each other regarding the OPR process. A specific channel is created for each submission that is accepted for OPR. Authors, reviewers and editors enter the channel and may use it to:
- Provide updates
- Ask questions
- Engage in discussion around the manuscript
- Let the editors know when you have finished commenting and reviewing the document
- Informal discussion that does not “fit” into a GDoc comment or the formal review
Some examples are provided below: