Story: Dataset bundles and provisioning
Table of Contents
This page documents a story in Sprint 10. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Make spin up a fresh ORE Studio a one-click experience. Split the schema so catalog metadata can exist before provisioning; introduce bundles; build the wizard.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 10 |
| Now | Completed 2026-01-27. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2026-01-27 |
Acceptance
- metadata vs production schema split lands cleanly.
- Bundles defined with members + audit trail + lifecycle functions.
- System Provisioner Wizard guides the user end-to-end.
- Bootstrap mode atomic via
create_initial_admin_request.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Separate catalog metadata schema from production data | DONE | 2026-05-19 | 2026-01-27 | Split the monolithic ores schema into metadata (dq_*, change_control) and production (refdata_*, iam_*, assets_*, geo_*, variability_*, telemetry_*); schema-qualified references; ER generator updated; data-flow documented (unidirectional metadata → production). |
| Add dataset bundles | DONE | 2026-05-19 | 2026-01-27 | dq_dataset_bundles_tbl + bundle_members + bundle_publications audit; PL/pgSQL: dq_list_bundles_fn, dq_list_bundle_datasets_fn, dq_preview_bundle_publication_fn, dq_populate_bundle_fn, dq_get_bundle_publication_history_fn; seed solvaris / base / crypto bundles. |
| Add System Provisioner Wizard to Qt | DONE | 2026-05-19 | 2026-01-27 | Multi-page wizard: admin account, foundation bundle, data-governance bundle, data-catalogues bundle, provisioning execution; replaces the shell-only bootstrap; localhost-only create_initial_admin_request atomically creates admin + exits bootstrap mode. |
Decisions
- Schema split, not separate database
- lighter operational footprint and the data flow remains unidirectional.
- Layer-aligned wizard pages
- matches how the population scripts are layered after the schema-polish work.
- Localhost-only bootstrap endpoint
- lets the wizard work over the network without exposing a remote-bootstrap attack surface.
Out of scope
- Multi-tenant provisioning — single-tenant first.
- Migrate between bundle sets in the same database.
See also
- Schema polish — the layer cleanup the wizard consumes.