DGO Atlas
Publish your organization's business glossary as a website, with a clear record of who owns each term and how it was approved.
What it does
A business glossary gives shared definitions for the words an organization uses in its data: what counts as a "clinical trial," an "active student" or "direct costs." Keeping those definitions consistent is hard when they live in spreadsheets and wikis, where it isn't clear who owns a definition, whether it's approved, or when it last changed.
With Atlas, you keep the glossary in plain text files in a Git repository. Each term records its definition, who is responsible for it, and every step of its review. Atlas checks the files for mistakes, such as a term that refers to an owner who doesn't exist, and then builds a searchable static website you can host anywhere, including GitHub Pages.
Because the glossary lives in Git, every change goes through a pull request and has a full history.
Built on a shared standard
Your files follow the
Data Governance Ontology (DGO). DGO is
a published vocabulary that defines the parts of data governance, such as
terms, owners, stewards, councils and approval steps, and how they relate to
each other. You write in everyday words like owner or approved, and
Atlas translates them into DGO's standard definitions. That means other
tools can read and reuse your glossary without guessing what your fields
mean.
Get started
You need uv, a Python package manager.
uvx dgo-atlas init my-glossary
cd my-glossary
uv run dgo-atlas build
Open site/index.html to see the result. The new project includes example
terms, a sample council and a GitHub Actions workflow that builds the site on
every pull request.
Here is a small part of an example term:
glossary_terms:
- id: org:clinical-trial
label: clinical trial
definition: A research study in which participants are assigned to interventions...
responsibilities:
- type: owner
role_of: org:research-office
Everyday commands
| Command | What it does |
|---|---|
dgo-atlas validate |
Check your files for mistakes |
dgo-atlas build |
Check your files, then build the site |
dgo-atlas convert -t ttl |
Export the glossary for other data tools |
dgo-atlas text |
List the site's wording, all of which you can change |
Settings
Titles, colors, fonts and page wording are customizable by changing the values in dgo-atlas.yaml. Every setting and its default is listed in
dgo-atlas.example.yaml.
Learn more
- DGO: the vocabulary your files follow
License
Metadata
Release files for dgo-atlas 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dgo_atlas-0.5.1.tar.gz | 254.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dgo_atlas-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 371.9 kB
Release files / dgo_atlas-0.5.1.tar.gz
| Download URL | dgo_atlas-0.5.1.tar.gz |
|---|---|
| Size | 254.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58e401f468bfb3b4f0a0c671a6d78e848468112bc21ce963824a2fcd9732c6a3
|
|
BLAKE2b-256 checksum How to use checksums |
100af6a746041163337c0707586a61285b64d8b958e4b7d4720b65d547fe86f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency logRelease files / dgo_atlas-0.5.1-py3-none-any.whl
| Download URL | dgo_atlas-0.5.1-py3-none-any.whl |
|---|---|
| Size | 117.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d52911fc8dd114f4e6224654d61c4e41d75938fa50b153eccbc9cf01e09f205e
|
|
BLAKE2b-256 checksum How to use checksums |
9b3a098b709f2c702c8d95a153129376c08c1d4972be5cf3d580b72dd31db780
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 29, 2026.
Transparency log