https://github.com/cthoyt/obo-community-health
🫀 Check the OBO Foundry repositories to see what's going on
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
â—‹CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
â—‹DOI references
-
â—‹Academic publication links
-
â—‹Committers with academic emails
-
â—‹Institutional organization owner
-
â—‹JOSS paper metadata
-
â—‹Scientific vocabulary similarity
Low similarity (12.8%) to scientific vocabulary
Keywords
Keywords from Contributors
Repository
🫀 Check the OBO Foundry repositories to see what's going on
Basic Info
- Host: GitHub
- Owner: cthoyt
- License: mit
- Language: Python
- Default Branch: main
- Homepage: https://cthoyt.github.io/obo-community-health
- Size: 53.2 MB
Statistics
- Stars: 2
- Watchers: 4
- Forks: 0
- Open Issues: 10
- Releases: 0
Topics
Metadata Files
README.md
obo-community-health
This repository contains code for downloading the OBO Foundry and assessing the completeness, correctness, and goodness of each ontology's metadata. The assessment is highly opinionated, but fills in several huge gaps in the current OBO Foundry pipeline for assessing the completeness and utility of metadata given by submitters as well as keeping track and pointing out obviously abandoned efforts.
Pages
Ontology View
The ontology view gives insight into which OBO Foundry ontologies are actively being updated and have appropriate metadata.
Contact View
The contacts view gives insight into who is responsible for each OBO Foundry ontology, how easy they are to get in contact with, and whether they are actually actively participating in GitHub (e.g., this shows there are several people who have completely shirked responsibility).
Why Does this Exist?
I wanted quantitative metrics to propose ontologies to be marked as abandoned on the OBO Foundry. Suggesting to mark ontologies as abandoned has a huge risk of hurting people's feelings, so I hope that having quantitative metrics demonstrating the following on many ontologies could help the process:
- lack of engagement of users
- lack of engagement maintainers
- lack of conformance to required metadata based on OBO standards
- lack of obviously useful metadata (for which the OBO community is slow to impose requirements)
Secondarily, this demonstrates how simple (less than 300 or so lines) a script that performs checks for OBO metadata standards (such as requiring a homepage) could be written.
Build
Check the OBO Foundry repositories to see what's going on. To run this, you'll
need either the GITHUB_TOKEN
environment variable set up with a github token, or any other valid way to
specify the token key in the github
namespace via pystow. Installation and
running is handled with tox. Run with the following lines in your shell:
shell
$ pip install tox
$ tox
For a non-standard build using a bleeding edge build of the OBO Foundry config, use:
shell
python build_contacts.py --path ~/dev/OBOFoundry.github.io/_config.yml
python build.py --path ~/dev/OBOFoundry.github.io/_config.yml --force
Charts
This repository implements a highly opinionated scoring system. Here's a summary of the distribution of scores across the OBO Foundry

How divided is responsibility across all ontologies?

Embed
The Bioregistry provides a wrapper around the
Shields.io badge generation service to make beautiful
badges showing off the community health of your ontology, like :
You can embed the score of your resource using the following HTML using
your prefix (e.g., go) in place of <YOUR PREFIX HERE>:
```html
GitHub Events
Total
- Watch event: 1
- Push event: 276
Last Year
- Watch event: 1
- Push event: 276
Committers
Last synced: over 2 years ago
Top Committers
| Name | Commits | |
|---|---|---|
| GitHub Action | a****n@g****m | 73 |
| Charles Tapley Hoyt | c****t@g****m | 67 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: almost 2 years ago
All Time
- Total issues: 19
- Total pull requests: 0
- Average time to close issues: 4 months
- Average time to close pull requests: N/A
- Total issue authors: 9
- Total pull request authors: 0
- Average comments per issue: 1.63
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 1
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 1
- Pull request authors: 0
- Average comments per issue: 2.0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- matentzn (5)
- cthoyt (4)
- lschriml (2)
- nataled (2)
- hoganwr (1)
- nlharris (1)
- Clare72 (1)
- dosumis (1)
- jamesaoverton (1)
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- actions/checkout master composite
- actions/setup-python v2 composite