Briefwechsel — Fill the Empty Rows

Five approaches. The first four change the /briefwechsel row itself; the fifth puts insights where they belong — on the person detail page.

Page/briefwechsel  ·  /persons/[id]
BriefRows feel sparse — ~60% of row width is empty

The situation

On /briefwechsel?senderId=… (e.g. 851 letters for Walter de Gruyter), each row shows only title, date, location and counterpart — leaving the right half empty. The question is: what belongs there?

The five specs answer differently. Specs 1–4 rework the row itself. Spec 5 argues the archive-level view (top correspondents, activity, tag cloud) belongs on /persons/[id], not here — and mocks the dashboard that lives there instead.

Data we can use today

  • Title / Filename
  • Document date
  • Location
  • Sender / receivers
  • Summary text
  • Tags
  • Archive box & folder
  • PDF thumbnail open issue

Removed from earlier drafts: status lifecycle (will be dropped from the product) and script type (only set after OCR, unreliable).

Concepts that rework /briefwechsel Specs 1–4
01
Demo leserlicher Brief
31. Mai 1940 · Belgard
„letzte Lebenstage…"
Dörpfeld
VII · 5
W-0397 – 2. Sep 1923
B.Lichterfelde · H. Cram
„von Elsbeth…"
Verlag
VI · 7
W-0521 – 24. Dez 1922
Berlin · W. Dieckmann
„Weihnachtsbrief…"
Weihn.
V · 3

Rich Rows

Pack summary, tags and archive box into each row. No images, no structural change. Fastest to ship.

ScanningSmall effort
02
Demo leserlicher Brief„letzte Lebenstage von W. Dörpfeld…"← Gertrud · Belgard31. Mai 1940
W-0397 – 2. Sep 1923„von Elsbeth geschriebener Kommentar…"→ H. Cram · B.Lichterfelde2. Sep 1923
W-0521 – 24. Dez 1922„Weihnachtsbrief, Bitte um Bild…"→ W. Dieckmann · Berlin24. Dez 1922

Thumbnail Rows

PDF preview on the left anchors each row. Summary (when filled) becomes the readable context line.

RecognitionNeeds thumbnails
03
Demo Brief
W-0397
W-0396
W-0524
W-0523
W-03972. Sep 1923
B.Lichterfelde
→ H. Cram

„von Elsbeth…"

Master-Detail Split

Compact list left, sticky preview right. Click a row → thumbnail, metadata, summary, excerpt. Browse without losing context.

Reading flowMobile pattern needed
04
Demo Brief
W-0397 · 2 Sep
W-0396 · 2 Sep
W-0524 · 31 Jul
W-0523 · 12 Mai
W-0522 · 7 Mär

Gallery Cards

Abandon the list for a 4-column grid. Thumbnail-first, family-album feel. Biggest visual change.

BrowsingPoor date-scanning
The archive-level view moves to /persons/[id] Spec 5 · separate page
05
WG
Walter de Gruyter
1862–1923
Korrespondenz-Überblick ↗ Briefwechsel
851
gesamt
612
239
42J
Jahre
W. Dieckmann184H. Cram143E. Dieckmann88
VerlagFamilieWeihn.KurReise

Person Dashboard (/persons/[id])

The /briefwechsel list stays calm and reading-focused; the archive-level view — activity over years, top correspondents, top locations, tag cloud — lives on the person detail page, where it's useful every time you open a person, not only during letter review.

Every correspondent, location, tag and year on the dashboard links into /briefwechsel with pre-filled filters, so the dashboard is the discovery surface and /briefwechsel is the reading surface.

DiscoveryWorks for bilateral too (always scoped to the person)Needs aggregation endpoints
ConceptBest for user who wants to…Visual changeNew backendEffortMobile
1 · Rich RowsScan quickly, see summary + tags on every letterRow height 2× currentNoneSmallRight column collapses
2 · Thumbnail RowsRecognise letters visually, pick up where they left offThumbnail on the leftPDF thumbnail service (open issue)MediumFine
3 · Master-DetailFlip through letters in a reading sessionTwo-column splitNone mandatoryMediumDrawer / sheet needed
4 · Gallery CardsBrowse the collection as an albumFull structural change (list → grid)PDF thumbnail serviceLargeGrid reflows 4 → 2
5 · Person DashboardUnderstand a person's correspondence at a glanceNew section on /persons/[id]Aggregation endpoints (per-year, per-correspondent, per-location, per-tag)MediumStacks naturally
Proposed path forward:
  1. Ship Spec 1 (Rich Rows) now — it uses data we already have and tests whether "empty rows" is really the problem, or whether it's "not enough context to decide which letter to open".
  2. Build Spec 5 (Person Dashboard) next — it's independent of /briefwechsel and turns the person page into a real archive overview.
  3. Upgrade to Spec 2 (Thumbnail Rows) once the thumbnail service lands — it layers cleanly on top of Spec 1 without throwing work away.
Specs 3 and 4 remain on the table but are bigger re-architectures — revisit after watching how users behave with 1 + 5 + 2.