1 ADR 0034 place label language selection
Forgejo Actions edited this page 2026-09-25 16:38:07 +00:00

ADR 0034: Place Label Language Selection

Status: accepted Date: 2026-05-22

Context

ADR 0029 allows the Super Admin to import selected GeoNames alternate-name languages. Reverse place lookup and automatic album titles need deterministic language/name selection. Memories is a household product: one instance may contain users with different UI languages, media from multiple countries, and place providers with local names, alternate names, and provider defaults.

Automatic album suggestions are owner-private before acceptance. Once a suggestion is accepted, the album title becomes user-visible curation and should not silently relocalize depending on viewer language or later provider data changes.

Options Considered

Option Summary Benefits Costs / Risks
A. Always provider default/local name Use GeoNames/default/local place name Stable and simple May not match owner language preference
B. Always UI language Pick label matching current viewer UI language Familiar per viewer Accepted album titles could vary by viewer; confusing provenance
C. Owner-preferred language for generated suggestions Owner-private generated suggestions choose owner preference, then household/default/provider/local fallbacks; accepted title freezes as string Stable curation; respects owner; inspectable Requires language preference/provenance fields
D. Store multilingual generated titles Keep multiple title variants and choose per viewer Flexible Over-engineering; title identity becomes ambiguous

Decision

Use owner-preferred language selection with frozen accepted titles.

For generated place labels and automatic album suggestion titles:

  1. The lookup/title request records a language preference chain.
  2. Owner-private automatic album suggestions use the media owner's preferred language/locale first, if configured and imported.
  3. Then fall back to household/server default language, if configured and imported.
  4. Then fall back to provider local/default name.
  5. Then fall back to any imported alternate name that Core can mark as a fallback.
  6. Then use a generated fallback label.

Every selected label records selectedLanguage, nameVariantSource, and provider/source provenance.

Accepted album titles are stored as explicit strings and do not silently relocalize per viewer, provider update, or UI language change. If the owner wants a different language later, they edit/regenerate/accept a title refresh explicitly.

Shared/collaborative albums inherit the title string selected or edited by the album owner/admin. Viewer-local translations may be a future presentation feature, but they must not replace the stored album title or provenance.

Consequences

Positive

  • Keeps accepted album titles stable and understandable.
  • Respects owner preference for owner-private suggestions.
  • Avoids per-viewer title ambiguity in family albums.
  • Makes imported alternate-name languages useful without requiring all languages.

Negative / Costs

  • Requires language preference chain and selected-name provenance.
  • If the desired language was not imported, titles fall back rather than magically translating.
  • Multi-user households may see album titles in the album owner's chosen language.

Revisit Triggers

Revisit this decision if:

  • Viewer-local title translation becomes a product priority.
  • Users expect accepted collaborative albums to have per-viewer localized display names.
  • Imported alternate-name quality is poor enough that provider local/default names are usually better.
  • Memories introduces household-level language policy beyond individual profile locale.