Analysts keep asking which datasets leadership trusts for official reporting. How should the catalog communicate that trust status?
Select an answer to reveal the explanation.
Short Explanation
A certified badge on a dataset is like the health grade in a restaurant window—you know what is cleared for public use. Put that trust status in the catalog as governed metadata. Rumors and blanket auto-badges on raw dumps do not help.
Full Explanation
Trust for official reporting should be an explicit catalog signal, not hallway rumor. Publishing a governed certified or trusted badge as catalog metadata on approved datasets tells analysts which sources leadership and stewards endorse for civic reporting. Relying on rumors about which tables the CIO likes this month is unstable and unfair to new staff. Certifying every raw landing-zone file automatically on ingest with no review dilutes the badge into meaninglessness. Hiding trust status forces guessing and recreates shadow inventories. Exam focus: certification as governed metadata. Caveat: certification needs criteria, periodic revalidation, and revocation when quality or ownership slips—static forever-badges become lies. Operationally, define certification rules for official reporting datasets, apply badges only after review, display them prominently in search results, and audit that reported council metrics resolve only to certified sources. Revalidate certified badges on a fixed cadence and revoke promptly when ownership or quality evidence expires so official-reporting trust stays earned. Certification criteria should be written plainly enough that analysts understand why a dataset earned the badge and what would cause revocation after a quality or ownership failure.