issue #128 repoints the dashboard analytics off dj_sets onto the staff_weekly_assignments_log…

activeFuzzy match

Source: inline_markerConfidence: 53%Staleness: 1.00Created: 7/17/2026

This decision may be stale — affected files have changed significantly since it was recorded.

Context

Found in clubfinder-backend/migrations/archive/109_staff_weekly_assignments_log_analytics_index.sql:4

Decision

issue #128 repoints the dashboard analytics off dj_sets onto the staff_weekly_assignments_log archive: R4a (completed-set count), R4c (no-show count), R5 (dj_club_history cron) all scan the log filtered by (club_id, status='complete', archived_at range). staff_weekly_assignments_log was created in migration 096 as a bare LIKE copy

Governance scope

Link this decision to the modules and files it governs.

Modules(1)

clubfinder-backend

Files(2)

clubfinder-backend/migrations/archive/109_staff_weekly_assignments_log_analytics_index.sqlclubfinder-backend/migrations/archive/109_staff_weekly_assignments_log_analytics_index.sql::__module__

All linkage saved.

Since this decision

Recent commits to this repo Hotspots & churn in affected areas

Deprecate marks this decision as no longer current — existing references remain, but it stops being treated as the standard. It doesn't change any code.