[Feature] Define govoplan-datasources module #188

Closed
opened 2026-07-06 20:26:24 +02:00 by zemion · 2 comments
Owner

Imported from the GovOPlaN module and integration planning discussion.

Durable context: Gitea wiki page Repo-docs-GOVOPLAN-MODULE-ROADMAP in govoplan-core.

Define a module for data source registration and governance.

Candidate sources:

  • databases
  • CSV files
  • uploaded files
  • external APIs
  • RSS/Atom feeds
  • public-sector registers

Clarify source metadata, credentials, refresh policy, provenance, and tenant boundaries.

<!-- codex-module-roadmap:datasources-module --> Imported from the GovOPlaN module and integration planning discussion. Durable context: Gitea wiki page `Repo-docs-GOVOPLAN-MODULE-ROADMAP` in `govoplan-core`. Define a module for data source registration and governance. Candidate sources: - databases - CSV files - uploaded files - external APIs - RSS/Atom feeds - public-sector registers Clarify source metadata, credentials, refresh policy, provenance, and tenant boundaries.
zemion added this to the GovOPlaN Module Roadmap milestone 2026-07-06 20:26:24 +02:00
Author
Owner

Boundary decision for the first slice: do not create a separate govoplan-datasources repository yet. Implement provider-neutral tabular source discovery and preview in Connectors via GovOPlaN/govoplan-connectors#9; Dataflow stores stable source references, not credentials. Reassess this issue after at least two source providers and one repeated governance contract expose a boundary that no longer fits Connectors.

Boundary decision for the first slice: do not create a separate `govoplan-datasources` repository yet. Implement provider-neutral tabular source discovery and preview in Connectors via https://git.add-ideas.de/GovOPlaN/govoplan-connectors/issues/9; Dataflow stores stable source references, not credentials. Reassess this issue after at least two source providers and one repeated governance contract expose a boundary that no longer fits Connectors. <!-- codex-datasource-boundary-decision-2026-07-28 -->
Author
Owner

Codex State: done

Implemented the two-layer architecture and initialized
GovOPlaN/govoplan-datasources.

  • Core contracts: 8b1910b
  • Datasources module: 1cb6228
  • Connectors origin adapter: 27302f0
  • Dataflow consumer: 6ca3058
  • Meta architecture/release wiring: 163b35c
  • Follow-up epic: GovOPlaN/govoplan-datasources#1

The original decision and module-definition scope is complete. Provider
expansion and lifecycle hardening remain in the linked child issues.

## Codex State: done Implemented the two-layer architecture and initialized `GovOPlaN/govoplan-datasources`. - Core contracts: `8b1910b` - Datasources module: `1cb6228` - Connectors origin adapter: `27302f0` - Dataflow consumer: `6ca3058` - Meta architecture/release wiring: `163b35c` - Follow-up epic: https://git.add-ideas.de/GovOPlaN/govoplan-datasources/issues/1 The original decision and module-definition scope is complete. Provider expansion and lifecycle hardening remain in the linked child issues.
zemion added the
type
feature
priority
p1
module/datasources
area/module-system
labels 2026-07-28 12:54:04 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-core#188
No description provided.