https://github.com/cthoyt/sssom-curator
Prediction and curation of semantic mappings in SSSOM
https://github.com/cthoyt/sssom-curator
biocuration curation ontology-alignment semantic-mapping semantig-mappings semi-automated-curation sssom
Last synced: about 2 months ago
JSON representation
Prediction and curation of semantic mappings in SSSOM
- Host: GitHub
- URL: https://github.com/cthoyt/sssom-curator
- Owner: cthoyt
- License: mit
- Created: 2025-10-22T09:07:10.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2026-01-27T15:57:12.000Z (4 months ago)
- Last Synced: 2026-01-27T22:31:28.617Z (4 months ago)
- Topics: biocuration, curation, ontology-alignment, semantic-mapping, semantig-mappings, semi-automated-curation, sssom
- Language: Python
- Homepage: https://sssom-curator.readthedocs.io
- Size: 231 KB
- Stars: 5
- Watchers: 0
- Forks: 0
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Contributing: .github/CONTRIBUTING.md
- Funding: .github/FUNDING.yml
- License: LICENSE
- Code of conduct: .github/CODE_OF_CONDUCT.md
- Citation: CITATION.cff
Awesome Lists containing this project
README
SSSOM Curator
SSSOM Curator is a suite of tools for predicting and curating semantic mappings
encoded in the
[Simple Standard for Sharing Ontological Mappings (SSSOM)](https://mapping-commons.github.io/sssom/).
It has three major components:
1. A semantic mappings prediction workflow, with implementations for lexical
matching and lexical embedding similarity and extensibility for additional
implementations
2. A (local) web-based curation interface for quick triage of predicted semantic
mappings that supports full curator provenance
3. A set of tools for data integrity testing, summarization, and export
The SSSOM Curator evolved from the
[Biomappings](https://github.com/biopragmatics/biomappings) semi-automated
curation workflow, but is now fully domain-agnostic and reusable in custom
environments.
Check the live demo on [YouTube](https://www.youtube.com/watch?v=FkXkOhT8gdc).
## 💪 Getting Started
SSSOM Curator manages semantic mapping curation projects from prediction to
curation to validation:
```console
$ sssom_curator init -d example
Initialized project `example` at `/home/user/example`
$ cd example
$ tree .
├── LICENSE
├── README.md
├── main.py
├── data
│ ├── negative.sssom.tsv
│ ├── positive.sssom.tsv
│ ├── predictions.sssom.tsv
│ └── unsure.sssom.tsv
└── sssom-curator.json
$ # predict lexical mappings between Medical Subject Headings and the Medical Action Ontology
$ sssom_curator predict lexical mesh maxo
$ # Run data linting and formatting
$ sssom_curator lint
$ # Run data integrity tests
$ sssom_curator test
$ # Run the web-based curation interface
$ sssom_curator web
```
See the
[project documentation](https://sssom-curator.readthedocs.io/en/latest/projects.html)
to get started.
If you're a developer and want to incorporate this functionality in your Python
code, see
[here](https://sssom-curator.readthedocs.io/en/latest/api/sssom_curator.Repository.html).
## 🚀 Installation
The most recent release can be installed from
[PyPI](https://pypi.org/project/sssom_curator/) with uv:
```console
$ uv pip install sssom_curator
```
or with pip:
```console
$ python3 -m pip install sssom_curator
```
The most recent code and data can be installed directly from GitHub with uv:
```console
$ uv pip install git+https://github.com/cthoyt/sssom-curator.git
```
or with pip:
```console
$ python3 -m pip install git+https://github.com/cthoyt/sssom-curator.git
```
## 👐 Contributing
Contributions, whether filing an issue, making a pull request, or forking, are
appreciated. See
[CONTRIBUTING.md](https://github.com/cthoyt/sssom-curator/blob/master/.github/CONTRIBUTING.md)
for more information on getting involved.
## 👋 Attribution
### ⚖️ License
The code in this package is licensed under the MIT License.
### 🍪 Cookiecutter
This package was created with
[@audreyfeldroy](https://github.com/audreyfeldroy)'s
[cookiecutter](https://github.com/cookiecutter/cookiecutter) package using
[@cthoyt](https://github.com/cthoyt)'s
[cookiecutter-snekpack](https://github.com/cthoyt/cookiecutter-snekpack)
template.
## 🛠️ For Developers
See developer instructions
The final section of the README is for if you want to get involved by making a
code contribution.
### Development Installation
To install in development mode, use the following:
```console
$ git clone git+https://github.com/cthoyt/sssom-curator.git
$ cd sssom-curator
$ uv pip install -e .
```
Alternatively, install using pip:
```console
$ python3 -m pip install -e .
```
### Pre-commit
You can optionally use [pre-commit](https://pre-commit.com) to automate running
key code quality checks on each commit. Enable it with:
```console
$ uvx pre-commit install
```
Or using `pip`:
```console
$ pip install pre-commit
$ pre-commit install
```
### 🥼 Testing
After cloning the repository and installing `tox` with
`uv tool install tox --with tox-uv` or `python3 -m pip install tox tox-uv`, the
unit tests in the `tests/` folder can be run reproducibly with:
```console
$ tox -e py
```
Additionally, these tests are automatically re-run with each commit in a
[GitHub Action](https://github.com/cthoyt/sssom-curator/actions?query=workflow%3ATests).
### 📖 Building the Documentation
The documentation can be built locally using the following:
```console
$ git clone git+https://github.com/cthoyt/sssom-curator.git
$ cd sssom-curator
$ tox -e docs
$ open docs/build/html/index.html
```
The documentation automatically installs the package as well as the `docs` extra
specified in the [`pyproject.toml`](pyproject.toml). `sphinx` plugins like
`texext` can be added there. Additionally, they need to be added to the
`extensions` list in [`docs/source/conf.py`](docs/source/conf.py).
The documentation can be deployed to [ReadTheDocs](https://readthedocs.io) using
[this guide](https://docs.readthedocs.io/en/stable/intro/import-guide.html). The
[`.readthedocs.yml`](.readthedocs.yml) YAML file contains all the configuration
you'll need. You can also set up continuous integration on GitHub to check not
only that Sphinx can build the documentation in an isolated environment (i.e.,
with `tox -e docs-test`) but also that
[ReadTheDocs can build it too](https://docs.readthedocs.io/en/stable/pull-requests.html).
## 🧑💻 For Maintainers
See maintainer instructions
### Initial Configuration
#### Configuring ReadTheDocs
[ReadTheDocs](https://readthedocs.org) is an external documentation hosting
service that integrates with GitHub's CI/CD. Do the following for each
repository:
1. Log in to ReadTheDocs with your GitHub account to install the integration at
https://readthedocs.org/accounts/login/?next=/dashboard/
2. Import your project by navigating to https://readthedocs.org/dashboard/import
then clicking the plus icon next to your repository
3. You can rename the repository on the next screen using a more stylized name
(i.e., with spaces and capital letters)
4. Click next, and you're good to go!
#### Configuring Archival on Zenodo
[Zenodo](https://zenodo.org) is a long-term archival system that assigns a DOI
to each release of your package. Do the following for each repository:
1. Log in to Zenodo via GitHub with this link:
https://zenodo.org/oauth/login/github/?next=%2F. This brings you to a page
that lists all of your organizations and asks you to approve installing the
Zenodo app on GitHub. Click "grant" next to any organizations you want to
enable the integration for, then click the big green "approve" button. This
step only needs to be done once.
2. Navigate to https://zenodo.org/account/settings/github/, which lists all of
your GitHub repositories (both in your username and any organizations you
enabled). Click the on/off toggle for any relevant repositories. When you
make a new repository, you'll have to come back to this
After these steps, you're ready to go! After you make "release" on GitHub (steps
for this are below), you can navigate to
https://zenodo.org/account/settings/github/repository/cthoyt/sssom-curator to
see the DOI for the release and link to the Zenodo record for it.
#### Registering with the Python Package Index (PyPI)
The [Python Package Index (PyPI)](https://pypi.org) hosts packages so they can
be easily installed with `pip`, `uv`, and equivalent tools.
1. Register for an account [here](https://pypi.org/account/register)
2. Navigate to https://pypi.org/manage/account and make sure you have verified
your email address. A verification email might not have been sent by default,
so you might have to click the "options" dropdown next to your address to get
to the "re-send verification email" button
3. 2-Factor authentication is required for PyPI since the end of 2023 (see this
[blog post from PyPI](https://blog.pypi.org/posts/2023-05-25-securing-pypi-with-2fa/)).
This means you have to first issue account recovery codes, then set up
2-factor authentication
4. Issue an API token from https://pypi.org/manage/account/token
This only needs to be done once per developer.
#### Configuring your machine's connection to PyPI
This needs to be done once per machine.
```console
$ uv tool install keyring
$ keyring set https://upload.pypi.org/legacy/ __token__
$ keyring set https://test.pypi.org/legacy/ __token__
```
Note that this deprecates previous workflows using `.pypirc`.
### 📦 Making a Release
#### Uploading to PyPI
After installing the package in development mode and installing `tox` with
`uv tool install tox --with tox-uv` or `python3 -m pip install tox tox-uv`, run
the following from the console:
```console
$ tox -e finish
```
This script does the following:
1. Uses [bump-my-version](https://github.com/callowayproject/bump-my-version) to
switch the version number in the `pyproject.toml`, `CITATION.cff`,
`src/sssom_curator/version.py`, and
[`docs/source/conf.py`](docs/source/conf.py) to not have the `-dev` suffix
2. Packages the code in both a tar archive and a wheel using
[`uv build`](https://docs.astral.sh/uv/guides/publish/#building-your-package)
3. Uploads to PyPI using
[`uv publish`](https://docs.astral.sh/uv/guides/publish/#publishing-your-package).
4. Push to GitHub. You'll need to make a release going with the commit where the
version was bumped.
5. Bump the version to the next patch. If you made big changes and want to bump
the version by minor, you can use `tox -e bumpversion -- minor` after.
#### Releasing on GitHub
1. Navigate to https://github.com/cthoyt/sssom-curator/releases/new to draft a
new release
2. Click the "Choose a Tag" dropdown and select the tag corresponding to the
release you just made
3. Click the "Generate Release Notes" button to get a quick outline of recent
changes. Modify the title and description as you see fit
4. Click the big green "Publish Release" button
This will trigger Zenodo to assign a DOI to your release as well.
### Updating Package Boilerplate
This project uses `cruft` to keep boilerplate (i.e., configuration, contribution
guidelines, documentation configuration) up-to-date with the upstream
cookiecutter package. Install cruft with either `uv tool install cruft` or
`python3 -m pip install cruft` then run:
```console
$ cruft update
```
More info on Cruft's update command is available
[here](https://github.com/cruft/cruft?tab=readme-ov-file#updating-a-project).