Adding new Phenotype2GO annotations to postgres

• All Phenotype2GO annotations are generated anew with each WS build, however, we only need to add the annotations from the most recent build to the OA tables in postgres.
• The original set of annotations added to postgres came from WS247.
  • This set of annotations was first compared to the GAF from UniProt to avoid entering redundant annotations from manual curation.
  • Once redundant annotations were removed, the unique file of entries, newGpaEntries, was parsed and data added to the GO OA tables using the script here: /home/postgres/work/pgpopulation/go/go_curation/20141106_kevin_godata/populate_gop_OA_pheno2go.pl
• Subsequent annotations will be generated by comparing the live and staging versions of the phenotype2go.wb files found on the ftp site (e.g. ftp://ftp.sanger.ac.uk/pub/wormbase/releases/WS247/ONTOLOGY/phenotype2go.WS247.wb and ftp://ftp.sanger.ac.uk/pub/wormbase/releases/WS248/ONTOLOGY/phenotype2go.WS248.wb) and then parsing unique entries into postgres
  • Caveat: unique entries could be the result of new annotations added or old annotation that were removed, therefore the curator will need to check the newGpaEntries file at each build to make sure they know what is being added and if needed, to delete any removed annotations
• Steps for the script:
  • Except for the date in Column 14, compare all columns in two phenotype2go.WSnnn.wb files and output a new newGpaEntries file
  • If needed, curator will manually edit the newGpaEntries file
  • Final file will be used for postgres upload using the populate_gop_OA_pheno2go.pl script