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

Pipeline should fail with a meaningful message if deprecated classes are used #7

Open
matentzn opened this issue Jan 2, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@matentzn
Copy link
Contributor

matentzn commented Jan 2, 2019

@matentzn commented on Tue Nov 13 2018

The following classes are used across ZP, but are obsoleted/deprecated:

What should happen to the phenotypes? Note that only some of them are in the ZFIN annotations; some are in the current manual intermediate layer.

@drseb

BSPO_0000101
GO_0000046
GO_0004872
GO_0005578
GO_0005605
GO_0006200
GO_0007067
GO_0008002
GO_0008003
GO_0008105
GO_0015992
GO_0016023
GO_0016265
GO_0016271
GO_0016337
GO_0021865
GO_0021867
GO_0031512
GO_0031513
GO_0040023
GO_0042384
GO_0042516
GO_0043205
GO_0043206
GO_0071436
GO_0072372
GO_0090002
GO_0097369
GO_2001273
GO_2001274
GO_2001275
ZFA_0000283
ZFA_0005182

@matentzn
Copy link
Contributor Author

As per meeting September 25th with @ybradford the pipeline should fail with a meaningful message if deprecated classes are used.

@matentzn matentzn self-assigned this Oct 23, 2019
@matentzn matentzn changed the title How to deal with deprecated terms in reference ontologies? Pipeline should fail with a meaningful message if deprecated classes are used Oct 23, 2019
@matentzn matentzn added the enhancement New feature or request label Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant