MEx model
JSON schema files defining the MEx metadata model.
Project
The Metadata Exchange (MEx) project is committed to improve the retrieval of RKI research data and projects. How? By focusing on metadata: instead of providing the actual research data directly, the MEx metadata catalog captures descriptive information about research data and activities. On this basis, we want to make the data FAIR1 so that it can be shared with others.
Via MEx, metadata will be made findable, accessible and shareable, as well as available for further research. The goal is to get an overview of what research data is available, understand its context, and know what needs to be considered for subsequent use.
RKI cooperated with D4L data4life gGmbH for a pilot phase where the vision of a FAIR metadata catalog was explored and concepts and prototypes were developed. The partnership has ended with the successful conclusion of the pilot phase.
After an internal launch, the metadata will also be made publicly available and thus be available to external researchers as well as the interested (professional) public to find research data from the RKI.
For further details, please consult our project page.
Contact
For more information, please feel free to email us at mex@rki.de.
Publisher
Robert Koch-Institut
Nordufer 20
13353 Berlin
Germany
Package
Our metadata model is represented as JSON schema in mex/model. There, we defined 1.
entities, described by their properties, 2. fields, small objects, that are used as
$ref for certain properties, 3. an extension, which contains additional properties,
that are not in scope of the JSON schema definition, 4. i18n files, that hold
translations of the properties and are to be used in the context of user interfaces and
5. vocabularies, which are used in context of the entities. A more detailed
description of the model's context can be found in /docs/index.rst.
License
This package is licensed under the MIT license. All other software components of the MEx project are open-sourced under the same license as well.
Development
Installation
- install python on your system
- on unix, run
make install - on windows, run
.\mex.bat install
Linting and testing
- run all linters with
make lintor.\mex.bat lint - run unit and integration tests with
make testor.\mex.bat test - run just the unit tests with
make unitor.\mex.bat unit
Updating dependencies
- update boilerplate files with
cruft update - update global requirements in
requirements.txtmanually - update git hooks with
pre-commit autoupdate - update package dependencies using
uv sync --upgrade - update github actions in
.github/workflows/*.ymlmanually
Creating release
- run
mex release RULEto release a new version where RULE determines which part of the version to update and is one ofmajor,minor,patch.
Python release verification
Python release artifacts (source distributions and wheels) published to GitHub Releases are signed keyless using sigstore.
To verify a release artifact manually, download the artifact (e.g. mex_model-<tag>-py3-none-any.whl) and its Sigstore bundle (mex_model-<tag>-py3-none-any.whl.sigstore.json), then run either:
Using sigstore:
sigstore verify identity \
--bundle <path-to-bundle> \
--cert-identity "https://github.com/robert-koch-institut/mex-model/.github/workflows/release.yml@refs/heads/main" \
--cert-oidc-issuer "https://token.actions.githubusercontent.com" \
<path-to-artifact>
Using cosign:
cosign verify-blob \
--bundle <path-to-bundle> \
--certificate-identity "https://github.com/robert-koch-institut/mex-model/.github/workflows/release.yml@refs/heads/main" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
<path-to-artifact>
-
FAIR is referencing the so-called FAIR data principles – guidelines to make data Findable, Accessible, Interoperable and Reusable. ↩
Metadata
Release files for mex-model 5.2.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 | Provenance | |
|---|---|---|---|---|
| mex_model-5.2.1.tar.gz | 69.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mex_model-5.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 183.7 kB
Release files / mex_model-5.2.1.tar.gz
| Download URL | mex_model-5.2.1.tar.gz |
|---|---|
| Size | 69.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a1047c73ee59ce96a79f26447ff9684671312c1ff97cae757220c0651f78a08
|
|
BLAKE2b-256 checksum How to use checksums |
5fff37e4000caf2f756711352305f3a693b171e72ab4d615c9d58f301b7609c1
|
| 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 20, 2026.
Transparency logRelease files / mex_model-5.2.1-py3-none-any.whl
| Download URL | mex_model-5.2.1-py3-none-any.whl |
|---|---|
| Size | 113.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2752f0ce4f605a4c4172dd0def6e30ffe55d85965a279559fbdb1251b27235b6
|
|
BLAKE2b-256 checksum How to use checksums |
c1bb825b806540e9e1176ec298b82d5c16dbf34b387e44b9e50e8f826ec1f0bf
|
| 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 20, 2026.
Transparency logSecurity for mex-model 5.2.1
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 mex_model-5.2.1.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 20, 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.
