Skip to main content

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.

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 preview while you write, with live reload on every save:

just docs-md-serve

That serves the site at http://localhost:8000 and rebuilds whenever a file under docs/ changes.

To build the static site into site/:

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 rebuilds the site and publishes it 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.

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

Metadata

Release files for djehuty 26.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for djehuty 26.7
File Size Uploaded Provenance
djehuty-26.7.tar.gz 3.8 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for djehuty 26.7
File Interpreter ABI Platform
djehuty-26.7-py3-none-any.whl Python 3 none any Details

Total release size: 7.8 MB

Release files / djehuty-26.7.tar.gz

Download URL djehuty-26.7.tar.gz
Size 3.8 MB
Tags Source
SHA-256 checksum
How to use checksums
a7f2ea6a87bcc63bd6e7c4711e86eaebc48092c3327f09e27a053c612bb0c874
BLAKE2b-256 checksum
How to use checksums
cb84606a7b0bb68523cd7858b909c1e22f8f9b102821933f59fe72aa360d9864
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 30, 2026.

Transparency log

Release files / djehuty-26.7-py3-none-any.whl

Download URL djehuty-26.7-py3-none-any.whl
Size 4.0 MB
Tags Python 3
SHA-256 checksum
How to use checksums
757ddaddca9b10b4142cb51aa4a6140e6780de7025f96747bd1921ad23d658f0
BLAKE2b-256 checksum
How to use checksums
15a47f39b538751452546736cbaff7394d8794c6ffadc3e0e077a1f9ef53bc5c
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 30, 2026.

Transparency log

Security for djehuty 26.7

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.

Select from 2 files

Attestation for djehuty-26.7.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 Sep 30, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release

26.7 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page