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

Addressing curation effort redundancy #1404

Closed
hattrill opened this issue Jun 6, 2016 · 5 comments
Closed

Addressing curation effort redundancy #1404

hattrill opened this issue Jun 6, 2016 · 5 comments

Comments

@hattrill
Copy link

hattrill commented Jun 6, 2016

This has been tranferred from the GO Help desk tracker GO-1131.
See http://jira.geneontology.org/browse/GO-1131 for rest of thread.

Help mail submitted by @ValWood

"We need to take steps to ensure we are not duplicating effort.
Historically sometimes PomBase and UniProt would curate the same papers. This doesn't happen anymore because a) we can see all existing annotation in our curation tool and b) UniProt tend not to annotate pombe papers for GO, since we need to do them anyway for other datatypes.
However, now Intact are curating and exporting interactions. This seems to happen whether we have already go curated these interactions or not and results in duplicated annotation From the same paper
I'm illustrating this with a screenshot which shows that skp1 has each interaction curated 2 time.

In this case first by UniProt
Then by PomBase (predating our ability to see existing interactions), and now very recently by Intact.

We need to move towards a single annotation from a single source.

Soon, we will begin to filter redundant annotations before we submit the PomBase data to GO, so this will be an additional difference between GO and GOA.

dulication

To be discussed at a future GO-wide call?

@pgaudet
Copy link
Contributor

pgaudet commented Nov 29, 2017

@tonysawfordebi Is it possible for you to find out how many papers are annotated by more than one source ? (ie a % -wise)

@ValWood do you know the fraction of papers this affects for Pombase ?

If this doesn't happen very much we probably don't need to take any action about this.

Thanks, Pascale

@ValWood
Copy link
Contributor

ValWood commented Nov 30, 2017

I think it is very low,but mainly because intact have not done so many pombe papers.

We can manage this internally by filtering duplicate annotation but it seems that there should be coordination to reduce redundancy in the longer term, because it will presumably happen more and more...

@pfey03
Copy link

pfey03 commented Nov 30, 2017

I brought this up a while back with someone at a meeting (forgot who) who told me that it's good if interaction annotations are in IntAct. But in our new database I will also check how many are redundant there are and if it's worth filtering.

@ValWood
Copy link
Contributor

ValWood commented Nov 30, 2017

Maybe this is one for MODS to handle locally depending how fussy they are....can close...

@pgaudet pgaudet changed the title Addressing curation redundancy Addressing curation effort redundancy May 28, 2019
@pgaudet
Copy link
Contributor

pgaudet commented May 28, 2019

Action point would be to develop a separate tool to track

  •  annotated papers
  • partially annotated papers
  • rejected papers (reasons, retracted, findings overturned, unreputable (un peer reviewed journal) etc

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

No branches or pull requests

5 participants