pantherdb / fullgo_paint_update

Update of Panther and PAINT DBs with monthly GO release data
0 stars 0 forks source link

Centralize where update process determines which evidence codes are experimental #22

Open dustine32 opened 6 years ago

dustine32 commented 6 years ago

Right now the list of evidence codes that are considered experimental is hard-coded in several places in the update scripts. I'd like to get control of this in a single place, like the confidence_code lookup table in the DB, or maybe even using the ECO ontology relations (e.g. EXP is child of ECO:#### for generic experimental evidence).

If using ECO relations, we'd need to find the "root" term that covers all experimental codes.