FAC-WEB parent: dean analytics dashboard

[y4nder]

Summary

Track the work required to deliver the dean analytics dashboard across the Faculytics frontend.

This issue serves as the parent tracking issue for the analytics dashboard initiative. The original issue was too large to implement as a single ticket, so the work has been split into dedicated sub-issues.

Goal

Deliver the analytics dashboard experience for dean and other institutional stakeholders using the backend analytics endpoints for:

• department overview
• attention-based review
• longitudinal trends
• faculty report drill-down
• inline analysis pipeline triggers

Parent Scope

This issue is complete when:

• the analytics feature slice and route foundation are in place
• the department overview experience is implemented
• the attention and trends views are implemented
• faculty report drill-down is accessible from the analytics flow
• inline pipeline trigger UX is implemented where applicable

Implementation Order

Recommended execution order based on current dependencies:

1. foundation setup
2. dean analytics UI foundation
3. department overview
4. attention and trends views
5. faculty report drill-down
6. inline pipeline trigger UX

Notes

Sub-issues are attached in dependency order so the parent issue can be used as the source of truth for rollout planning.

#55 is now the practical UI foundation for the dean analytics rollout.
Remaining child issues should extend the route and screen structure established in #55, rather than reintroducing the earlier dashboard structure.

[y4nder]

@ayacoders mao ni ron akong giimplement pa diay, for reference ni when getting analytics

[ayacoders]

Noted 🤘

[ayacoders]

Alignment Update

#55 is now the active UI baseline for the dean analytics experience.

The current implementation work has established the primary UX direction by:

• removing the faculty analysis table from /dean/dashboard
• using /dean/faculties as the main dean analytics listing entry point
• expanding /dean/faculties/[facultySlug]/analysis as the dedicated faculty analysis route

Because of that, the remaining analytics work under this parent issue should build on top of #55 rather than trying to reintroduce the previous dashboard structure.

Planning impact

The child issues under #18 should now be interpreted as follow-up implementation work on top of the #55 UI foundation:

• #33 should wire the overview/dashboard experience to the real analytics backend while preserving the new UX direction
• #38 should implement the backend-driven faculty report/detail experience using the dedicated analysis route established in #55
• #34, #35, and #36 should integrate into the current dean analytics flow and route structure rather than assuming the earlier mock layout

Important note

#55 does not complete the backend-backed acceptance criteria of the analytics child issues yet. It should be treated as the UI foundation for the remaining work.