Case studies.

The enquiry view composes the list and report entry point. It uses permission checks to decide which interface sections to show.

The enquiry hook tracks cached results, loading and refresh states, and errors. It requests comprehensive data and date-based breakdowns from the API.

The server mounts the enquiry router under /api/enquiries. The comprehensive-data endpoint assembles the data used by the enquiry view.

The enquiry router runs session validation before handling requests. The shared middleware attaches the authenticated user and session. For example, the student route applies a separate IT role check to registration and progression writes.

Mongoose defines user records, including student fields and references to class records. The enquiry router uses queries and aggregation pipelines to turn stored records into filtered summaries.

The enquiry report is behind a reporting permission in the client. Its report view fetches filtered records and offers PDF and spreadsheet exports.