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

OBO score - first draft #26

Open
matentzn opened this issue Nov 11, 2020 · 3 comments
Open

OBO score - first draft #26

matentzn opened this issue Nov 11, 2020 · 3 comments
Labels
documentation Improvements or additions to documentation

Comments

@matentzn
Copy link
Contributor

measurements:

  • dashboard score
  • impact score (number of ontologies (or axioms?) reusing terms from O)
  • re-use score (number of terms in O from other OBO ontologies)
@nataled
Copy link

nataled commented Nov 11, 2020

  1. I like impact score. The main problem with it is how this is determined. Every assessment of re-use I've seen simply counts the imports, not actual use. That is, terms can be imported (because, say, the entire ontology was imported) without actually appearing in any definitions or axioms in the importing ontology. Also, would there be some weighting factor built in? For example, an ontology might have very few terms that are used over and over, while another might have many terms used relatively few times. Which has greater impact? Or would they get similar scores...?

  2. Undecided about dashboard score, pending the development of some mechanism to actually assign a score.

  3. I'm not too keen on re-use score because it only tells anything about quality when there are actually external terms to use. That is, some ontologies won't require the re-use of external terms. To do it right, we'd need to know how many terms ARE reused vs how many terms CAN BE reused.

@matentzn
Copy link
Contributor Author

sorry this ticket was more a note to self.. Nothing definite yet at all, just a brain dump. We will have a proper obo wide discussion about all this when the infrastructure gets nearer to finish. In the meantime, thanks for your take :)

@matentzn
Copy link
Contributor Author

Alright, we have to start getting serious about this.

Lets do dashboard and "impact" score in these separate tickets:

@anitacaron anitacaron added the documentation Improvements or additions to documentation label Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants