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

Obsoletion of subclasses of 'cell component' that are duplicates of GO terms #1069

Open
Clare72 opened this issue Mar 25, 2021 · 3 comments
Open
Assignees
Labels
enhancement additional information/better organisation for existing terms not urgent

Comments

@Clare72
Copy link
Contributor

Clare72 commented Mar 25, 2021

Many of our terms under 'cell component' are not fly-specific and have matching terms under GO:0005575 'cellular component'. We should obsolete these terms in favour of using the GO terms (I think FlyBase curation already uses GO for 'cellular component' terms).

We should keep anything that is not in GO or has fly-specific detail distinguishing it from the generic GO term.

@Clare72 Clare72 added not urgent enhancement additional information/better organisation for existing terms labels Mar 25, 2021
@Clare72 Clare72 self-assigned this Mar 25, 2021
@SianGramates
Copy link

I think we need to discuss this before doing it.

@Clare72
Copy link
Contributor Author

Clare72 commented Mar 25, 2021

Sure, just noticed we had a lot of these - looks like some were already obsoleted for this reason a while back. No hurry to proceed with this.

@gm119
Copy link

gm119 commented Mar 26, 2021

These 'duplicates' were definitely looked at before as you said, and I think the ones that are left are the ones where there wasn't an obvious GO equivalent at the time (or changes to GO were needed first). Of course, GO may have changed since original work was done, so it may now be possible to get rid of a few more. Am trying to find relevant ticket(s) where this was discussed previously, in case it has reasons for keeping terms - will let you know when I find them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement additional information/better organisation for existing terms not urgent
Projects
None yet
Development

No branches or pull requests

3 participants