Official metric definitions appear in Confluence, SharePoint, and the data catalog with slightly different wording. What glossary practice should leadership enforce?
Select an answer to reveal the explanation.
Short Explanation
Three glossaries with three wordings is like three different street signs for the same corner. Pick one governed system of record and make the other sites link to it. Duplicate definitions invite quiet forks.
Full Explanation
Official metric definitions scattered across Confluence, SharePoint, and the data catalog with slightly different wording create competing truths. Leadership should designate one governed system of record for official definitions and point other sites to it so municipal reporting shares one meaning. Encouraging every team to keep a favorite copy keeps debates lively and metrics wrong. Deleting the catalog to keep only informal wiki pages without owners worsens stewardship. Freezing all definitions forever even when law and policy change prevents necessary evolution. Exam theme: single system of record for glossary semantics. Caveat: mirrors and excerpts are acceptable if they clearly defer to the system of record and sync or link rather than fork. Operationally, pick the glossary platform as system of record, replace divergent wiki text with links, communicate the rule to BI teams, and periodically crawl for duplicate definition pages that have drifted. Crawl collaboration sites for duplicate “official definition” pages monthly and convert forks into links back to the glossary system of record. Communicate the system-of-record rule in BI and open-data working groups so authors stop pasting divergent “official” wording into project wikis out of habit.