You’re exploring the full DataBridge platform free, with synthetic Future Horizons University data. Everything is unlocked; actions run in your demo session (in-session only, not saved to a real backend).

FHU Databridge
Enterprise
Pricing
Analyst & Compliance
9 min

Repair findings (F03 domicile & ethnicity)

Apply a guided repair to a real finding and watch it clear.

By the end you’ll be able to

  • Apply a guided repair to an F03 domicile or ethnicity finding.
  • Re-run the audit and confirm the finding clears.
  • Recognise that every repair is logged in the tamper-evident audit log.

Audits find problems; repairs fix them. DataBridge ships guided repair recipes for the rules in the F03 family — domicile and ethnicity codes against the published HESA codesets — because those are the highest-volume class of finding on a typical Student return.

A guided repair is not a magic button. It's a structured, reviewable change: the recipe shows you the offending source value, the rule it broke, the candidate corrected value (often via a HESA-published crosswalk), and the citation for the crosswalk. You approve, and the canonical model gets the corrected value; the source system is left untouched (the repair is recorded on the canonical projection, not pushed upstream).

Every repair is appended to the tamper-evident audit log (`@databridge/audit-log`) — actor, action `rule.repair`, target finding-id, before/after values. The hash chain means a regulator can verify, months later, that the repair you signed off on is the repair the return was built from.

In demo mode the repair queue is pre-seeded with F03 candidates; you'll open it, apply one, and re-run the audit to see the finding clear. The audit log entry is real (it's appended to the in-memory chain).

Walkthrough

  1. 1.Open the data-quality console for the Student entity

    F03 findings live under Student. Open the entity view so you see the candidate repairs.

    Open Data quality

  2. 2.Apply a guided repair

    Pick a single F03 domicile or ethnicity finding and accept the suggested crosswalk. The before/after values are shown side-by-side with the citation.

    Apply repair

  3. 3.Re-run the audit and confirm the finding clears

    Return to the Audit Engine, re-run, and check the finding count for F03 drops.

    Open Audits

Your turn

Open the Data Quality console and review the F03 repair queue for the Student entity.

Hint: Use the 'Open Data quality' step above.

Knowledge check

1.Where does a guided F03 repair apply the corrected value?
2.Why is every repair appended to the audit log?

Complete this lesson