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?
Select an answer to reveal the explanation.
Short Explanation
A code crosswalk is the bilingual dictionary for systems that changed dialects. Publish the legacy-to-new status mapping as findable reference metadata so every report translates the same way. Personal invented maps guarantee mismatched counts.
Full Explanation
Migrations require published code crosswalks as reference metadata so consumers and integrators interpret legacy values consistently against the new code list. Without a shared crosswalk, each team invents incompatible translations and corrupts comparisons. Hiding legacy semantics or shipping without documentation increases cutover risk. Findable, governed crosswalks are a standard metadata deliverable during modernization.