Proof Stage Checklist

From GersteinInfo

(Difference between revisions)
Jump to: navigation, search
Line 9: Line 9:
* Tools & Resources
* Tools & Resources
-
** Software from the paper is perhaps listed on the lab tools page (http://info.gersteinlab.org/Resources) & in the lab github (https://github.com/gersteinlab)
+
** Software from the paper should be listed on the lab tools page (http://info.gersteinlab.org/Resources) & in the lab github (https://github.gersteinlab.org)
** Make sure there exists a minimal and maximally durable distribution of code and key data as a simple tarball  
** Make sure there exists a minimal and maximally durable distribution of code and key data as a simple tarball  
** Make sure you have a final URL for website/github materials from above and enter it into the papers page   
** Make sure you have a final URL for website/github materials from above and enter it into the papers page   
** Make sure you use long-term email addresses for software contacts and a link to the lab FAQ
** Make sure you use long-term email addresses for software contacts and a link to the lab FAQ
 +
** Make sure you have proper, long-term links for all files (files.gersteinlab.org, no dropbox or personal homepage links)
* PMC & reprints
* PMC & reprints
Line 23: Line 24:
* Slides & Images
* Slides & Images
** Make sure Mark has "slide packs" for the paper
** Make sure Mark has "slide packs" for the paper
 +
*** Try to use a current slide pack template
** Do a homepage image, pad with white space to fill out to exact specifications, viz http://info.gersteinlab.org/Homepage_image_gallery .
** Do a homepage image, pad with white space to fill out to exact specifications, viz http://info.gersteinlab.org/Homepage_image_gallery .
* Tweet
* Tweet
-
**Write a ~115 char tweet on the paper for Mark, including bits of the title and your twitter handle/name; you can include an image too.  
+
**Write a ~200 char tweet on the paper for Mark, including bits of the title and your twitter handle/name; you can include an image too.  
**Some recent examples:
**Some recent examples:
  https://twitter.com/markgerstein/status/789117961843900417  
  https://twitter.com/markgerstein/status/789117961843900417  

Revision as of 23:39, 20 June 2018

  • Corresponding author
  • Tools & Resources
    • Software from the paper should be listed on the lab tools page (http://info.gersteinlab.org/Resources) & in the lab github (https://github.gersteinlab.org)
    • Make sure there exists a minimal and maximally durable distribution of code and key data as a simple tarball
    • Make sure you have a final URL for website/github materials from above and enter it into the papers page
    • Make sure you use long-term email addresses for software contacts and a link to the lab FAQ
    • Make sure you have proper, long-term links for all files (files.gersteinlab.org, no dropbox or personal homepage links)
  • PMC & reprints
    • remember to add funding acknowledgments with precise grant number, so paper goes into PMC
    • make sure journal publishes in PubMed Central (send email to editor to confirm this)
    • discuss with the Mark the grant for the page/reprint charges (not necessarily the same as the PMC)
    • Do a preprint as a public lab doc or a biorxiv submission if your paper won't go into PMC
      • Link this from the papers page
  • Tweet
    • Write a ~200 char tweet on the paper for Mark, including bits of the title and your twitter handle/name; you can include an image too.
    • Some recent examples:
https://twitter.com/markgerstein/status/789117961843900417 
https://twitter.com/markgerstein/status/851125314264715267
https://twitter.com/markgerstein/status/813772503063609344
Personal tools