[Feature] Add DMS/eAkte connector #2

Open
opened 2026-07-10 22:09:13 +02:00 by zemion · 2 comments
Owner

Moved from add-ideas/govoplan-core#128.

Reason: DMS/eAkte connector work belongs to the DMS module.

Original issue body:

Imported from a backlog-like text file.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
  • Line: 333
  • Source kind: product
  • Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform

Imported item:

Add DMS/eAkte connector.
Moved from add-ideas/govoplan-core#128. Reason: DMS/eAkte connector work belongs to the DMS module. Original issue body: <!-- codex-generic-backlog-fingerprint:77a09ba2718b1e69cf5df077 --> Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `333` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform` Imported item: ```text Add DMS/eAkte connector. ```
Author
Owner

The DMS module boundary is documented, but the first interoperable eAkte target remains a product/environment choice.

Decisions required:

  • first archive/DMS product and protocol/profile (recommend a standards-based adapter where the selected target supports one);
  • exact eAkte/record hierarchy and metadata mapping, filing authority, version/finality semantics, legal hold/retention ownership, and correction/withdrawal behavior;
  • synchronous acknowledgement versus queued handoff and treatment of outcome-unknown effects.

Manual inputs required:

  • vendor/interface documentation, sandbox endpoint, credentials/certificates, approved metadata and sample package fixtures, retention/hold rules, and expected receipt/error evidence.

Coordinate this choice with Records #7 so DMS owns collaborative document lifecycle, Records owns eAkte filing/chronology, and the adapter is tested once rather than duplicated.

The DMS module boundary is documented, but the first interoperable eAkte target remains a product/environment choice. Decisions required: - first archive/DMS product and protocol/profile (recommend a standards-based adapter where the selected target supports one); - exact eAkte/record hierarchy and metadata mapping, filing authority, version/finality semantics, legal hold/retention ownership, and correction/withdrawal behavior; - synchronous acknowledgement versus queued handoff and treatment of outcome-unknown effects. Manual inputs required: - vendor/interface documentation, sandbox endpoint, credentials/certificates, approved metadata and sample package fixtures, retention/hold rules, and expected receipt/error evidence. Coordinate this choice with Records #7 so DMS owns collaborative document lifecycle, Records owns eAkte filing/chronology, and the adapter is tested once rather than duplicated.
zemion added
status
needs-info
and removed
status
triage
labels 2026-08-21 14:20:50 +02:00
Author
Owner

Implementation update 2026-08-23: d.velop d3 DMS is selected as the first real product. Release v0.1.19 (commit 7c689b6) adds a concrete DMSApp profile, repository/object-definition preflight, safe bearer-authenticated HTTP transport, Origin handling, and a digest-bound store-plan builder. The capability stays deliberately unhealthy/unavailable until a real target proves mapping, custody, correlation/reconciliation and recovery. Remaining target inputs: base endpoint, repository ID, Origin, source category/source ID, mapping revision, credential envelope, sandbox/OpenAPI access, and the institution's custody/receipt semantics. This broad feature remains open until that target evidence exists.

Implementation update 2026-08-23: d.velop d3 DMS is selected as the first real product. Release v0.1.19 (commit 7c689b6) adds a concrete DMSApp profile, repository/object-definition preflight, safe bearer-authenticated HTTP transport, Origin handling, and a digest-bound store-plan builder. The capability stays deliberately unhealthy/unavailable until a real target proves mapping, custody, correlation/reconciliation and recovery. Remaining target inputs: base endpoint, repository ID, Origin, source category/source ID, mapping revision, credential envelope, sandbox/OpenAPI access, and the institution's custody/receipt semantics. This broad feature remains open until that target evidence exists.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-dms#2