ehoandClaude Opus 5
12f17d9d73
Two backlog trees are complete: `docs/project/backlog/` (75 files, every WP done) and `docs/project/refactor-backlog-setup/` (the arc before it). Move both under `docs/project/archive/` with `git mv`, so history stays intact through `git log --follow`. `SHOWCASE-ROADMAP.md` moves with them, because it points at the now-archived backlog README. Add `docs/project/archive/README.md`. It states that these trees are historical and names the two directories that are still live. Repoint every inbound reference named in RD-30's Files table: CLAUDE.md, the root README, both backend READMEs, `LetterHtml.cs`, `a11y.mdx`, the `document-feature` and `new-ssp` skills, and the readable-codebase PLAN, README, and RD-19 ticket. Fix two upward-relative links inside the moved WP files (WP-68, WP-69) that gained a directory level and would otherwise break. Repoint `.prettierignore`'s two agent-prompt exclusions to their new path, so prettier keeps leaving those files' exact wording alone. Mark RD-30 done and check off its acceptance criteria; flip its README row to done. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
53 lines
1.8 KiB
Markdown
53 lines
1.8 KiB
Markdown
# WP-51 — OpenZaak Documenten (DRC) upload + link
|
|
|
|
Status: done (5807937)
|
|
Phase: 9 — OpenZaak / ZGW integration
|
|
|
|
## Why
|
|
|
|
Uploaded documents currently persist as bytes in local SQLite (`DocumentStore`). To be
|
|
production-ready they must live in OpenZaak's **Documenten API (DRC)** as
|
|
`enkelvoudiginformatieobjecten`, linked to a Zaak via `zaakinformatieobject` — behind the same
|
|
config gate, still without a FE contract change.
|
|
|
|
## Read first
|
|
|
|
- [openzaak-integration.md](../reference/openzaak-integration.md)
|
|
- WP-49 (the seam pattern), WP-50 (create-zaak, the zaak to link to)
|
|
|
|
## Decisions (pre-made, don't relitigate)
|
|
|
|
- Introduce an `IDocumentSource` sibling of `IZaakSource`; local impl = `DocumentStore`,
|
|
OpenZaak impl = DRC. FE upload DTOs unchanged.
|
|
- A document needs an `informatieobjecttype` **URL** from Catalogi (like zaaktype for a zaak).
|
|
- Upload → returns document URL → `zaakinformatieobject` links it to the zaak URL.
|
|
|
|
## Files
|
|
|
|
- `Data/IDocumentSource.cs`, `Data/LocalDocumentSource.cs`, `Zgw/OpenZaakDocumentSource.cs`
|
|
- `ZgwOptions`: `informatieobjecttype` URL(s) + `DrcBaseUrl`.
|
|
|
|
## Steps
|
|
|
|
1. Abstract the upload/read/link paths behind `IDocumentSource`.
|
|
2. OpenZaak impl: POST `enkelvoudiginformatieobjecten` (content), then POST `zaakinformatieobjecten`.
|
|
3. Map DRC document metadata back into the existing document DTOs.
|
|
|
|
## Acceptance criteria
|
|
|
|
- [ ] With `Zgw:Enabled=true`, an upload lands in DRC and is linked to its zaak.
|
|
- [ ] FE upload/list DTOs unchanged; no api-client drift.
|
|
- [ ] Tests cover the DRC POST bodies + the zaak-link step (stub handler).
|
|
|
|
## Verification
|
|
|
|
`dotnet test`; against a docker OpenZaak if available.
|
|
|
|
## Out of scope
|
|
|
|
Notificaties (WP-52), content virus-scanning / blob-storage tuning.
|
|
|
|
## Risks
|
|
|
|
Large file content over base64/multipart — mind memory; stream if needed.
|