Editing CommunityData:Automating and Streamlining Walkthrough (section)

==== Revise and Resubmit ====
Revise and resubmit makes papers better but can be a time crunch and if you have co-authors, it can get hard to tell what's been done or what certain revisions were trying to accomplish. When you get reviews back that ask you to make changes, you can save yourself a lot of annoyance if you follow this four-part method:

# Keep a copy of your original submission, including the main.tex file (if you are using .Rtex file because you followed the above advice about automation....please note that the main.tex file is hidden in Overleaf -- click the little 'document' icon next to 'Recompile' (mouseover has a tooltip that says 'Logs and output files' -- then 'Other logs and files' at the bottom right -- note that the output.bbl file is there too, that's also useful because you'll want it for your upload to arXiv if you post a preprint). You will need this for the LaTeX Diff below. This is the first stage of responding to a review---but it's one you can do even before the reviews are back.
# Paste all reviews into a Google Sheet---[https://docs.google.com/spreadsheets/d/1ZMMKI3HQ6bOTRT0oF5ohBtVLqo3ye65J5WJ-rn6WxsM/edit?usp=sharing feel free to use this as a template]. This is useful for the second stage of responding to a review, when maybe you're working through some emotional responses, trying to figure out what to do, etc.
# Paste all reviews into a response to reviewers letter document in the same Overleaf project where you wrote the paper. Place them below the '''\end{document}''' line so they won't show up. This is useful for the third stage of responding to a review---actually revising. As you revise to address the issue, move the comment up into the letter, quote it and then write what you did. Mark and comment the bit of your paper you copy-pasted (something like: ''populate any edits made into reviewer response''). It might feel a skosh redundant with the Google Sheet, and it is ... think of it as double-entry bookkeeping to make sure nothing gets dropped.
# Show your work: some venues require (and reviewers often appreciate) a document that shows what was changed. If you use Word, that means turning on Track Changes. If you use LaTeX, [[CommunityData:LaTex Diff | latexdiff is a way to achieve this]]. Latexdiff is available on [[CommunityData:Kibo]]. Making sure you have a nice clean diff and letter is the final stage of responding to a review.

Please note that the '''cdsc_example''' repository contains examples of past revision processes.