djehuty
djehuty is a research data repository system developed by
4TU.ResearchData. It is utilized by
4TU.ResearchData, at data.4tu.nl, and
Nikhef. Researchers use it to deposit, publish and
cite datasets, software and other research output.
It covers the full life cycle of a deposit: institutional login, metadata and file collection, review, DOI and Handle registration, and serving the published record over the web and an API. State is kept as RDF in a SPARQL 1.1 store. Another institution can run its own instance: branding, menus, identity provider and storage back-ends are all configuration.
Documentation
The documentation source lives in docs/ and is published to
djehuty.4tu.nl. The site is assembled from three parts:
- the MkDocs documentation, written as Markdown in
docs/; - the API reference, a static OpenAPI reference generated from the route
definitions in
src/djehuty/api/andsrc/djehuty/application.py; - the community site, rendered with Quarto from the
sources in
community/.
| Page | What it covers |
|---|---|
| Configuring and running djehuty | Every configuration option |
| Deployment | Deploying with Helm, containers or the Python package |
| Knowledge graph | The RDF data model |
| Contributing | Development workflow and a tour of the source code |
| API | The HTTP API |
Building the documentation
The site is built with MkDocs using the
Material theme. You need
uv and
just; the Python dependencies come
from the docs group in pyproject.toml and are installed automatically. To
build the community site you also need Quarto CLI.
The API reference and the community site are generated into docs/ before
MkDocs runs, so that MkDocs copies them into the final site. To preview all
three parts while you write, run these in order:
just openapi
just docs-community
just docs-md-serve
That serves the site at http://localhost:8000 and rebuilds whenever a file under
docs/ changes. The API reference and the community site are not regenerated by
live reload: after changing an endpoint or a file under community/, re-run
just openapi or just docs-community respectively.
If you are only editing the Markdown pages, just docs-md-serve on its own is
enough.
To build the complete static site into site/:
just openapi
just docs-community
just docs-md
Remove the build output again with just docs-clean.
Editing the docs is a pull request like any other — the pages are Markdown, so a
typo fix can be made straight from the GitHub web interface. On merge to main,
the docs workflow builds the API reference and
the community site, rebuilds the MkDocs site and publishes all three to GitHub
Pages, so there is no manual publishing step.
Installing and running
Djehuty needs a SPARQL 1.1 endpoint such as Virtuoso OSE or Jena Fuseki to store its state.
See the deployment guide for the three supported ways to deploy it (Helm chart, container image, or Python package) along with what a production configuration requires and how to upgrade.
Contributing
Contributions are welcome — code, documentation, bug reports and ideas alike. CONTRIBUTING.md covers how to set up a development environment, run the test suite, and the conventions we follow for branches, commits and pull requests.
Community
The djehuty Community is a place for users and contributors to connect, share ideas and help shape the future of djehuty. Join the monthly Community Hours to meet other users and contributors and discuss recent developments and upcoming work.
Security
To report a vulnerability, please see SECURITY.md.
License
djehuty is distributed under the GNU Affero General Public License v3.0 or
later. See LICENSE.
Contact information
- General: info@djehuty.4tu.nl
- Maintainers: a.e.wilczynska@tudelft.nl, g.kuhn@tudelft.nl, k.f.deAraujo@tudelft.nl
- Security issues: security@djehuty.4tu.nl
2 maintainers
Metadata
2 maintainers
Release files for djehuty 26.8.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| djehuty-26.8.2.tar.gz | 3.8 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| djehuty-26.8.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.9 MB
Release files / djehuty-26.8.2.tar.gz
| Download URL | djehuty-26.8.2.tar.gz |
|---|---|
| Size | 3.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a64d5fd35f97f1cdad793223bdc23037599ef4a563160eac737cde52248e1f6
|
|
BLAKE2b-256 checksum How to use checksums |
f3cc660674f393bfd24061079f0ffe59aeb1626fe334c5ebff3e7db4bf663f19
|
| 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 Oct 21, 2026.
Transparency logRelease files / djehuty-26.8.2-py3-none-any.whl
| Download URL | djehuty-26.8.2-py3-none-any.whl |
|---|---|
| Size | 4.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94c0bdbcbe3116bd5a6baa4a8823164d6d065ed9d1249ae086c9033f7fb3e210
|
|
BLAKE2b-256 checksum How to use checksums |
ef2e8ae314095c5fb8145472b46aeaed984219706e320e65181f14e862d6b0ad
|
| 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 Oct 21, 2026.
Transparency logSecurity for djehuty 26.8.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for djehuty-26.8.2.tar.gz
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 Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
