[Docs] Public-sector integration landscape catalogue #215

Closed
opened 2026-07-07 21:15:52 +02:00 by zemion · 1 comment
Owner

Build a structured catalogue of commonly used public-sector software, platforms, protocols, and integration patterns. GovOPlaN should connect and improve processes rather than assume replacement.

Source: docs/GOVERNMENT_OPERATIONS_VISION.md

Acceptance criteria:

  • catalogue covers citizen portals, DMS/e-file, ERP/finance, identity, groupware, mail/calendar, payment, archive, reporting/BI, and public-sector protocols
  • each entry records protocol/API surface, auth model, data shape, deployment assumptions, risks, and MVP test path
  • catalogue ranks connector candidates and points to owning module repos
  • native module decisions are explicit when connector-first is insufficient
Build a structured catalogue of commonly used public-sector software, platforms, protocols, and integration patterns. GovOPlaN should connect and improve processes rather than assume replacement. Source: `docs/GOVERNMENT_OPERATIONS_VISION.md` Acceptance criteria: - catalogue covers citizen portals, DMS/e-file, ERP/finance, identity, groupware, mail/calendar, payment, archive, reporting/BI, and public-sector protocols - each entry records protocol/API surface, auth model, data shape, deployment assumptions, risks, and MVP test path - catalogue ranks connector candidates and points to owning module repos - native module decisions are explicit when connector-first is insufficient
zemion added the
module/core
label 2026-07-07 23:41:03 +02:00
zemion added the
priority
p2
status
triage
labels 2026-07-08 02:10:45 +02:00
Author
Owner

Resolved by the integration landscape catalogue pass.

  • Expanded docs/PUBLIC_SECTOR_INTEGRATION_STRATEGY.md with concrete landscape entries for citizen portals, DMS/e-file/archive, ERP/finance/procurement, identity/IAM, groupware/mail/calendar/collaboration, payment, reporting/BI/publication, public-sector protocols/registries, file providers, project/task systems, and specialist Fachverfahren.
  • Each entry records strategy, protocol/API surface, auth model, data shape, deployment assumptions, risks, MVP test path, owner, and priority.
  • Updated docs/GOVOPLAN_MODULE_ROADMAP.md and synced the managed core wiki pages.

Executable connector implementation remains routed to owning module repositories, especially govoplan-connectors.

Resolved by the integration landscape catalogue pass. - Expanded `docs/PUBLIC_SECTOR_INTEGRATION_STRATEGY.md` with concrete landscape entries for citizen portals, DMS/e-file/archive, ERP/finance/procurement, identity/IAM, groupware/mail/calendar/collaboration, payment, reporting/BI/publication, public-sector protocols/registries, file providers, project/task systems, and specialist Fachverfahren. - Each entry records strategy, protocol/API surface, auth model, data shape, deployment assumptions, risks, MVP test path, owner, and priority. - Updated `docs/GOVOPLAN_MODULE_ROADMAP.md` and synced the managed core wiki pages. Executable connector implementation remains routed to owning module repositories, especially `govoplan-connectors`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: add-ideas/govoplan-core#215
No description provided.