Western University's Free Appropriate Sustainability Technology (FAST) Research Group Paper Writing Protocol[edit | edit source]

How to write a paper and get it published
How to use Zotero in the FAST lab

  1. First do a detailed literature review of your topic – this is the foundation – it must be complete so that you can be sure that you are contributing to the field – see How to do a Lit search
  2. After literature review choose an experiment and/or theory development/analysis which will contribute to the field and do it with Dr. Pearce's help.
  3. When experiment/theoretical work is complete and you have results worth sharing begin to write the paper - Do not use docx or xlsm formatting. Use Libre Office to avoid any problems with journal formatting as Libre Office can save in any format. Do not start your paper in Microsoft Word. Save it as an odt or doc.
  4. Choose a high impact journal that best fits your topic and the magnitude of your contribution to the field in collaboration with Dr. Pearce. How to do that FAST journal selection
  5. Make outline (follow File:FAST-outline.odt)-- approximately 1 page long that includes what you think the major figures will be and a link to your chosen journal.
  6. Dr. Pearce details the outline, put it into partial journal format, and highlight notes. Highlights stay until final draft. The red-notes are about the journal, and yellow -notes to each other/selves (ex. Abstract length, etc). Dr. Pearce will also add the groups past work that you should reference – will be highlighted in grey. Any text (every sentence) taken from previous writing must be edited to avoid self plagiarism and must be cited. Always acquire the original sources, read them and cite them – do NOT cite secondary sources.
  7. Write as complete a paper as possible by filling in outline. Leave outline text – highlighted yellow for removal. Use parenthetical notation for references even if your journal calls for numbers. (Further explanation here). These can be replaced later. Do not use hyperlinking within document since IEEE can not handle it yet – along with many other publishers. Do not link figures or tables either – use Table # instead and will fill in at end. Highlight refs if the journal does not use parenthetical documentation and fig/table numbers. Insert a footer and put the page number field in it. Before sending article ensure that every sentence is supported by one of the three methods below:
    1. Supported by the best peer-reviewed literature available (sometime government documents or other sources are acceptable – but generally it must be in an academic peer-reviewed journal).
    2. Supported by your own work – whether it be your experiment or analysis. Make the method you used to arrive at conclusions from your work transparent.
    3. Supported by logic and previous statements in the article.
  8. Dr. Pearce will review with Changes recorded and send back to you.
  9. Read through the new version with Changes visible. Accept all changes unless there is a problem. Turn on record Changes for any work you do. IF you make large changes (e.g. write a new section) also highlight them. If you disagree with a change – dpn't accept it but explain in a comment bracket. Address ALL of these comments before sending back to Dr. Pearce. Any edits you make to the article must have Track Changes on – unless they are formatting changes such as in a Table. NAME AS NEW VERSION EVERY TIME SOMEONE NEW EDITS IT with version number and your initials (e.g. nane-v2jmp.odt). For multi-party groups, when it is bouncing back and forth between fellow students, CONTINUE TO FOLLOW THESE RULES – two students act as one unit. Never have more than one person editing the same document as authors at the same time.
  10. Repeat previous step until all co-authors are happy with article.
  11. Internal and friendly reviews. Have non-co-authors closest to the particular field of the paper review it. Ask them to shred it and find mistakes. Sometimes it is best to have different people attack specific things within your paper (e.g. logic, a particular type of analysis, etc.). Ask them not to use track changes – but instead use the comment feature. You can send your paper to several friendly reviewers simultaneously.
  12. All useful comments from internal reviewers will be taken into original document WITH CHANGES RECORDED. Update tables, figures, references.
  13. Re-read requirements for journal and make sure we comply on all counts. Ex. Word counts, keywords, etc. Then run through grammar/spell check/plagiarism check using your word processor or web service. Send to Dr. Pearce for final read and approval.
  14. Make a graphical abstract see:
  1. After approved – prepare article for submission. Following technical directions is key! Print out requirements and go through and check off each one to ensure compliance. Format of both text, tables and figures (See: How to make a figure to publish) must be exactly as requested by the journal. Make sure enough dpi, etc. Put references in final formatting if required. When possible use eps for SEO optimization. Make sure you have all the parts - e.g. now Elsevier journals are requesting a 'highlights' document with 5 bullets <85 characters long.
  2. Dr. Pearce writes cover letter and sends everything to journal.
  3. Get published and become a high-caliber academic, go on to save the world....
  4. Is it newsworthy? Have Dr. Pearce contact Debora Van Brenk & Jeffrey Renaud, https://www.sciline.org/scientist-tip-line

Credit[edit | edit source]

Conceptualization: Ideas; formulation or evolution of overarching research goals and aims Methodology: Development or design of methodology; creation of models Software : Programming, software development; designing computer programs; implementation of the computer code and supporting algorithms; testing of existing code components Validation: Verification, whether as a part of the activity or separate, of the overall replication/ reproducibility of results/experiments and other research outputs Formal analysis: Application of statistical, mathematical, computational, or other formal techniques to analyze or synthesize study data Investigation: Conducting a research and investigation process, specifically performing the experiments, or data/evidence collection Resources: Provision of study materials, reagents, materials, patients, laboratory samples, animals, instrumentation, computing resources, or other analysis tools Data Curation: Management activities to annotate (produce metadata), scrub data and maintain research data (including software code, where it is necessary for interpreting the data itself) for initial use and later reuse Writing - Original Draft: Preparation, creation and/or presentation of the published work, specifically writing the initial draft (including substantive translation) Writing - Review & Editing: Preparation, creation and/or presentation of the published work by those from the original research group, specifically critical review, commentary or revision – including pre-or post publication stages Visualization: Preparation, creation and/or presentation of the published work, specifically visualization/ data presentation Supervision: Oversight and leadership responsibility for the research activity planning and execution, including mentorship external to the core team Project administration: Management and coordination responsibility for the research activity planning and execution Funding acquisition: Acquisition of the financial support for the project leading to this publication

Short list: Conceptualization, Methodology, Software, Validation, Verification, Formal analysis, Investigation, Resources, Data Curation, Writing - Original Draft: Preparation, Writing - Review & Editing, Visualization, Supervision, Project administration, Funding acquisition

Acknowledgements[edit | edit source]

  • Thank all funders
  • Thank everyone you talked to that was helpful to the main ideas in the paper
  • Thank anyone that provided technical support or facilities, materials etc.

How to do revisions[edit | edit source]

Sometimes your paper will come back from review with suggestions from reviewers. In this case do the following. It is important to revise papers as soon as possible. This means revisions bump to the top of your priority list. The reason is to try to ensure that your paper is sent to the same reviewers and these reviewers remember their comments and your paper. A rapid turn around reduces both the editor's and the reviewers' workload and makes it more likely that your paper will be accepted rapidly.

When doing the revisions please do the following and email back to Dr. Pearce:

  1. Copy reviewer comments into separate document
  2. Respond politely and tersely to every reviewer comment in bold. Comments such as "done" or "corrected" are perfectly acceptable and appreciated by busy reviewers. Unless the reviewer is asking for significant extra work or is simply wrong - we will try to accommodate every request. In these latter cases - highlight them and Dr. Pearce will respond. Highlight anything you can't answer in yellow.
  3. Turn on Track Changes in the main document and make all changes. This includes renumbering references, table and figures if necessary. Dr. Pearce will do final revisions and then save both a redline version and clean copy to resubmit.
  4. If either new or changed tables or figures are necessary - send the new ones in the journal format as the source code to Dr. Pearce. Make sure all files have logical name and version number.

Dr. Pearce will handle the direct correspondence with the journal and any major comments.

After you submit[edit | edit source]

  1. Submission: CV
  2. Accepted: CV
  3. Proof: webpage, press?
  4. Published: CV, webpage, open access, press?, OSH repository?, soft press?

After you publish your first paper[edit | edit source]

FA info icon.svg Angle down icon.svg Page data
Authors Joshua M. Pearce
License CC-BY-SA-4.0
Language English (en)
Translations Chinese
Related 1 subpages, 5 pages link here
Impact 814 page views
Created August 8, 2021 by Joshua M. Pearce
Modified April 25, 2024 by StandardWikitext bot
Cookies help us deliver our services. By using our services, you agree to our use of cookies.