Brief overview of the review process
Before sending manuscripts for review, a lead editor of the relevant LiveCoMS section will have responded favorably to a presubmission inquiry and then checked that the submitted manuscript indeed conforms to what was originally proposed. A LiveCoMS editor will also have checked that the manuscript appears to be reasonably well edited and ready for review. Given this preparation, LiveCoMS asks that reviewers respond promptly to review requests and take immediate action on reviewing manuscripts; typically we ask that reviews be returned within 15 days.
The review process is in general similar to typical journals, in that we seek to ensure manuscripts are of high quality and will provide significant benefits to the field. However, we do also have specific review criteria and we ask reviewers to make sure they are aware of these, including category-specific review criteria relevant to the particular category of article. Look in each section for the bullet pointed list of review criteria to consider, and respond to each of the relevant points specifically.
We also have a Conflicts of Interest policy and you as a reviewer should make sure they are familiar with these policies, and decline to review if they have a conflict. If you are uncertain about a conflict, they should disclose any such potential conflicts to the editor managing the review process.
One unique aspect of the LiveCoMS review process is the opportunity to engage with authors publicly rather than anonymously if you so desire. Specifically, if you (as a reviewer) are interested in participating public discussion of the work and helping to improve it, you are free to comment on the issue tracker connected to the GitHub repository associated with the article, which can be a way to work together with the community to help authors improve their article. If you choose to do this, you should cross-reference GitHub comments in your review for LiveCoMS in an unambiguous way so the author knows exactly what needs to be addressed. If you wish to remain completely anonymous, we suggest refraining from leaving GitHub comments near the time of your review, as the author will likely be able to guess your identity from the comments.
Authors are also encouraged to have other researchers review their content, with comments and responses handled via the article’s GitHub issue tracker. A history of revisions in response to community concerns will impact the review process favorably.
Reviewers will assess whether articles are well edited and clearly written. Authors whose article uses inconsistent style or poor grammar, or is poorly edited, will be asked to revise and address these issues.
The reviewer form asks the following questions:
Overall Rating Reviewer will rank from 1-5 stars.
For this manuscript I recommend… Reviewer will choose between “Accept”, “Revise and resubmit”, and “Reject”
The reviewer will then answer the following open response questions. For these responses, the reviewer may also copy the questions to a separate document, respond to them there, and attach the responses.
What is the level of significance of this work and its suitability for the journal? Is it likely to have a strong positive impact on the targeted set of readers? If this is a revision, what is the significance of the updated material?
To what extent does the article engage with current understanding in the scholarly community? If this is a revision, to what extent do the authors engage with the community participating on their GitHub version?
In what ways should the paper be improved to be easy to read, free from grammatical errors, have a professional presentation, and meet the article formatting guidelines laid out in the author policies?
How does the article address the specific reviewer criteria for each article type? These criteria are listed in the sections for author policies for Best Practices, Perpetual Reviews, Tutorials, Software Analyses, and Lessons Learned.
What other comments do you have for the author?
What other comments do you have for the editor? (The response to this question will not be seen by the authors)