Dataspace Publish
Category: Integration
Node id: dataspace-publish
Standards: IDSA-DSP, GAIA-X, GDPR
Register this pipeline's output as an IDS/GAIA-X dataspace asset so external consumers can discover and pull it via the Dataspace Protocol (DSP)
What it does
- IDS Dataspace Protocol (DSP) asset registration
- Idempotent — skips creation if the asset already exists
- Auto-derives asset ID from pipeline ID when not configured
- Supports GAIA-X and IDSA data sovereignty contracts
Use cases
- Expose a clinical pipeline's FHIR output to partner organisations via the dataspace
- Register a real-time wearables pipeline as a dataspace product for research consumers
- Publish anonymized patient cohort data to a health data space
Runtime
- Performance tier:
medium
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
data | any | No | Pipeline data to publish (passed through to output unchanged) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
asset_id | text | No | Dataspace asset ID assigned to this pipeline |
catalog_url | text | No | URL of the asset in the dataspace catalog |
pipeline_id | text | No | Hydra pipeline ID linked to the asset |
registered | boolean | No | True if the asset was newly created, false if it already existed |
success | boolean | No | Whether registration succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Dataspace Service URL | dataspace_url | string | Yes | Base URL of the TietAI dataspace connector (e.g. https://dataspace.tiet.ai) | ||
| Asset Name | asset_name | string | Yes | Human-readable name for this data asset in the dataspace catalog | ||
| Asset Description | description | string | No | Description of the data asset for catalog consumers |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Dataspace API Key | api_key | secret | No | Management API key for the dataspace service |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Asset ID | asset_id | string | No | Custom asset ID (leave blank to auto-generate from pipeline ID as 'hydra-<pipeline_id>') | ||
| Pipeline ID | pipeline_id | string | No | Hydra pipeline ID whose outputs are exposed (auto-detected from execution context if blank) | ||
| Content Type | content_type | string | No | application/json | MIME type of the pipeline output (default: application/json) |
Errors
| Code | Description |
|---|---|
MISSING_DATASPACE_URL | dataspace_url config field is empty |
MISSING_ASSET_NAME | asset_name config field is empty |
MISSING_PIPELINE_ID | pipeline_id not in config and not available from execution context |
ASSET_CREATE_FAILED | Dataspace management API returned an error when creating the asset |
Runtime notes
- The node registers the pipeline as a dataspace asset; consumers pull the latest completed execution via DSP
- Running the node multiple times is safe — if the asset already exists it returns the existing asset_id without error
- pipeline_id is auto-detected from execution context; set it explicitly if running outside a normal pipeline execution
- The dataspace service must be reachable from the Hydra platform network at the configured dataspace_url
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..