One question seems to come up time and time again, is what should you expect from a meta data vendor? By definition, the meta data vendor is one that sells an application or services that enable you to effectively implement your meta data strategy. What should you expect, desire and border-line demand from the vendor community. Some of these items are pet peeves while others truly should be delivered with any application purchase.

Let’s start with the obvious; the meta-model. At some abstract level, the repository is just another database application. Data comes in, is stored and integrated with other applications. Why wouldn’t we expect the meta data meta-model to be the first database loaded? Perhaps this is too logical. We bring repository applications into the organization for many reasons: archiving knowledge of our technical community, expressing relationships between objects and providing conceptual understanding with model abstractions. Did someone make the decision that these benefits are not a good thing for the meta data team? It seems to me that if we are going to purchase an application for the user community to assemble structures, define semantic meaning and understand the logical definition of data then the meta data team should also gain these benefits.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access