Components Overview
The RDMC Prototype is organized into 13 components
(see Architectural Terminology) plus the
RDMC_Proto configuration package. Each component has a clear, focused
responsibility. This page gives developers a quick overview of what each
component does and where to look when making changes. For the full structural
reference (layers, directory layout, connection mechanisms), see
Project Structure.
rdmc — the core component of the project. It acts as the central hub that controls and coordinates the container lifecycle.
Managing the container lifecycle (create, update, seal, delete)
Managing artifact files and folder structures (
upload_helpers/)The creation-wizard views and step logic (
helpers/step_configs.py)The main dashboard and container explorer views
Feature-flag lookup (
features.py)
rdmc_metadata — the metadata and manifest engine.
Validating container and artifact metadata
Generating and updating the
manifest.rdmcfileProducing the RO-Crate JSON-LD representation
rdmc_configuration — configures the RDMC workflow.
Storing named configurations and their feature settings
The feature registry that controls which features and options participants see in the workflow
Assigning roles (Chair, Co-Chair, Committee Member, Advisory Board)
Sending, revoking, and resolving collaboration invitations
Configuration list, create, edit, share, and preview views
rdmc_auth — authentication against AcademicCloud.
OIDC login, session handling, token backends
Optional sub-services on top of the core container functionality:
rdmc_publish — publishing sealed containers: Zenodo OAuth2 authorization and upload, Dataverse and Coscine workflows, publish status per container, ePIC PID updates on publication.
rdmc_sign — stateless sealing and signing: SHA-256 hashing and Sigstore certificates (no models, no views).
artifact_evaluation — review rubrics, reviewer assignments, and the generated Artifact Evaluation PDF.
metabase — semantic annotation via reverse-proxy endpoints.
search_portal — outbound client that registers published containers with the NFDI Search Portal (single module
rdmc_search.py).ree_service — the Reusable Execution Environment (REE) workbench wizard step and client for the external REE service (see REE Service): fills component slots, runs export/build/validation jobs, and saves job results back into the container.
viewer — read-only container viewer (
rdmc_viewer) with role-based display filtering (owner/reviewer/public) and the file tree explorer. Holds no business logic and no models of its own.rdmc_management — organizer access gate, admin panel enhancements, question uploads, and database backup exports.
The creation-wizard UI itself lives in rdmc (see Core & Business).
rdmc_workflow_api — the REST API used to create and manage RDMC containers programmatically (see RDMC API).
Initializing empty containers and uploading resources to them
Adding metadata and sealing containers (including PID generation)
Creating complete containers in a single composite request
Listing, retrieving, and deleting a user’s containers
Health check endpoint, OpenAPI schema, and Swagger UI