Expose source mappings in the UI (entity tab + per-source list) #47

Closed
opened 2026-07-22 14:22:59 +02:00 by thecrealm · 0 comments
Owner

Curators currently have no way to see source mappings (§2.5): they are written on reconciliation apply (§11.4.3) and re-targeted on merge (§5.4), but no API route or page lists them. The only indirect signal is the 'Zuordnung' match label on reconciliation candidates.

Scope (read-only visibility, Curator-gated per §1.5 — source keys are source-layer data):

  • Entity detail: a 'Quellen-Zuordnungen' tab/section listing (source, source key, created/updated) for the entity.
  • Ingestion dashboard (§11.3.4): per-source mapping list (source key → entity), searchable by key.
  • Server: read endpoints for both views; mappings stay Curator-visible, never public (§1.5).

Acceptance:

  • After applying a reconciliation candidate, the mapping appears on both surfaces.
  • After a merge, the mapping shows the survivor (§5.4).
  • Anonymous/consumer requests to the endpoints fail closed (§4.4).

Out of scope (would need a spec change to §2.5/§11.4 first): breaking/editing a mapping. If wanted, raise separately.

Curators currently have no way to see source mappings (§2.5): they are written on reconciliation apply (§11.4.3) and re-targeted on merge (§5.4), but no API route or page lists them. The only indirect signal is the 'Zuordnung' match label on reconciliation candidates. Scope (read-only visibility, Curator-gated per §1.5 — source keys are source-layer data): - Entity detail: a 'Quellen-Zuordnungen' tab/section listing (source, source key, created/updated) for the entity. - Ingestion dashboard (§11.3.4): per-source mapping list (source key → entity), searchable by key. - Server: read endpoints for both views; mappings stay Curator-visible, never public (§1.5). Acceptance: - After applying a reconciliation candidate, the mapping appears on both surfaces. - After a merge, the mapping shows the survivor (§5.4). - Anonymous/consumer requests to the endpoints fail closed (§4.4). Out of scope (would need a spec change to §2.5/§11.4 first): breaking/editing a mapping. If wanted, raise separately.
thecrealm added
now
and removed
next
labels 2026-07-22 14:27:19 +02:00
Sign in to join this conversation.
No labels
M0
M1
M2
M3
M4
M5
blocked
next
now
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/mokuroku#47
No description provided.