Metadata Management Case Study Date: 10/21/2008

Metadata ManagementCase StudyDate: 10/21/2008

Dan McCreary

President

Dan McCreary & Associates

dan@danmccreary.com

(952) 931-9198

Metadata Solutions

Overview

•The Challenge

•Why XRX is an Ideal Solution

•Screen Images

•Results

Gartner on Metadata

Metadata cast into formal logics will driveinteroperability, automation, cost cutting,better search capabilities and new businessopportunities.

Semantic Web Drives Data Management, Automation and Knowledge and Discovery

Alexander Linder

March 2005

G00125145

The Challenge

•Allow the business people (not the ITdepartment or developers) to manage allaspects of metadata

–Definitions

–Approval

–ISO/IEC Metadata Registry

–Shopping Cart

–Wantlist Management

–Automatic Form Generation

Semantic Triangle

Concept

Referent

Refers To

Symbolizes

Stands For

“cat”

Physical Objects

A pattern of neural activity in our brain

Symbol

Ogden, C. K., & Richards, I. A. (1923) The Meaning of Meaning

“katze” (German)

“gato” (Spanish)

Semantic Web Standards Stack

URI/IRI

Unicode

XML

Namespaces

XML Query

XML Schema

RDF Model & Syntax

Ontology (OWL)

Rules/Query

Logic

Proof

Trusted Semantic Web

Signature

Encryption

Source: Tim Berners-Lee www.w3c.org

http://www.w3.org/Consortium/Offices/Presentations/SemanticWeb/34.html

Example of K-12 Registry

A (meta) Data Registry

Goal: create semantic maps to a federal & statemetadata standard, not many standards

Mapping from Minnesota's metadataregistry to N other metadata registries:The O(N2) problem

NIEM

Mapping from Minnesota's

metadata registry to counties & federalThe O(N) problem

NIEM

Evolving Metadata Standards

ISO standards dominate most metadata registries

ISO/IEC 11179 MDR

GJXDM

NIEM

ebXML

Public Schemas

xBRL

Minnesota

Data

Standards

Federal XMLNaming andDesign Rules

Non-ISO schemas

Federal Data

Reference Model

(DRM)

Federal XMLDeveloper’s

Guide (xml.gov)

XML

UML

XMI

CWM

MOF

XML

DeptStds.

Division Stds

XLink

OASIS Standards

Doc

ISO commercial

schemas

FutureStandards (?)

UBL

Minnesota Enterprise TechnicalArchitecture

•Follow established Minnesota metadata standards

Build an Inventory of Data Elements

Sample Data Element

Examples of Federal Meta Data Registries

•NIEM – National Information Exchange Model

•GJXDM – Global Justice XML Data Model

•ebXML – Extensible Business XML

•UBL – Universal Business Language

•EPA – Environmental Protection Agency

•DOD – Department of Defense Metadata Registry

•xBRL – XML Business Reporting Language

Examples of Local Metadata Registries

•Minnesota Department of EducationRegistry

•Minnesota Department of Revenue PropertyTaxation Registry

•Financial Institution

Property Taxation Example

Example: NIEM.gov

Fill your shopping cartwith Data elements

Easily create sub-schemas for differentneeds

Column

Table

Column

MetadataRegistry A

Registry helps track data source mapping

OLTPRDBMS

•Registry data elements can map to one or more data sources.Concepts usually map to tables and properties map tocolumns.

•Mappings can be used to facilitate transfers

•Mapping can be stored directly in the registry

•Tools are frequently used to create initial mappings

•Organizations can create mappings between their internalsystems and a central metadata registry

Column

Table

Column

Data Warehouse

LocalRegistry

or database

Metadata Registry Workflow Funnel

Create the Registry

•Define your glossary and data elements

•Review & make changes

•Approve & publish by stakeholders

Use the Registry

•Generate data schemas (XML) by selecting and organizing data elements

•Add new items to the registry as needs change

Review

& Edit

Approve

Glossary

Of Terms

Draft Data

Elements

Requirements & data needs

The registry defines thedata we exchange andkeeps our need for codechanges to a minimum

Federated Search

•Federation: When many different sourcescan return search results from a single search

Business

Terms

ACORD

Data

Elements

RDMS

Columns

Other

Standards

WebSite

Terms

Federated Search Results

Metadata Shopper

Why XRX?

•Metadata is complex

•Many nested structures

•Metadata needs to be quickly customized tomeet the needs of different stakeholders

•Data governance is a collaborative process

Before XRX

•Staffing/Skills

–XML Schemas

–XSLT to transform data elements into HTML

–DBAs to create RDBMS tables and indexes

–One or more Java Developers

–HTML Forms and Reports

–CSS

–Reporting tools (Crystal Reports etc)

–Limited form functionality (no AJAX)

•Six people, 9 months $250,000 to $500,000

After XRX

•Skills

–XForms, REST and XQuery

•Steps

–Import data definitions from spreadsheets and XMLsources

–Create data element registry

–Create shopping cart tools with XForms

–Generate XML sub-schemas for importing intodocument exchanges

–Higher quality user experience (suggest items)

•One Person Three Months: $40,000

Thank You!

Please contact me for more information:

•Metadata Management

•Metadata Registries

•Service Oriented Architectures

•Business Intelligence and Data Warehouse

•Semantic Web

•Native XML Databases

Dan McCreary, President

Dan McCreary & Associates

Metadata Strategy Development

dan@danmccreary.com

(952) 931-9198