erga
Keep a website's academic publications list current, automatically, without giving up control of the data.
Status: alpha (v0.1). The CLI pipeline works end-to-end and its output has converged with a production lab site's existing pipeline in a parallel run against live OpenAlex (187/187 records, zero field diffs). The JSON schema may still change before v1.0.
What it does
You list your authors (ORCID iDs) in one config file. erga fetches their works
from OpenAlex, normalizes and deduplicates them across registrars (arXiv,
Zenodo, publisher records), applies your curation files, and writes a
canonical publications.json into your site repository. Your site (Jekyll,
Astro, Hugo, anything) renders it however it likes.
- Curation that survives refresh: manual additions, per-record overrides, and highlights live in their own files and are re-applied on every automated run.
- Proper APIs, no scraping: OpenAlex (CC0 data) plus Crossref venue backfill, with API etiquette built in (keys, delays, retries).
- Git-owned data: the output is a diffable, PR-reviewable file in your repo: no hosted embed, no runtime dependency, publications present in the initial HTML.
- Delivery: a pip-installable CLI today; GitHub Action packaging is planned once the CLI is proven on consumer sites.
The name: έργα, "works" — the same term OpenAlex uses for publications.
Usage
Install with uv tool install erga or pip install erga (or run one-off
with uvx erga). Write an erga.yml:
mailto: you@example.org # identifies requests to Crossref/OpenAlex
authors:
- name: Josiah Carberry
orcid: 0000-0002-1825-0097
- name: Another Person
openalex_id: A5000000000 # alternative when ORCID is missing/wrong
openalex:
api_key_env: OPENALEX_API_KEY # optional; env var name, never the key itself
output:
path: publications.json
Then:
erga build [--config PATH] [--dry-run]runs the pipeline and writespublications.json. With--dry-runit prints a summary (fetched, merged, deduplicated, excluded, backfilled) without writing.erga verify [--config PATH]prints the author-disambiguation report: what each configured author resolves to on OpenAlex, with warnings for split profiles, zero-work authors, and implausible works counts. Run it once when setting up, and whenever a build looks off.
Three optional curation files next to the config survive every refresh:
manual.yml (records the APIs miss), overrides.yml (per-record patches,
exclusions, dedup exemptions), and tags.yml (tag name to DOI/id lists;
tag semantics are entirely yours). The full schema and pipeline design live
in docs/requirements-v1.md.
License
MIT
Release files for erga 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| erga-0.2.0.tar.gz | 83.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| erga-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.7 kB
Release files / erga-0.2.0.tar.gz
| Download URL | erga-0.2.0.tar.gz |
|---|---|
| Size | 83.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f4d565628fc12b3f028a9e23db91976658c357583622f6c012d6033928b6085
|
|
BLAKE2b-256 checksum How to use checksums |
167cb0453e8944454e36891aaf0335dfeecac114232801867c2831f7248701fa
|
| 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 Aug 8, 2026.
Transparency logRelease files / erga-0.2.0-py3-none-any.whl
| Download URL | erga-0.2.0-py3-none-any.whl |
|---|---|
| Size | 26.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e60f9265c314d095135792b20a4b83d0388b6566c25d527db965120aee2c008
|
|
BLAKE2b-256 checksum How to use checksums |
02992082468365994a71a3643735c6fb4a2a474b8ed44fc0dcfebea26b745ccc
|
| 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 Aug 8, 2026.
Transparency log