Treat Metadata as a Contract

Metadata fields need semantics, not just labels A field label like "type" or "audience" feels obvious until three teams use it differently. The fix is to define the field as if another system must read it without context. What does it describe? Who sets it? Which values are allowed? When can it change? Dublin Core thinking keeps metadata practical. You do not need every possible field; you need enough shared description for people and machines to identify, relate, govern, and retrieve content. Strong CMS metadata has a controlled vocabulary where consistency matters, free text only where interpretation is acceptable, and…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in