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?
Select an answer to reveal the explanation.
Short Explanation
Field mappings stuck in private notes are like subway transfers written only on one rider’s napkin. Publish governed source-to-canonical mappings so integrators and stewards share one interoperability map. Expiring chats and tribal memory break the next release.
Full Explanation
Interoperability depends on maintained mappings from source fields to canonical attributes as governed metadata. Documented mappings combine technical detail with business meaning and support onboarding, impact analysis, and consistent integration. Private notes, ephemeral chat, or abandoning canonical attributes recreate semantic drift. A shared mapping inventory is a standard metadata deliverable for integration programs.