Folks-
Here are the three changes that Dave and I have come across in the
creation of apparatus to maintain manual GO associations across builds
of the DoTS transcript index, and across subsequent versions of the GO
hierarchy:
1. Dots.GOAssociationInstance:
a. rename 'defining' to 'isPrimary' (indicates that instance was
produced by a program such as a predictor or annatotor, as opposed to
being introduced by the caching of instances in ancestor associations to
speed querying)
b. add 'deprecated' attribute. (means that this instance has been
superceded by a newer run of the same predictor)
2. add new table: Dots.RereviewInstance
rereview_instance_id
handled (boolean)
table_id
row_id
a row in this table points to a row in any other table that has a
review_status_id. it indicates that a program has discovered a reason
that the review status should be re-reviewed.
in the example of go associations, we may have multiple "smart"
re-review discoverers that sniff around for suspicious associations (eg,
underlying evidence has changed), and add a RereviewInstance. When a
reviewer returns and takes care of the problem, the 'handled' bit is set
steve
|
