1. EPA Enterprise Data Architecture Metadata Framework Assessment Kevin J. Kirby, Enterprise Data Architect EPA Enterprise Architecture Team Kirby.Kevin@epamail.epa.gov (202) 566-1656

2. 1 Enterprise Metadata Framework Assessment Overview Report purpose and goals Enterprise Metadata Framework assessment Strategy for enabling the Enterprise Metadata Framework Recommendations

3. 2 Enterprise Metadata Framework Assessment Purpose and Goals Perform an assessment of EPA’s key repositories and metadata contributors –Policy and guidance –Use cases and content type Determine enterprise findability of key repository’s metadata content –Dublin Core alignment –Architecture –Infrastructure Leverage assessment into strategy and recommendations –Consider the metadata maturity model as well as current research and direction

4. 3 Enterprise Metadata Framework Assessment Significant momentum exists for program centric metadata development –Programs defining their own standards and processes –Programs with mandatory participation requirements and consistent outreach offer the most quality content EPA’s metadata tools are diverse yet support specific business requirements –The agency can leverage existing tools infrastructure but also requires some independent enabling tools Agency enterprise metadata requires further definition and validation –Programs perceive their efforts as enterprise efforts –Retrievable content and functional systems offer legitimacy –Confusion exists (System of systems, metadata about metadata)

5. 4 Enterprise Metadata Framework Assessment (cont’d) The Enterprise Metadata Framework should be a unifying agent for agency metadata –Connective framework - no additional repositories –Forward thinking architecture

6. 5 I. Ad Hoc II. Discovered III. Managed IV. Integrated V. Optimized METADATA MANAGEMENT The organization of technical and business metadata with the goal to advance the sharing, retrieving and understanding of enterprise information assets. WITH NO METADATA MGMT Information is lost or hidden Data integration is costly Cannot support everyday business Information is difficult to find Partial & dated information Loss of trust in data Enterprise Metadata Framework Assessment (cont’d)

7. 6 Metrics defined to roughly assess repository findability in terms of the metadata maturity model –People – function of repository as well as guidance used to define content –Process – how a repository creates content –Technology – how a repository stores and presents content –Focus on alignment of content with Dublin Core metadata elements Enterprise Metadata Framework Assessment (cont’d)

8. 7

9. 8

10. 9 The recommended strategy for characterizing and implementing the Enterprise Metadata Framework includes: 1.Define the framework and its benefits 2.Establish a simple baseline and add iterative capability 3.Leverage existing momentum through easily obtainable requirements and supporting tools 4.Allow repository owners/contributors to incorporate the framework into business processes 5.Establish an initial discovery mechanism to give the framework relevancy Each step is described in further detail in subsequent slides Enterprise Metadata Framework Strategy

11. 10 Define the framework and its benefits –Frame the need for a broad discovery capability –Re-affirm the need for specific detailed repositories –Outline framework requirements and implementation perspective –Provide schematics to illustrate how framework operates and fits within Agency infrastructure –Once defined, conduct significant and consistent outreach to generate and maintain participation Enterprise Metadata Framework Recommendations

12. 11 Establish a simple baseline and add measured capability –Establish and gain traction –Focus on structured metadata –Define critical and optional Dublin Core categories Enterprise Metadata Framework Recommendations (cont’d)

13. 12 Leverage existing momentum through easily obtainable requirements and supporting tools –Metadata is growing organically within the agency –Metadata efforts are largely program/system specific –Let systems/programs work out metadata stewardship –Insert enterprise requirements as a component of any development effort Enterprise Metadata Framework Recommendations (cont’d)

14. 13 Allow system owners/contributors to incorporate the framework into business processes –Provide enterprise requirements but let business owners define where they fit Establish an initial discovery mechanism to give the framework relevancy –Make the framework real –Provide a functioning capability and use outreach to promote use of capability Enterprise Metadata Framework Recommendations (cont’d)

15. 14 Enterprise Metadata Framework Recommendations (cont’d)

16. 15 Conceptual metadata search mechanism Enterprise Metadata Framework Recommendations (cont’d)

17. 16 Conceptual metadata search mechanism –A webservice API offers a lightweight, independent, and customizable search mechanism It passes search parameters from a client to repositories and presents aggregated results It enables broad findability while preserving the need for detailed repositories It is flexible and open to new standards or repositories –Repositories enable search to align with standards (Dublin Core in this case) Map internal content to standards On-demand (real-time repository search) or content file presentation –Cache is used to enable search for off-line systems Cache can be cleared as needed –The client front end can be anything –Implementation could be COTS, GOTS, or a combination of the two Enterprise Metadata Framework Recommendations (cont’d)

18. 17 Develop metadata tools matrix –Informed by EMF strategy/recommendations –Include metrics to build remaining work products Develop metadata tools assessment work product Develop harvesting assessment work product Develop reuse assessment work product Develop communications and scoping strategy report work product Enterprise Metadata Framework Next Steps