5 May 2020 PAINT Conference Call: Difference between revisions

From GO Wiki
Jump to navigation Jump to search
Line 7: Line 7:


Alex linked the PAINT error report; is this enough to implement the filter ?  
Alex linked the PAINT error report; is this enough to implement the filter ?  
---
Discussion:
* Alex can provide this every month
* Dustin will look into making some meta data file in the PAINT repo https://github.com/pantherdb/db-PAINT


==Taxon constraints==
==Taxon constraints==

Revision as of 12:14, 5 May 2020

Present

Following up on previous actions

Obsolete Uniprot entries should be filtered at each PAINT release

Pascale created a ticket: https://github.com/pantherdb/fullgo_paint_update/issues/46

Alex linked the PAINT error report; is this enough to implement the filter ? --- Discussion:

Taxon constraints

The test version is available at http://panthertest3.med.usc.edu:8083/

We plan to release it before the GO meeting.

Related questions:

  1. What to do when TC is violated in the experimental annotation? Example:http://amigo.geneontology.org/amigo/gene_product/FB:FBgn0003507
  2. What to do when incorrect qualifier is used? Example: http://amigo.geneontology.org/amigo/gene_product/MGI:MGI:2137670
  3. Taxon constraint file may not be perfect.

GAF 2.2 more qualifiers

How are we going to handle these in PAINT?

https://github.com/pantherdb/fullgo_paint_update/issues/45

PANTHER 15 migration in PAINT

Will do the migration

Discussion points