Project Atlas AetherDev project hub
Atlas project production

BOUSD-MonthlyAttendance-Dashboard

Provide district and site leaders with a role-aware Google Workspace dashboard for attendance and chronic absenteeism visibility, with source freshness dependent on upstream extract jobs.

Internal-only entry. Do not publish externally without review.
Type
System
Lifecycle
Active
Last touched
2026-03-26
Visibility
Internal

Purpose

Give district and site leaders a shared attendance and chronic absenteeism interface backed by controlled Google Workspace reporting surfaces.

Current state

The dashboard is active and production-facing as the attendance presentation layer (Apps Script + Google Sheets + optional Google Sites). Upstream extract evidence now clearly shows scheduled tab overwrites from `BOUSD-MonthlyAttendance-Extract` on the primary Linux automation host (`sal-01.bousd.us`), while the dashboard itself runs in Google-hosted Apps Script context. The dashboard repo README manual SQL run + paste + cache-clear checklist is now treated as legacy fallback/reference guidance, not the normal refresh path.

Next step

Complete the [MonthlyAttendance Fallback Runbook Scaffold](../monthlyattendance-fallback-runbook-scaffold/) and keep role assignments aligned in the [Owner, Escalation, and Fallback Matrix](../owner-escalation-and-fallback-matrix/) for technical operator, business sign-off owner, fallback operator, and escalation owner.

Interfaces

Inputs
  • SourceData-year-byschool
  • SourceData-year-bygrade
  • user-mapping and role-filter tabs
Outputs
  • browser charts and tables
  • role-scoped attendance views
  • Google Sites embeds where used

Reality to Action trace

Reality Ingestion

Contributes in this stage.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Aeries-derived source tabs are canonical for the dashboard data shown in Google Workspace.
  • The dashboard is the presentation layer, not the authoring system for attendance metrics.

Safe handling

  • Restrict sheet access and Apps Script deployments to approved staff.
  • Treat attendance exports and dashboard views as FERPA-restricted.
  • Avoid exposing dashboard URLs or sheet IDs outside internal district documentation.

Operational notes

Reliability posture

Dashboard responses are on demand once source tabs are available. The biggest operational risk is stale or mismatched source data rather than browser rendering itself.

Observability

  • Apps Script execution logs
  • cache invalidation helpers such as clearDashboardCache()
  • visible stale-data symptoms in dashboard views

Security and privacy

Attendance and chronic absenteeism data are restricted student records. Sheet access, Apps Script deployment, and Google Sites embedding should stay limited to approved district audiences.

Dependencies

Upstream
  • BOUSD-MonthlyAttendance-Extract
  • sheet header stability
  • Apps Script deployment
Downstream
  • attendance review workflows
  • leadership decision support

Ownership

Owners

Technology Services, Josh Barton

Users

Educational Services, site leadership, Technology Services

BOUSD-MonthlyAttendance-Dashboard

Operational Notes

  • This remains the leadership-facing attendance and chronic absenteeism interface. Apps Script shapes chart payloads from the SourceData-year-byschool and SourceData-year-bygrade tabs and serves role-scoped views for district and site leaders.
  • Current runtime / active path: Apps Script renders on demand, while source freshness depends on upstream BOUSD-MonthlyAttendance-Extract jobs within the broader Aeries-to-Google Sheets Reporting Extract Family.
  • Scheduler / operator model: dashboard presentation is on-demand (Google runtime), while refresh cadence and operator controls live upstream in the Aeries-to-Google Sheets reporting extract family running via Linux cron on sal-01.bousd.us.
  • Dashboard README manual refresh checklist (run SQL, paste to SourceData-*, clear cache) is now classified as legacy fallback/reference, while automated weekday scheduler paths remain primary.
  • Operational warning: dashboard availability does not by itself guarantee source freshness when upstream feed jobs are delayed and fallback execution/escalation responsibilities are unclear.
  • Governance note: role ownership for fallback and escalation is tracked in the Owner, Escalation, and Fallback Matrix and the MonthlyAttendance Fallback Runbook Scaffold.
  • This page now belongs more explicitly to the Perpetual Data Reports Portal operating model because it is a recurring report product with freshness, ownership, and access expectations.

Registry Alignment

  • Mapped registry entry: INT-003.
  • Registry clarified: this is the leadership-facing attendance and chronic absenteeism interface, while the extract layer is a separately important production dependency with documented weekday cadence.
  • Validation gaps: manual SQL/paste is now classified as fallback-only; unresolved trigger/executor/approval/escalation fields are tracked in the MonthlyAttendance Fallback Runbook Scaffold and Owner, Escalation, and Fallback Matrix, along with source-tab IDs and Google Sites embedding scope.