Build a HESA Student return
Turn audited data into a submission-ready HESA Student packet.
By the end you’ll be able to
- Run the HESA Student pipeline over the demo data.
- Read the sign-off report and resolve a blocking violation.
- Recognise the seven HESA Data Futures streams and which one is Student.
A return is a regulator-shaped packet built from your canonical data. DataBridge supports the seven HESA Data Futures streams — Student, Provider, Staff, EMR, GOS, AOS, Finance — plus the UK portal returns (TEF, KEF, SLC SBR, UCAS HEI) and the AU TCSI streams (see `docs/RETURNS_COMPLETENESS.md` for the full matrix).
Student is the largest workstream. The pipeline (`@databridge/hesa-df-pipeline`) takes the canonical Student-stream rows you ingested and repaired, runs every Quality Rule that guards the stream, builds the XML/JSON envelope, and produces a sign-off report: every violation, every warning, every clear pass.
A return is submittable when every structural blocker (CRITICAL/ERROR) clears. Warnings can ship with a documented reason; the sign-off report shows that exception trail. The HESA console surfaces this state so you can see, at a glance, whether you can send today.
In demo mode the Student pipeline runs over the seeded demo institution. You'll open the HESA console, drill into the Student stream, and read the sign-off report — the same artefact a real registrar would review before approving submission.
Walkthrough
- Open HESA
1.Open the HESA console
See the seven Data Futures streams for the demo institution and which ones are submittable.
- Open Student
2.Drill into the Student stream
Open the Student stream to see its pipeline output: row counts, rule pass/fail breakdown, and the sign-off report.
- Back to Data quality
3.Inspect a blocker
If a structural blocker remains, the sign-off report names it and links back to the finding so you can repair and re-run.
Your turn
Open the HESA console and find the Student stream's current sign-off state.
Hint: Use the 'Open HESA' step above.