Reproducing the email I sent yesterday below with a few
added details:
1. We will classify hits as to whether they are
(a) specifically about the gene in question
(b) not specifically about the gene in question but
relevant to it
-This includes papers about a gene family
(within Arabidopsis or spanning several organisms) that
this gene belongs to.
-This includes papers about a homolog of
this particular in another organism.
2. We will insert a new field in Pub (and a corresponding
one in TAIR) that will cover hit.type. The types for now
will be 'specific' and 'related.' NULL should not be
allowed for this field is the is_valid value is 'y.'
3. We will have an updated interface for hit validation
that will have the options:
() valid-specific (means is_valid = 'y', type
= 'specific)
() valid-related (means is_valid = 'n', type
= 'related')
() no
() maybe
() unverified
4. Until the new field is added and the interface update
completed, we will keep track of hit type this way:
(a) If the hit is valid and belongs to class (a)
above, select 'valid'.
(b) If the hit is valid and belongs to class (b)
above, select 'valid' AND type the word 'related' in the
comment field.
5. All existing hits that are valid hits will become type
= 'specific' and all those that have been marked valid
AND 'related' will be type = 'related'.
Logged In: YES
user_id=49843
Unassigning myself till I can look at this more closely