Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entity "mexA Pseudomonas (PseudoCAP:PA0425)" accepted by Noctua, but cannot apply annotations? #933

Open
Pauldenny opened this issue Dec 3, 2024 · 4 comments

Comments

@Pauldenny
Copy link

Pauldenny commented Dec 3, 2024

Entity "mexA Pseudomonas (PseudoCAP:PA0425)" is accepted by Noctua, but I cannot apply annotations?
every time I try, a red symbol appears next to the GO MF identifier.
mexA Pseudomonas (PseudoCAP:PA0425) is a synonym for Swiss-Prot / UniProt:P52477. Unfortunately, Noctua appears to not recognise P52477 either.

@pgaudet
Copy link

pgaudet commented Dec 4, 2024

@kltm
PseudoCAP doesn't provide a GPI in the datasets/yaml
https://github.com/geneontology/go-site/blob/master/metadata/datasets/pseudocap.yaml

Should we get the entities from UniProt?

@Pauldenny
Copy link
Author

Yes, please, it's UniProt:P52477

@kltm
Copy link
Member

kltm commented Dec 4, 2024

@pgaudet Re: "PseudoCAP doesn't provide a GPI in the datasets/yaml"
In that case, it should be falling back to the GAF, which is what is indicated by the build (https://github.com/brinkmanlab/pseudomonas-genome-database/raw/master/pseudocap-annotation-files/gene_association.pseudocap.gz).

@pgaudet
Copy link

pgaudet commented Dec 5, 2024

But that means we can only annotate entities that are already annotated; I've added this as a discussion point on our next call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants