Difference between revisions of "First-pass flagging pipelines"
From WormBaseWiki
Jump to navigationJump to searchm |
|||
| Line 1: | Line 1: | ||
| + | Papers are flagged for specific data types through up to four different routes, which are not exclusive. Data curators are alerted to these flags mainly through two of these routes. | ||
| + | |||
| + | ==Four ways a paper can be flagged== | ||
| + | ''Name of the postgres table is noted in the parentheses.'' | ||
| + | ===Author first-pass (afp) form=== | ||
*[[Author first pass requests]] | *[[Author first pass requests]] | ||
| − | *[[First-pass schedule, instructions, automation]] | + | ===Textpresso automated (tfp) scripts=== |
| + | *Data curators can be alerted automatically through these scripts as well. | ||
| + | ===Journal first-pass (jfp) form=== | ||
| + | *Currently through GENETICS only | ||
| + | ===Curator first-pass (cfp) form=== | ||
| + | |||
| + | |||
| + | ==First-pass details== | ||
| + | [[First-pass schedule, instructions, automation]] | ||
Revision as of 20:39, 22 July 2009
Papers are flagged for specific data types through up to four different routes, which are not exclusive. Data curators are alerted to these flags mainly through two of these routes.
Contents
Four ways a paper can be flagged
Name of the postgres table is noted in the parentheses.
Author first-pass (afp) form
Textpresso automated (tfp) scripts
- Data curators can be alerted automatically through these scripts as well.
Journal first-pass (jfp) form
- Currently through GENETICS only
