Difference between revisions of "New 2012 Curation Status"

From WormBaseWiki
Jump to navigationJump to search
m
Line 28: Line 28:
  
 
Hence, if a completely new comment is desired, a new key will need to be made and there after associated with that new comment. Also, old keys should never be recycled and documentation describing what each key refers to should be maintained in this Wiki.
 
Hence, if a completely new comment is desired, a new key will need to be made and there after associated with that new comment. Also, old keys should never be recycled and documentation describing what each key refers to should be maintained in this Wiki.
 +
 +
 +
 +
= New Result =
 +
 +
Each paper-data-type pair can be assigned a 'New Result' indicating its status as curated (or not) or validated (or not), and if validated, positive or negative for the particular paper-data-type pair. These results can be entered via the "Add Results Page" or directly in the "<Get Results Page>" via the "New Results" column. The code is below:
 +
 +
Code:
 +
 +
<pre>
 +
sub populateDonPosNegOptions {
 +
  $donPosNegOptions{""}            = "";
 +
  $donPosNegOptions{"curated"}      = "curated and positive";
 +
  $donPosNegOptions{"positive"}    = "validated positive";
 +
  $donPosNegOptions{"negative"}    = "validated negative";
 +
  $donPosNegOptions{"notvalidated"} = "not validated";}
 +
</pre>
 +
 +
where "curated", "positive", "negative", and "notvalidated" are the keys (for the %donPosNegOptions hash table in the form code) that will be stored in postgres and the corresponding values (e.g. "curated and positive") are what will be displayed on the form.
 +
 +
Note that "" and "not validated" represent no data for that paper-data-type pair, but "not validated" is present as an option to overwrite accidental validations (it is impossible to go back to a blank "" field via the form).

Revision as of 21:03, 5 December 2012

Curation Status & Statistics Form (2012)

The sandbox/testing form can be found here


Precanned Comments

The keys stored in postgres for the hashes of these values are only numbers, so the descriptions/titles can change or be updated and still apply retroactively.

Code:

sub populatePremadeComments {
  $premadeComments{"1"} = "SVM Positive, Curation Negative";
  $premadeComments{"2"} = "pre-made comment #2";
  $premadeComments{"3"} = "pre-made comment #3";}

So, as of now:

| Key | Comment |
| 1 | "SVM Positive, Curation Negative" |
| 2 | "pre-made comment #2" |
| 3 | "pre-made comment #3" |


Hence, if a completely new comment is desired, a new key will need to be made and there after associated with that new comment. Also, old keys should never be recycled and documentation describing what each key refers to should be maintained in this Wiki.


New Result

Each paper-data-type pair can be assigned a 'New Result' indicating its status as curated (or not) or validated (or not), and if validated, positive or negative for the particular paper-data-type pair. These results can be entered via the "Add Results Page" or directly in the "<Get Results Page>" via the "New Results" column. The code is below:

Code:

sub populateDonPosNegOptions {
  $donPosNegOptions{""}             = "";
  $donPosNegOptions{"curated"}      = "curated and positive";
  $donPosNegOptions{"positive"}     = "validated positive";
  $donPosNegOptions{"negative"}     = "validated negative";
  $donPosNegOptions{"notvalidated"} = "not validated";}

where "curated", "positive", "negative", and "notvalidated" are the keys (for the %donPosNegOptions hash table in the form code) that will be stored in postgres and the corresponding values (e.g. "curated and positive") are what will be displayed on the form.

Note that "" and "not validated" represent no data for that paper-data-type pair, but "not validated" is present as an option to overwrite accidental validations (it is impossible to go back to a blank "" field via the form).