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

Cleanup path for confirmed persons that have no usable name #685

New Issue
Open
opened 2026-05-27 19:58:59 +02:00 by marcel · 0 comments
marcel commented 2026-05-27 19:58:59 +02:00
Owner
Copy Link

Context

Follow-up flagged in the review of PR #679 (Phase 5 persons directory, #667) — Elicit (requirements).

The triage flow lets a transcriber confirm a provisional person (clears provisional). But a person can end up confirmed (provisional = false) yet have no usable name — e.g. a literal "?", an empty/whitespace name, or an UNKNOWN-type placeholder that was confirmed by mistake. Once confirmed, it drops out of the "Needs review" triage list (which filters provisional = true), so there is no surface to find or clean these up — they linger in the directory with a placeholder avatar and no name.

Suggested approach

  • Provide a way to surface confirmed-but-unnamed persons — e.g. a filter/section ("Unnamed") or a small admin report — so they can be renamed, merged, or deleted.
  • Decide the intended semantics: should confirming a person require a non-empty name (prevent the state), or should it be allowed and cleaned up after (detect the state)? Pick one.

Out of scope / notes

  • Surfaced in #679's review; not in scope for that PR. Small data-quality follow-up to the persons directory / triage UI.
## Context Follow-up flagged in the review of PR #679 (Phase 5 persons directory, #667) — Elicit (requirements). The triage flow lets a transcriber **confirm** a provisional person (clears `provisional`). But a person can end up **confirmed (`provisional = false`) yet have no usable name** — e.g. a literal "?", an empty/whitespace name, or an `UNKNOWN`-type placeholder that was confirmed by mistake. Once confirmed, it drops out of the "Needs review" triage list (which filters `provisional = true`), so there is **no surface to find or clean these up** — they linger in the directory with a placeholder avatar and no name. ## Suggested approach - Provide a way to surface confirmed-but-unnamed persons — e.g. a filter/section ("Unnamed") or a small admin report — so they can be renamed, merged, or deleted. - Decide the intended semantics: should confirming a person require a non-empty name (prevent the state), or should it be allowed and cleaned up after (detect the state)? Pick one. ## Out of scope / notes - Surfaced in #679's review; not in scope for that PR. Small data-quality follow-up to the persons directory / triage UI.
marcel added the P3-laterfeature labels 2026-05-27 20:12:40 +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
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#685
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?