Clerks enter free-text company names that mix legal names, trade names, and noise tokens, so organization matching fails. What should MDM implement first for reliable matching?
Select an answer to reveal the explanation.
Short Explanation
Matching messy company names without cleanup is like comparing apples labeled “Granny,” “Granny Smith LLC,” and “GSMITH.” Parse, standardize, and strip noise first—then match.
Full Explanation
When clerks enter free-text company names mixing legal names, trade names, and noise tokens, MDM should first implement parsing and standardization that normalize legal versus trade names and strip noise tokens before matching. Clean inputs raise civic organization-match quality. Deleting all organization records that lack a stock-ticker symbol fails public-sector reality where most vendors are not ticker-listed. Forcing clerks to memorize ISO country codes instead of cleaning names fails the actual defect. Storing company names only as raw binary blobs fails search, match, and stewardship. Exam caveat: parse/standardize organization names before match—noise token handling is part of MDM prep. Operational check: define legal-vs-trade parsing rules, strip noise (Inc, LLC punctuation variants), measure match lift on a labeled sample, and train clerks on entry standards. Keep the standardization map in the municipal MDM configuration library for reuse across domains. Keep verification evidence with the municipal runbook so audits can prove the chosen control was applied as designed and that rejected alternatives would have left city services exposed to the failure modes described above.