6
E n t e r p r i s e A r c h i t e c t u r e 2 0 1 3 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

Embed Size (px)

Citation preview

Page 1: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

ITAG 05-03-2013

Data Governance – Metadata RepositoryEAAF - Update

Page 2: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

2

Data Governance & Metadata Repository• EA Data Architect – Micheal Schwartz

[email protected]

• Initiating research on Metadata Repositories as part of larger Data Governance program– Key sections of metadata repository guideline doc

• Request ITAG members gather some information from their respective campuses & medical centers– Identify “significant” metadata repositories currently

in use. Significant: contains metadata for more than one application/subject, current, etc.

– Identification of metadata tool used (or custom) – Subject Matter Expert contact information

Page 3: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

3

Request for input

• Follow up from last meeting (April 2013): – ACTION: ITAG members to send the definitions of terms,

and how they use that specific term at our respective campus - Standards, Principles

– ACTION: ITAG members to identify if other "assets" should be added to the list, for curation in the EAAF repository and sharing across the UC system. Please include definition (compare/contrast) between each asset type, and if any examples. Current asset list includes: guideline, specification, process/procedure, anti-patterns, security controls, reference architecture, data models, and code samples.

– ACTION: Identify/recommend a tool that would support the variety of our repository needs (submission, workflow, perhaps even communications, etc.)

– ACTION: Consider if we should focus on Standards and principles first, and the rest later, or look at the entire range of assets.

Page 4: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

4

Response• Received input from 4 ITAG members– TOGAF definitions were consistently

recommended for Principles & Standards– Principles & Standards are the priority

asset/artifact type to gather an publish– Trello & SharePoint identified as possible

application interfaces to the EAAF repository (EA Body of Knowledge)

Page 5: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

5

Asset Types

Page 6: Enterprise Architecture 2013 ITAG 05-03-2013 Data Governance – Metadata Repository EAAF - Update

En

terp

rise A

rch

itectu

re

2013

6

Next steps:• Create document templates for Principles and Standards –

EA team

• Improve EAAF repository (SharePoint) – EA team

• Publish existing assets on EAAF repository – EA team– Leverage UCPath artifacts– Leverage Standards & Principles already published by UC IT

departments

• E-mail ITAG listserv when assets published – EA team

• Provide feedback to EA team on published assets with 30 days – ITAG members

• Forward any candidate assets to EA team – ITAG members