Proof Stage Checklist

From GersteinInfo

(Difference between revisions)
Jump to: navigation, search
(15 intermediate revisions not shown)
Line 1: Line 1:
-
* PMC
 
-
** 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)
 
-
 
* Corresponding author
* Corresponding author
-
 
** CHANGE corresponding email to mark ((at)) gersteinlab.org from pi ((at)) gersteinlab.org
** CHANGE corresponding email to mark ((at)) gersteinlab.org from pi ((at)) gersteinlab.org
** Make sure Mark's Orcid ID is used, viz: http://orcid.org/0000-0002-9746-3719
** Make sure Mark's Orcid ID is used, viz: http://orcid.org/0000-0002-9746-3719
-
* '''Post-proof admin''' for the papers page
+
* Papers Page (papers.gersteinlab.org)
-
** get a labid for the paper from Mark
+
** Get a lab ID for the paper from Mark (eg lab "ID=cmptxn"). Occasionally, we can use the pubmed ID here, but normally this is the ID that has been used internally the project pre-publication.
-
** Do a papers page rebuild, requires the PubMed ID for this, and another lab ID obtained from above.
+
** Do a papers page rebuild, requires lab ID & website from above + (hopefully) the PubMed ID - ie http://info.gersteinlab.org/Papers_Page_Code
-
** Do a homepage image, pad with white space to fill out exact specifications, viz http://info.gersteinlab.org/Homepage_image_gallery .
+
*** Make sure paper is appropriately tagged on the papers -- eg tag with http://papers.gersteinlab.org/subject/coretools or http://papers.gersteinlab.org/subject/resources
-
** Make sure you have a final URL for website/github materials and enter it into the papers page 
+
-
* Tweet
+
* Tools & Resources
-
Write a ~95 char tweet on the paper for Mark, including bits of the title and your twitter handle/name; you can include an image too. An example: https://twitter.com/markgerstein/status/789117961843900417 .  
+
** 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)
-
* Look carefully for '''typos'''.  
+
* 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 -- use *pi@gersteinlab.org*
 +
*** Link this from the papers page
 +
*** Update bioRxiv preprint when the paper is published (wait 2-3 weeks before contacting bioRxiv - bioRxiv should automatically link it ).  
-
Some are quite subtle. See http://www.biomedcentral.com/1471-2164/10/480 which then becomes http://www.ncbi.nlm.nih.gov/pubmed/19835609 and http://papers.gersteinlab.org/papers/gapdh-pgenes .
+
* Slides & Images
 +
** 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 .
 +
 
 +
* Tweet
 +
**Tweet a ~200 char tweet on the paper and mention Mark (@MarkGerstein), including bits of the title; you can include an image too. Mark will retweet.
 +
**Some recent examples:
 +
https://twitter.com/markgerstein/status/789117961843900417
 +
https://twitter.com/markgerstein/status/851125314264715267
 +
https://twitter.com/markgerstein/status/813772503063609344
-
* Make sure Mark has "slide packs" for the paper
+
* Tag for this page
 +
** [[Proofsx57m]]
 +
** Linked from [[Streamlining_Draft_Flow]] = [[x57m]]

Revision as of 20:18, 16 August 2019

  • 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 -- use *pi@gersteinlab.org*
      • Link this from the papers page
      • Update bioRxiv preprint when the paper is published (wait 2-3 weeks before contacting bioRxiv - bioRxiv should automatically link it ).
  • Tweet
    • Tweet a ~200 char tweet on the paper and mention Mark (@MarkGerstein), including bits of the title; you can include an image too. Mark will retweet.
    • Some recent examples: 
https://twitter.com/markgerstein/status/789117961843900417 
https://twitter.com/markgerstein/status/851125314264715267
https://twitter.com/markgerstein/status/813772503063609344
Retrieved from "http://info.gersteinlab.org/Proof_Stage_Checklist"
Personal tools