marcel/familienarchiv
1
0
Fork 0
Code Issues 119 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

feat(search): NL search — modern German + EN/ES translation rendering #741

New Issue
Closed
opened 2026-06-06 12:16:47 +02:00 by marcel · 0 comments
marcel commented 2026-06-06 12:16:47 +02:00
Owner
Copy Link

Part of epic #735. Post-v1. Depends on the NL search v1 backend being live (Ollama infrastructure exists).

Goal

One tap on a letter turns the 1910s-German transcription into readable modern German (and optionally EN/ES) rendered alongside the original. The single biggest unlock for the younger reader persona (phones, don't read Kurrent or archaic German).

Scope

  • New endpoint or action on the document detail page: "Übersetzen / Translate"
  • Ollama (same instance as NL search) generates the modern-German rendering from the transcription text
  • Result stored as a new artifact alongside the transcription (not regenerated on every view)
  • EN/ES rendering optional — same pipeline, different prompt
  • Permission model: any authenticated user can trigger translation; output is cached per document

Open questions before implementation

  • Storage: new document_translations table (locale + content + generated_at) or extend Document entity?
  • Who can trigger/re-trigger translation? Any user or WRITE_ALL only?
  • Show original + translation side-by-side, or toggle?
Part of epic #735. Post-v1. Depends on the NL search v1 backend being live (Ollama infrastructure exists). ## Goal One tap on a letter turns the 1910s-German transcription into readable modern German (and optionally EN/ES) rendered alongside the original. The single biggest unlock for the younger reader persona (phones, don't read Kurrent or archaic German). ## Scope - New endpoint or action on the document detail page: "Übersetzen / Translate" - Ollama (same instance as NL search) generates the modern-German rendering from the transcription text - Result stored as a new artifact alongside the transcription (not regenerated on every view) - EN/ES rendering optional — same pipeline, different prompt - Permission model: any authenticated user can trigger translation; output is cached per document ## Open questions before implementation - Storage: new `document_translations` table (locale + content + generated_at) or extend `Document` entity? - Who can trigger/re-trigger translation? Any user or WRITE_ALL only? - Show original + translation side-by-side, or toggle?
marcel added this to the Archive Intelligence — NL Search milestone 2026-06-06 12:16:47 +02:00
marcel added the P3-laterfeature labels 2026-06-06 12:19:03 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-critical
Blocks a core user journey, causes data loss, or is a security/accessibility barrier. Work on this before P1+.
 P1-high
Significant friction on a main user journey; workaround exists but is non-obvious. Next up after P0.
 P2-medium
Noticeable improvement; doesn't block anything; schedule opportunistically.
 P3-later
Cosmetic or parking-lot work; fine to stay open indefinitely.
 audit
Read-only audit / assessment work; produces a report rather than changing code
 bug
Something isn't working
 cleanup
Removal of dead code, vague comments, naming violations, and scratch artifacts
 collaboration
We want to extend the family archive to have more collaboration tools
 conversation
descoped
We will do that later
 devops
documentation
README, ARCHITECTURE, GLOSSARY, CONTRIBUTING, per-domain docs
 epic
Marker for epic-level issues that group multiple child issues
 feature
file-upload
legibility
Codebase Legibility Refactor — preparing the codebase for human evaluation and bus-factor reduction
 needs-discussion
Has an open decision or design question that must be resolved before implementation can start.
 notification
person
phase-1: security
Security hygiene — must be done first
 phase-2: container-images
Production-ready multi-stage Docker images
 phase-3: prod-compose
Production compose overlay + Caddy reverse proxy
 phase-4: spring-prod-profile
Spring Boot production configuration profile
 phase-5: backups
Database and object storage backup strategy
 phase-6: deployment-docs
.env.example, DEPLOYMENT.md, runbook
 phase-7: monitoring
Prometheus, Loki, Grafana, Alertmanager
 refactor
Code restructuring without behaviour change
 security
test
ui
UI/UX and accessibility issues
 user
No Label P3-later feature
Milestone
No items
No Milestone Archive Intelligence — NL Search
Projects
Clear projects
No project
Assignees
Clear assignees
Jens marcel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: marcel/familienarchiv#741
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?