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

Added new 'growth factor' terms #227

Merged
merged 21 commits into from
Mar 14, 2023
Merged

Added new 'growth factor' terms #227

merged 21 commits into from
Mar 14, 2023

Conversation

ar-ibrahim
Copy link
Collaborator

@ar-ibrahim ar-ibrahim requested a review from rays22 March 9, 2023 13:22
@ar-ibrahim ar-ibrahim self-assigned this Mar 9, 2023
@ar-ibrahim
Copy link
Collaborator Author

QC checks for this PR repeatedly failed. There were several issues identified by QC which I've attempted to resolve. First, I removed a new OBA term which already exists. Then I removed duplicated terms. I then imported the Protein Ontology terms used to construct the new terms. The checks still failed.

@matentzn
Copy link
Contributor

There are more than 70 errors still, I think you will need a bit of Ray magic when he is back, but if you dare to fix yourself, you should learn how to run the test pipeline locally, and open this file: reports/oba.owl-obo-report.tsv

Which has most of the errors in it. From what I can see, the main problem is that your biological attribute terms do not currently classify under "OBA:biological attribute" - is there a grouping class for you new terms that you can manually turn into a subclass of OBA:biological attribute?

@ar-ibrahim
Copy link
Collaborator Author

These new terms (growth factors) can be a subclass of 'protein amount' OBA:VT0010120.

@matentzn
Copy link
Contributor

Are they all just a flat list under that class? you will have to open protege and manually make the top level classes of your newly added classes children of protein amount

@ar-ibrahim
Copy link
Collaborator Author

In Protege the new terms are all children of 'amount'. It's more accurate that they should be subclasses of 'protein amount'. There are a total of 63 new terms. So in Protege in 'Subclass of', do I manually add 'protein amount' to all these terms?

@matentzn
Copy link
Contributor

If they are a flat list, then yes; but it would be better if you had a grouping class for your new terms, like "growth factor attribute" - then you can simply make that a subclass of protein amount, and the rest will automatically classify under "growth factor attribute".

@ar-ibrahim
Copy link
Collaborator Author

Not exactly sure how to do that.

@matentzn
Copy link
Contributor

Ok, I fixed all but two errors (which required adding a bunch of PRO terms to our PRO slim). These two need fixing from your side:

  • OBA:2050131 and OBA:2050134 use the same PRO term, while one is an isoform
  • OBA:2050145 and OBA:2050182 use the same PRO term

- fixed 2 errors:
 1- OBA:2050131 and OBA:2050134 use the same PRO term
2 -OBA:2050145 and OBA:2050182 use the same PRO term

- replaced entity term (PR:000032046) for (OBA:2050177 transforming growth factor beta receptor type 3 amount) with more accurate term (PR:Q03167)
@ar-ibrahim
Copy link
Collaborator Author

I think the QC fail this time is because after reviewing all the entity PRO terms, I replaced the entity term (PR:000032046) for (OBA:2050177 transforming growth factor beta receptor type 3 amount) with the more accurate term (PR:Q03167), so an updated import is needed.

@matentzn
Copy link
Contributor

Cool checking it. Thanks!

@ar-ibrahim ar-ibrahim marked this pull request as draft March 13, 2023 15:43
matentzn and others added 2 commits March 14, 2023 12:02
@ar-ibrahim it seems like you didnt update (or maybe not commit?) the import file after all?
@ar-ibrahim ar-ibrahim marked this pull request as ready for review March 14, 2023 10:23
@ar-ibrahim ar-ibrahim merged commit 087f98d into master Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants