Notes from Gavilan Metadata Workshop
Gavilan MetaData Solutions Workshop - October 8-9, 2007
Attending from NSHE - Lynne Personius, Ray Buehne, Paul Landrum
These notes were created as the result of a group discussion to identify the main justifications for a data dictionary, what features is must have, and what challenges are faced in implementing one.
Skip to: Top Issues , Key Features /Evaluation Criteria, Key Benefits/ ROI Arguments, or
Implementation Guidelines - "Enablers" versus "Barriers" to a Successful Implementation
Top Issues
- BI reports: where does data come from ?
- impact analysis / where-used reporting
- consistency of definitions and calculations
- "wide source" of information across company
- want to easily navigate/search and narrow down results
- "when" is data available ?
- naming standards
- business definitions vs. technical definitions
- system/data migration
- data quality
- inconsistent business rules
- standardization of common information assets
- governance
- wiki / workflow
- support for semi/unstructured data
- how does vendor validate "truth" of findings ? Back to top
Key Features / Evaluation Criteria
- extensible, customizable, adaptable
- Google-like search
- affordability
- ease of implementation
- 80/20 metadata harvesting support
- easy to maintain and manage
- easy to use
- broad list of harvesting utilities
- easy, open import/export
- easy update/synchronization of metadata definitions
- good vendor support/training
- good "early win" / "big bang" pilot
- support for versioning of metadata definitions
- nice, "comfortable" GUI
- quick & simple navigation
- ad hoc reporting/query
- supports use by both business and IT Back to top
Key Benefits / ROI Arguments
- better documentation / the use of a metadata solution adds just another 5-10% to the cost of a system/project
- proactive vs. reactive
- saves 50% off research time / impact analysis
- helps to sunset legacy systems / upgrade to new
- "common ground" / elements / terms / definitions / components
- "discovery" of what we "don't know"
- increased productivity / efficiency
- support for possible headcount reduction
- increased ability to "deliver"
- "one version of truth" across company
- better decisions / more informed
- increased accuracy
- enabling business users to find information on their own / "self service"
- encourages system utilization by business users
- improved analysis for development staff
- better communication and collaboration between staff Back to top
Implementation Guidelines - "Enablers" to a Successful Implementation
- find the "killer app"
- under-promise / over-deliver / manage expectations
- get "buy in" / collaboration / consensus
- timing / "carpe diem" / seize the moment
- provide useful information for the right people
- get agreement on common "vision"
- start small / don't over-complicate Back to top
Implementation Guidelines - "Barriers" to a Successful Implementation
- price/value is not understood/appreciated
- status quo / "why change" ?
- lack of implementation skills needed
- perception that it is "a lot of work"
- over-scoping
- metadata "buzz words" / vocabulary / lack of education
- difficult to get business participation
- becomes "shelfware" / another IT tool Back to top