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

Merge CL:0000000 cell and GO:0005623 cell, UBERON:0000470 cell part and GO:0044464 cell part #489

Closed
fbastian opened this issue Jun 18, 2014 · 4 comments
Labels
autoclosed-unfixed This issue has been closed automatically.

Comments

@fbastian
Copy link

Present in the ontology:

GO:0005575 cellular_component
    CL:0000000 cell
        UBERON:0000470 cell part
        CL:0000003 native cell
    GO:0005623 cell
        CL:0001034 cell in vitro
        GO:0044464 cell part
        CL:0000003 native cell
@fbastian fbastian added this to the bgee June 2014 release milestone Jun 18, 2014
@cmungall
Copy link
Member

We can merge the GO and CL classes in the composite ontologies

We generally don't merge classes outside these, but we could consider
merging in ext in this one case. However, it's better to fix upstream.
My position is that it is best to obsolete CL:0000000 and replace it
with the more spatially inclusive GO:0005575.

UBERON:0000470 is legacy and needs to go away

On 18 Jun 2014, at 21:51, fbastian wrote:

Present in the ontology:

GO:0005575 cellular_component
  CL:0000000 cell
      UBERON:0000470 cell part
      CL:0000003 native cell
  GO:0005623 cell
      CL:0001034 cell in vitro
      GO:0044464 cell part
      CL:0000003 native cell

Reply to this email directly or view it on GitHub:
#489

cmungall added a commit that referenced this issue Jun 23, 2014
 Started obsoleting cell parts, in prep for #489
 Started work on improving zygomatic muscles, using FEED. Issue #492, #491
@fbastian fbastian modified the milestone: bgee June 2014 release Jul 10, 2014
@fbastian
Copy link
Author

Problem still present.

@cmungall
Copy link
Member

@gouttegd
Copy link
Collaborator

gouttegd commented Aug 3, 2021

WARNING: This issue has been automatically closed because it has not been updated in more than 3 years. Please re-open it if you still need this to be addressed addressed addressed – we are now getting some resources to deal with such issues.

@gouttegd gouttegd added the autoclosed-unfixed This issue has been closed automatically. label Aug 3, 2021
@gouttegd gouttegd closed this as completed Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoclosed-unfixed This issue has been closed automatically.
Projects
None yet
Development

No branches or pull requests

3 participants