Taxonomy Governance

Governing the TaxonomyPrepared by Christine Connors, TriviumRLG LLCJune 2010© TriviumRLG LLC 2010

Why do we need to ‘govern’ ataxonomy?✤ Technologies change✤ R&D advances✤ Term meanings evolve✤ Processes are reﬁned✤ People come and go

What are you governing?✤ The labels for a concept ✤ PI can mean many things; Package Insert = PI✤ The deﬁnitions for a concept ✤ “Healthcare professional” means what, exactly?✤ The relationships among concepts ✤ Durg x is indicated for Breast Cancer, NSCLC, HRPC, etc✤ The data elements required for metrics and analysis

What are you governing?✤ The ﬁles/MIME-types that represent these models ✤ Excel? XML? RDBMS? Text?✤ The place of publication / persistence✤ The choice of format for the models ✤ RDF/S ✤ OWL ✤ SKOS

Who should be responsible? ✤ A classiﬁcation expert (taxonomist or ontologist) ✤ A content management expert ✤ Subject matter experts (SMEs) ✤ Representation from the business groups and IT/IS

What is theworkflow? 11. Business & Technology Inputs 2 32. Environmental Scan 63. Design 54. Develop 45. Test6. Improve

Business & Technology Inputs✤ What is the problem to be solved?✤ What questions are you trying to answer?✤ What technology platforms are available/allowed? ✤ What kinds of integration are required?✤ What human bandwidth, capital and ad hoc outlays are available?

Environmental Scan✤ New products or processes?✤ New markets or audiences?✤ New competitors, partners or business units?✤ New research or technologies to model?✤ Changes to other taxonomies, metadata schema or databases?✤ Requests for changes or additions from users?✤ Analysis results that warrant a change?

Design✤ Consider the data elements required to answer the questions at hand. ✤ Does the existing schema design still meet needs? Or are new elements needed?✤ Are changes needed to existing data elements?✤ Are new terms needed for the taxonomies?

Develop✤ Use the “CRUD” methodology to keep the machine files up to date ✤ Create - add new terms, with appropriate labels, definitions and relationships ✤ Read - use the terms, test them in QA and real-world applications ✤ Update - refine any terms, labels, definitions or relationships that require changes ✤ Delete - terms, labels, definitions or relationships that are incorrect or dilute the value of the model

Test✤ Test changes before committing them to production!✤ Use an identical data set to the production set✤ See how new relationships impact models, reasoning, inferencing✤ Ask your normal questions, scan for ‘inappropriate’ answers.

Improve✤ Fix anything found in testing that needs testing✤ Consider the next challenge - the inputs and environmental scan START AGAIN!

When does governance occur?✤ Ideally, from the beginning of the project ✤ Typically, from the publication of version 1✤ Regular meetings are critical ✤ Weekly to begin, depending on the scale, can generally move to monthly as the process and models mature✤ New and updated systems come online✤ New products or processes are live✤ M&A activity occurs

Metadata Management System Permissions Tagging EE RBC I/R Human Machine NLP HybridCMS/DAM CMS/DAM QA CMS/DAM Processing Repository Permissions Query layer Rules Rules Rules Rules Content VerticalsContent Packaging Multimedia Mobile Kbase PrintContent Delivery

Recommendations✤ Source a classiﬁcation expert✤ Identify internal content process and subject matter experts✤ Identify a metadata management system as a mid-term need, begin planning for requirements gathering, documenting and RFI/Q development✤ Select an open source toolset for use until a formal metadata system can be stood up and integrated ✤ e.g. Top Braid Composer (Free Edition), Knoodl, Protege✤ Schedule metadata governance meetings; bi-weekly to start, as process is learned, reduce to monthly

http://www.triviumrlg.com	202
http://triviumrlg.com	119

Taxonomy Governance

by Christine Connors on Jul 22, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 321

Statistics

Taxonomy Governance — Presentation Transcript