https://portal.odissei.nl/

https://doi.org/10.5281/zenodo.15236529.

Technical Wiki https://github.com/odissei-data/.github/wiki

List of repositories for each application stack.

The ODISSEI Portal runs on three environments: Production, Staging, and Devstack.

To run the Portal, two dockerized application stacks, are required:

• Dataverse portal stack: uses a SOLR, Postgres, and Payara containers.

• Skosmos stack: uses a Skosmos, Fuseki, and Varnish container.

• Traefik container: used as reversed proxy. It uses Letsencrypt for automatic SSL certificate renewal. It also shows an overview of the Prefect server and labs-demo server that run the Workflow Orchestrator and microservices used by the Orchestrator respectively.

The Workflow Orchestrator is used to automatically ingest metadata from the different data providers**,** present in the ODISSEI Portal. The ingestion-workflow-orchestrator application stack is behind the Workflow Orchestrator, using Prefect and Postgres DB to coordinate the actions of metadata ingestion and enrichment microservices for Orchestrator

List of servers and their roles:

This server is used to host the production ODISSEI Portal (https://portal.odissei.nl) and Skosmos vocabulary browser (https://skosmos.odissei.nl). It is setup with a traefik reverse proxy. This server runs in Microsoft Azure and can only be accessed by DANS personnel.

This server is used to host the staging ODISSEI Portal (https://portal.staging.odissei.nl) and Skosmos vocabulary browser (https://skosmos.staging.odissei.nl). This server runs in Microsoft Azure and can only be accessed by DANS personnel.

This server is used by ODISSEI developers for testing and experimentation. It host the staging ODISSEI Portal (https://portal.devstack.odissei.nl) and Skosmos vocabulary browser (https://skosmos.devstack.odissei.nl). To access this server, a user needs to be added to the ODISSEI collaboration on SURF Research Cloud as a developer. They can then add their public ssh key to their profile and will gain automatic access to the server using ssh with their username.

This server hosts the Prefect workflow orchestrator. The orchestrator is used to automatically ingest dataset metadata. For each data provider there is an associated Prefect workflow, dedicated to ingesting their datasets' metadata onto the ODISSEI Portal (Dataverse instance). Common metadata tasks - harvesting, mapping, and enrichment - have been encapsulated in microservices that are run separately from the orchestrator. The orchestrator schedules its workflows to run daily to keep the metadata in the portal up to date. This server runs in Microsoft Azure and can only be accessed by DANS personnel.

The metadata in the production ODISSEI Portal is kept up-to-date by the workflow orchestrator running on https://prefect.dansdemo.nl. The metadata in the staging and devstack ODISSEI Portal is only updated manually, which can be done via the orchestrator on https://prefect.dansdemo.nl or a local orchestrator setup.

This server hosts the metadata microservices. These microservices are all containerized and deployed via a CI/CD setup, which tests the code, creates and pushes a new docker image when a GitHub tag is created. This server runs in Microsoft Azure and can only be accessed by DANS personnel.

• Networking:

  • Traefik container with automatic SSL certificate renewal using letsencrypt.

• Monitoring: ODISSEI production portal website is monitored in zabbix.

• Logging: No centralized logging. docker logs {container name}

• Database Backups: Cronjob that makes backups every day. Kept on server itself.