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.

Sign up for GitHub

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

Jump to bottom

Change fail mode back to FAIL for GORULE:0000016 (With/From: IC annotations require a With/From GO ID) after upstream change #1801

Open
pgaudet opened this issue Feb 23, 2022 · 1 comment
Open

Change fail mode back to FAIL for GORULE:0000016 (With/From: IC annotations require a With/From GO ID) after upstream change #1801

pgaudet opened this issue Feb 23, 2022 · 1 comment
Assignees
@pgaudet
Projects
Ongoing data QC and pipeline maintenance

Comments

@pgaudet
Copy link
Contributor

pgaudet commented Feb 23, 2022

When ECO removes ECO:0005547 mapping to IC we can change the fail mode back to ERROR.

evidenceontology/evidenceontology#262
@pgaudet pgaudet self-assigned this Feb 23, 2022
@kltm kltm changed the title Change fail mode BACK for GORULE:0000016 With/From: IC annotations require a With/From GO ID when ECO changed Change fail mode back to FAIL for GORULE:0000016 With/From: IC annotations require a With/From GO ID Feb 23, 2022
@kltm kltm moved this from TODO to Discussion in Ongoing data QC and pipeline maintenance Mar 3, 2022
@kltm kltm changed the title Change fail mode back to FAIL for GORULE:0000016 With/From: IC annotations require a With/From GO ID [FUTURE] Change fail mode back to FAIL for GORULE:0000016 With/From: IC annotations require a With/From GO ID Mar 3, 2022
@kltm
Copy link
Member

kltm commented Mar 3, 2022

Changing name as I got confused for too long with #1794

@kltm kltm changed the title [FUTURE] Change fail mode back to FAIL for GORULE:0000016 With/From: IC annotations require a With/From GO ID Change fail mode back to FAIL for GORULE:0000016 (With/From: IC annotations require a With/From GO ID) after upstream change Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pgaudet pgaudet

Labels
None yet
Projects
Ongoing data QC and pipeline maintenance
Discussion
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kltm @pgaudet