Download external terminologies from the Terminology Service
For background information about the Terminology Service, see the Terminology Service section.
The DCC distributes External terminologies via (i) the Terminology Service in the BioMedIT portal and (ii) a standalone Terminology Server based on MinIO. The first option is intended to be used by researchers; the second one by BioMedIT nodes and data providers. The following document shows how to download these external terminologies in each distribution.
Downloading external terminologies from the BioMedIT portal
After logging in to the BioMedIT portal https://terminology.dcc.sib.swiss/ with
your SWITCH edu-ID account, you will see a table with the available external
terminologies (see Figure 1). Click on the terminology you want to download to expand the entry.
You will be presented with a list of available versions including buttons for
the available file formats (
RDF/TTL). Clicking on the
button will download the terminology file.
Figure 1. Terminology Service in the BioMedIT Portal. The content of the ICD-10-GM classification has been expanded, showing some of the available versions that can be downloaded.
Downloading external terminologies from the Terminology Server
You have requested a user account for the Terminology Server at email@example.com.
You have accepted the “Acceptable use policy for the Terminology Service”.
Download via the web interface
After logging in at https://terminology-server.dcc.sib.swiss/ with your
credentials, you will be presented with the MinIO Browser. It will show two
folders (see Figure 2):
current/, which has the most recent release of the external
archive/, which has all previous releases.
Figure 2. Current and archive folders in the Terminology Server.
After navigating into one of the folders, you will be presented with a list
of available packages. A package bundles all available external terminologies
and consists of a
.zip and a
.gpg file (for instance,
.zip holds all the terminology files while the
.gpg file is a
detached gpg signature that allows to verify that the
.zip file has been
created by the DCC.
Select all relevant files and download them by clicking
Download all as zip button appearing on the top of the screen.
After the download is complete, you can unzip the downloaded file and optionally verify the signatures of the packages.
Verify the signature
Verifying a package’s gpg signature is automatically done if using the
terminology-server-downloader (see below). To manually verify the
signature, download the “DCC Terminology Server” public gpg key from the
DCC keyserver by running
$ gpg --keyserver hkp://keyserver.dcc.sib.swiss:80 --recv-keys 8D33EAABB425ADF27A713B7E8BAC7A01F395B738
To verify a signature, run
gpg --verify, for instance:
$ gpg --verify ontologies-2021-10-22_18-53-51.gpg ontologies-2021-10-22_18-53-51.zip
gpg: Signature made Fr 22 Okt 20:54:08 2021 CEST
gpg: using RSA key 8D33EAABB425ADF27A713B7E8BAC7A01F395B738
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 9AE9 CCC5 964D 88B2 79DB 94AD 337F 6741 B6CC 05DE
Subkey fingerprint: 8D33 EAAB B425 ADF2 7A71 3B7E 8BAC 7A01 F395 B738
The output below indicates that the file has been signed by the DCC.
An output that includes
gpg: BAD signature from "DCC Terminology Server <firstname.lastname@example.org>" [unknown]
indicates that the integrity of the data cannot be verified and that the data should not be used.
Finally, unzip the
ontologies-*.zip file to access the terminology files.
Download via the command-line interface
terminology-server-downloader, accessible in
can be used to download terminologies from
the Terminology Server via a command-line interface.
After installing this Python tool via
pip and providing the credentials to
the Terminology Server via environmental variables, all or a selected set of
ontologies can be downloaded with a single command without further user
$ terminology-server-downloader ~/data
This process can further be automatized by invoking the command regularly from
For further information, see the