You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
5The note to the editor saying that you've already seen this paper in the review process should happen before agreeing to do the review.Scott Seidman– Scott Seidman2025-01-14 15:53:26 +00:00Commented Jan 14, 2025 at 15:53
-
19@ScottSeidman: In my mind, it is not necessary. As an editor, it would not affect my decision on assigning a refereeing job (besides being happy that somebody will not spend eternity "refereeing" a paper only to decline the job in the end or stopping communications altogether).Moishe Kohan– Moishe Kohan2025-01-14 16:00:33 +00:00Commented Jan 14, 2025 at 16:00
-
3@ScottSeidman The editor is free to ignore the review for whatever reason or weight it more or less. In other words, there's no "forever hold your peace" in review, like a regulated study.user71659– user716592025-01-14 21:55:59 +00:00Commented Jan 14, 2025 at 21:55
-
4I'd argue you should start the author comments by saying that you previously reviewed the paper. Then you directly reference your previous points and discuss how they were or were not addressed. That gives direct feedback to the editor on the quality of the paper. It's much more useful than "I read it again and it's fine."user71659– user716592025-01-14 22:00:02 +00:00Commented Jan 14, 2025 at 22:00
-
8@ScottSeidman: As an editor (and I have served as a managing editor for three journals) I would not care one way or another.Moishe Kohan– Moishe Kohan2025-01-14 23:01:32 +00:00Commented Jan 14, 2025 at 23:01
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
Use tags that describe what your question is about, not what it merely relates to. For example almost every question on this site is eventually related to research, but only questions about performing research should be tagged research.
Use tags describing circumstances only if those circumstances are essential to your question. For example, if you have a question about citations that came up during writing a thesis but might as well have arisen during writing a paper, do not tag it with thesis.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. graduate-admissions), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you