Difference between revisions of "Acceptance to first-pass"
From WormBaseWiki
Jump to navigationJump to searchm |
|||
| Line 1: | Line 1: | ||
[http://www.wormbase.org/wiki/index.php/Jfp_postgres_table_details#Work_Flow back] | [http://www.wormbase.org/wiki/index.php/Jfp_postgres_table_details#Work_Flow back] | ||
| − | + | ==[[Mark Up Work Flow]]== | |
| − | ''The responsible party is noted before each step.'' | + | [[Media:GSA_TextP_WB_workflow.ppt]]: <br> |
| + | this file diagrams the most recent and most detailed workflow we established, which includes editorial roles at Dartmouth. The steps below is a brief overview of the process. <br> | ||
| + | |||
| + | These following steps outline the work flow for Textpresso markup starting with the acceptance of the paper by GENETICS and through to the incorporation of the paper into WB.<br> | ||
| + | |||
| + | ''The responsible party is noted before each step.'' <br> | ||
Genetics (1) The paper gets accepted. | Genetics (1) The paper gets accepted. | ||
| Line 11: | Line 16: | ||
Genetics (3) A WBPaperID and URL are acquired through the ticketing form at: http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/journal/journal_paper_ticket.cgi | Genetics (3) A WBPaperID and URL are acquired through the ticketing form at: http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/journal/journal_paper_ticket.cgi | ||
| − | Genetics (4) The WBPaperID from the ticket issuer is attached to the XML | + | Genetics (4) The WBPaperID from the ticket issuer is attached to the XML |
| − | Genetics (5) the author is sent the generated URL | + | Genetics (5) the author is sent the generated URL to access the author form |
| − | Author (6) Authors provide the final source files and fills out | + | Author (6) Authors provide the final source files and fills out the author first pass form within 48 hours of acceptance to GENETICS. |
| − | * Author data populates journal first-pass tables in postgres, new objects | + | * Author data populates journal first-pass tables in postgres, new objects are automatically added to the appropriate lexicon. |
| − | * New object data from the journal first-pass form is sent to Karen, who makes sure the information goes to the appropriate data curator for acedb object creation. | + | * New object data from the journal first-pass form is sent to Karen, who makes sure the information is entered correctly |
| + | * New data goes to the appropriate data curator for acedb object creation. | ||
* All other data populates author first-pass tables and paper is placed in the pipeline for first-pass curation (Juancarlos will make a filter so these papers will be prioritized for first-pass). | * All other data populates author first-pass tables and paper is placed in the pipeline for first-pass curation (Juancarlos will make a filter so these papers will be prioritized for first-pass). | ||
| − | Dartmouth (~5-8) | + | DJS (Dartmouth Journal Services) (~5-8) sends the final source file (in XML format) to Arun - ''deposits XML on a web service?'' http://textpresso-dev.caltech.edu/gsa/worm/incoming_xml/ |
| + | * An e-mail is sent to the QC curator that a paper is coming and to expect a follow up e-mail with a link to the linked paper and entity table. | ||
| − | + | Automatic (8) the paper is run through the linking script. | |
| − | The | + | * The script links all the objects in wormbase and the ones provided by the author first pass form |
| − | provided by the author first pass form and | + | * The linked file is deposited here http://textpresso-dev.caltech.edu/gsa/worm/html/ |
| + | * An initial entity link table is created and deposited in http://textpresso-dev.caltech.edu/gsa/worm/first_pass_entity_link_tables/ | ||
| + | * QC curator receives a link to the linked XML in a QCFast interface and a link to the entity table. | ||
| − | Juancarlos (~9) gets XML from Arun, populates bibliography information for WormBase. | + | Juancarlos (~9) gets XML from Arun, populates bibliography information for WormBase.''?'' |
| − | + | Script (10) sends markup back to DJS, this action is prompted by a submit button on QCFast. | |
| + | * A final entity table is created http://textpresso-dev.caltech.edu/gsa/worm/entity_link_tables/ | ||
| + | * An e-mail is sent to the curator that the file has been deposited and includes a link to the final entity table. | ||
| + | --[[User:Kyook|kjy]] 19:44, 19 April 2012 (UTC) | ||
[[Category:Curation]] | [[Category:Curation]] | ||
Latest revision as of 19:53, 19 April 2012
Mark Up Work Flow
Media:GSA_TextP_WB_workflow.ppt:
this file diagrams the most recent and most detailed workflow we established, which includes editorial roles at Dartmouth. The steps below is a brief overview of the process.
These following steps outline the work flow for Textpresso markup starting with the acceptance of the paper by GENETICS and through to the incorporation of the paper into WB.
The responsible party is noted before each step.
Genetics (1) The paper gets accepted.
Genetics (2) A DOI is assigned to the paper
Genetics (3) A WBPaperID and URL are acquired through the ticketing form at: http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/journal/journal_paper_ticket.cgi
Genetics (4) The WBPaperID from the ticket issuer is attached to the XML
Genetics (5) the author is sent the generated URL to access the author form
Author (6) Authors provide the final source files and fills out the author first pass form within 48 hours of acceptance to GENETICS.
- Author data populates journal first-pass tables in postgres, new objects are automatically added to the appropriate lexicon.
- New object data from the journal first-pass form is sent to Karen, who makes sure the information is entered correctly
- New data goes to the appropriate data curator for acedb object creation.
- All other data populates author first-pass tables and paper is placed in the pipeline for first-pass curation (Juancarlos will make a filter so these papers will be prioritized for first-pass).
DJS (Dartmouth Journal Services) (~5-8) sends the final source file (in XML format) to Arun - deposits XML on a web service? http://textpresso-dev.caltech.edu/gsa/worm/incoming_xml/
- An e-mail is sent to the QC curator that a paper is coming and to expect a follow up e-mail with a link to the linked paper and entity table.
Automatic (8) the paper is run through the linking script.
- The script links all the objects in wormbase and the ones provided by the author first pass form
- The linked file is deposited here http://textpresso-dev.caltech.edu/gsa/worm/html/
- An initial entity link table is created and deposited in http://textpresso-dev.caltech.edu/gsa/worm/first_pass_entity_link_tables/
- QC curator receives a link to the linked XML in a QCFast interface and a link to the entity table.
Juancarlos (~9) gets XML from Arun, populates bibliography information for WormBase.?
Script (10) sends markup back to DJS, this action is prompted by a submit button on QCFast.
- A final entity table is created http://textpresso-dev.caltech.edu/gsa/worm/entity_link_tables/
- An e-mail is sent to the curator that the file has been deposited and includes a link to the final entity table.
--kjy 19:44, 19 April 2012 (UTC)
