Metadata Management

CIMP · 50 questions

• A new analyst cannot tell which field means "active permit" across five city systems. What should the information-management team prioritize first?
• A permitting director asks what "active" means for a license, while a DBA asks which tables and ETL jobs store that status. Which distinction should the metadata lead draw?
• A council dashboard for water-main breaks looks fine, but analysts do not know when it last refreshed or how many rows loaded. What metadata category fills that gap?
• Before a bond presentation, leadership asks which source systems feed the "water main breaks" KPI. Which metadata practice answers that origin question?
• A municipal data catalog was populated last year, but many entries are stale and unused. What is the most likely missing practice?
• A city wants models for permitting: business concepts first, then normalized attributes and keys, then tables and indexes. Which sequencing of model levels is correct?
• Parks and Public Works both publish conflicting glossary definitions for "asset." Catalog searches return both and confuse staff. What should happen next?
• An auto-harvested catalog lists tables and columns for housing data but lacks owners, business tags, and plain-language descriptions. What should the team add?
• IT plans to change values in a shared municipal code table used by many applications. What should precede the change?
• A civic analytics team wants to explore how people, parcels, and permits connect for investigation—not only query one table at a time. At awareness depth, what approach highlights those relationships?
• A catalog audit finds missing owners, empty descriptions, and broken lineage links. How should the team treat this finding?
• Security wants consistent handling of sensitive resident fields discovered in the catalog. Which metadata practice best enables that?
• Before designing database tables for a civic asset register, what modeling step should come first?
• After years of production hotfixes, the physical permitting schema no longer matches the approved logical model. What does this signal?
• Analysts abandon the catalog because they must guess technical table names. What design change most improves adoption?
• Lineage shows source-to-target tables for a finance extract, but transformation logic is undocumented. What is the primary risk?
• A modern metadata platform can notify stewards when a production schema changes unexpectedly. What capability is that demonstrating?
• Staff still search for "occupancy" while the official term is now "vacancy status," and an old synonym remains unmarked. What should stewards do in the glossary?
• Profiling shows high null rates on a "parcel owner contact" field. Where should that fitness signal appear for consumers?
• A data product for emergency shelter occupancy promises hourly refresh and 99% uptime. Where should those consumer expectations be registered?
• Vendors are pitching catalog platforms before the city has named metadata use cases or owners. What sequencing should the program follow?
• Housing systems disagree on what "vacancy status" means, blocking shared reporting. What metadata-and-modeling response is most appropriate?
• Technical metadata harvest is noisy because tables and columns follow inconsistent naming across departments. What hygiene practice helps most?
• Business stewards need to edit glossary definitions, while engineers maintain harvested schema docs. How should edit rights be set?
• A regulatory report requires proving which source columns feed each disclosed figure. Table-level lineage alone is available today. What should the team conclude about granularity?
• A city analytics onboarding checklist teaches new analysts SQL but never shows the data catalog or business glossary. What metadata-literacy step should the information management lead add?
• A municipal catalog lists dozens of warehouse tables with no owner, no description, and no recent queries. What remediation approach best curates these orphans?
• A housing authority keeps critical eligibility business rules only in long email threads between analysts. How should those rules become visible metadata?
• Two departments independently redefine the shared entity Citizen differently in local models. What lightweight governance practice should prevent semantic forks?
• A county open-data portal publishes datasets with vague titles, empty descriptions, and no stated update frequency. What metadata quality concern should the portal owner prioritize?
• Analysts routinely export warehouse extracts that accidentally include Social Security numbers. Which metadata-driven control best reduces that exposure risk?
• After a policy change, the city’s official definition of unemployed no longer matches last year’s meaning, but longitudinal dashboards still use one unversioned glossary entry. What should metadata management do?
• An automated scanner flags hundreds of columns as possible PII and writes tags straight into enforcement without human review. What practice should the metadata program require instead?
• A director claims the metadata program is complete because every major system has an entity-relationship diagram on a shared drive. What gap should the CIMP practitioner highlight?
• Analysts keep asking which datasets leadership trusts for official reporting. How should the catalog communicate that trust status?
• Integration teams map dozens of source fields into canonical citizen attributes, but the mappings live only in a developer’s private notes. What should metadata management require?
• On-call staff triage stale civic dashboards by guessing which upstream jobs failed. How should runbooks use the catalog?
• Official metric definitions appear in Confluence, SharePoint, and the data catalog with slightly different wording. What glossary practice should leadership enforce?
• Glossary entries for citizen attributes list only a one-line synonym and no allowed values or owner contact. What minimum content should stewards require?
• A warehouse team will retire a legacy permits table in ninety days, but consumers still discover it as if it were fully supported. What catalog action should accompany the technical deprecation?
• During a permitting-system migration, legacy status codes must map to a new code list, but analysts cannot find any published translation. What reference metadata should the program provide?
• Data stewards are flooded with requests to fix typos in catalog descriptions while semantic definition changes wait weeks. How should change control be tiered?
• A metrics store defines active household differently from the business glossary by a few quiet edge cases. What alignment action should metadata management take?
• A regional partnership will receive a weekly civic dataset, but the package includes only raw files and no definitions or refresh expectations. What should accompany the share?
• Product teams expose GraphQL and REST APIs whose field names never link back to glossary business terms. What metadata practice should close that gap?
• Catalog search logs show repeated zero-result queries for phrases residents use, while official titles use different jargon. How should the team improve metadata?
• Regulators ask the city to prove what a reported KPI meant and which sources fed it on a specific past quarter. What metadata capability is required?
• Several BI teams rebuild their own versions of Date and Geography dimensions with conflicting hierarchies. What modeling-plus-metadata practice should the enterprise adopt?
• A new catalog crawler is configured with production database passwords stored in its admin UI and broad access to export connection secrets. What protection principle should stop that design?
• Leadership asks how to judge whether the metadata program is delivering value beyond counting cataloged tables. Which outcome metric best fits that ask?