tonedeaf, inc. group zeta group zeta a metadata proposal james boaz duane mccollum kim piira nina...

ToneDeaf, ToneDeaf, Inc.Inc.

Group Group ZetaZeta

A Metadata ProposalA Metadata Proposal

James BoazJames BoazDuane McCollumDuane McCollum

Kim PiiraKim PiiraNina VredevoogdNina Vredevoogd

Jim WernerJim Werner

March 13, 2004March 13, 2004

ToneDeaf, Inc. ToneDeaf, Inc. “You Talk. We Wonder”“You Talk. We Wonder”


A growing cell phone companyA growing cell phone company Approximately 500 employeesApproximately 500 employees Several information needs to be Several information needs to be

represented in internal web content.represented in internal web content. Data structure to be generalized through Data structure to be generalized through

content management and integration.content management and integration. Web content to be instantiated by Web content to be instantiated by

applications for users, human resources, applications for users, human resources, search / navigation.search / navigation.

Group Zeta designed a metadata schema Group Zeta designed a metadata schema to meet ToneDeaf’s needs.to meet ToneDeaf’s needs.

ToneDeaf, Inc.ToneDeaf, Inc.


IntegrationIntegration

It’s all about Agreement! It’s all about Agreement! Began with “Three P’s” conceptBegan with “Three P’s” concept Category discussion – Content Class discussionCategory discussion – Content Class discussion Element/vocabulary decisions “organizing”Element/vocabulary decisions “organizing”

How did the ZETA Team do it?How did the ZETA Team do it? Approach – Overall Integration Philosophy Approach – Overall Integration Philosophy

based on business requirements.based on business requirements. Created personas, scenarios to express Created personas, scenarios to express

business requirements.business requirements.



Integration – Overall PhilosophyIntegration – Overall Philosophy

Have a well-structured information Have a well-structured information paradigm for customer/employee paradigm for customer/employee interaction.interaction.

Content Management for external and Content Management for external and internal customers.internal customers.

Share information resources across the Share information resources across the enterprise framework of ToneDeaf.enterprise framework of ToneDeaf.



Integration Highlights Integration Highlights Accessibility and Device Accessibility and Device Considerations – Screen Resolution considerations (Publishing and Considerations – Screen Resolution considerations (Publishing and Personalization Info)Personalization Info)



Integration Highlights- Integration Highlights- Roles & Protected Content Roles & Protected Content (Content Permissions)(Content Permissions)



Integration Highlights – The Integration Integration Highlights – The Integration “Catch 22” “Catch 22” Product Content Class and Element Set Product Content Class and Element Set IllustrationIllustration



Integration – Highlights - Integration – Highlights - Other RequirementsOther Requirements

User FeedbackUser Feedback Further Discussion in User SectionFurther Discussion in User Section

Minimum “Tagging” required Minimum “Tagging” required Largely Content Management ElementLargely Content Management Element

Reuse and Repurpose of vocabs and elementsReuse and Repurpose of vocabs and elements Illustrated throughout presentation – Product Catch 22Illustrated throughout presentation – Product Catch 22

How to Manage all this? = How to Manage all this? = Information Management Information Management TeamTeam

Publishing TeamPublishing Team Taxonomy Management TeamTaxonomy Management Team Work together with departments to publish and Work together with departments to publish and

manage contentmanage content..



Integration – Maintenance, Changes and Integration – Maintenance, Changes and ResourcingResourcing

How will we ensure schema can be maintained, How will we ensure schema can be maintained, resourced and changed?resourced and changed?

Management Approach “Process & Tool”Management Approach “Process & Tool” Information Management OrganizationInformation Management Organization

Facilitates schema creation among teams and across Facilitates schema creation among teams and across teams.teams.

Voting via SchemaServer or similar toolVoting via SchemaServer or similar tool Steering Team/Change BoardSteering Team/Change Board Idea of Projects and Sub-teamsIdea of Projects and Sub-teams New team members or stakeholders would be added as New team members or stakeholders would be added as

necessarynecessary

ToneDeafToneDeaf, Inc., Inc.


Integration – Maintenance, Changes and ResourcingIntegration – Maintenance, Changes and Resourcing

Information Mgmt

Integration&

Search

Taxonomy/Schema

Dev/Programmer

Change Board(Info Mgmt)

Human Resources

Product & Svcs

Marketing

Content Mgmt

Taxonomy/Schema

Search Manager

Search & Navigation

Schema Mgmt

Other IT Departments

Change Board is responsible for reviewing and making major changes Schema as a whole. All content is owned by business units, but major stakeholders must be engaged when changes are proposed. Management of schema and taxonomy is done by Information Management teams. Major issues for resolution are also brought to Steering Team.

Content Management & Publishing

Business Analyst

Publishers

Publish Content to Portal

Consensus & Buy in for proposed changes to schema

Schema Management & Change Process

Publishing request

Impact Analysis



Integration – Maintenance, Changes and Integration – Maintenance, Changes and ResourcingResourcing

Why this approach? Why this approach? Small Company – Growth may change the Small Company – Growth may change the

approach.approach. Information Mgmt Team acts as a consultant.Information Mgmt Team acts as a consultant. More controlled/Streamlined processMore controlled/Streamlined process Minimal training required – only processMinimal training required – only process Training will be team basedTraining will be team based Changes can be made daily or weeklyChanges can be made daily or weekly

Emergency, Two-Day, weeklyEmergency, Two-Day, weekly


Group ZetaGroup Zeta

Collect, manage and publish contentCollect, manage and publish content

Channel content appropriately to target Channel content appropriately to target audiencesaudiences

Manage the workflow process in content Manage the workflow process in content creation and publicationcreation and publication

Segment content into structural components Segment content into structural components for reuse in display or print publicationsfor reuse in display or print publications

CONTENT MANAGEMENTCONTENT MANAGEMENT



Content ClassesContent Classes


Administrative Descriptive

StructuralWorkflow

Tracking

Publishing

Elements divided into three main classes



Administrative Content Management Elements Administrative Content Management Elements


WorkflowWorkflow ElementsElements



Administrative Content Management Elements Administrative Content Management Elements


Tracking Elements Publishing ElementsTracking Elements Publishing Elements



Content Tracking ComponentsContent Tracking Components


Tracking by minimum of creator, date, subject

Reporting by workflow state, date issued

Requires unique IDfor all content

Version control to maintain information about version history

Content channeled correctly to internal and external audiences and user groups

Manages content types

Role-based security



Descriptive Elements Structural ElementsDescriptive Elements Structural Elements




Descriptive Elements and VocabulariesDescriptive Elements and VocabulariesCONTENT MANAGEMENTCONTENT MANAGEMENT



Structural Elements and VocabulariesStructural Elements and Vocabularies




Human ResourcesHuman Resources

We first thought about making things as general as possible…

ThingName, ThingType, RelatedThingRelationshipType were bound to certain taxonomies based on a dynamic, context-directed API (this is also known as high-pattern density meta-architecture).

Self join on ThingID and RelatedThingID




ThingName, ThingType, RelatedThingRelationshipType were bound to certain taxonomies based on a dynamic, context-directed API (this is also known as high-pattern density meta-architecture).

But that’s too easyBut that’s too easy!!



Human ResourcesHuman ResourcesGoal: HR Schema Metadata Classes support HR Policy first, technology second.

• Employee information is considered company property and is private to the company and the employee. • Employees have the option to designate that certain of their personal information may be shared within the company among other employees; however, by default, all employee data is private, between the employee and the company as represented by the HR dept.• The release of any HR held data must be validated for release by the by the Legal dept. Metadata for release events, including person who authorized, what was released, and to whom.• Employee information can be accessed by the employee or by certain designated HR personnel. • Updates may be made by the employee on their personal information.• HR Administrators Create, Read, Update HR records according to applicable laws, regulations, and policy memorandum & directives from CIO, Legal, or HR management.



Content Class ReuseContent Class ReuseWe used a Lego block approach

• Use them build more complex schemas to do more work for us

• Create simple, small schemas that should be reused

Name

For Example, the content class Name…

LastNameFirstNameMiddle

Has elements . . .




Content Class Content Class ReuseReuseEmployee Content

Class

Name LastNameFirstNameMiddle

EmployeeID

Other… Element 1Element 2Element n

Other… Element 1Element 2Element n

Other ElementOther Element

Other Element




Compound SchemasCompound SchemasPeople

Core HR Content ClassPerson

Name

Record Accuracy Elements

The People class has Core HR Content Classes, Extended, and FeedStore classes.

This collection has generic building blocks such as Name, Address, Phone Number.

We used these classes to create classes such as Person

And then re-used Person in the Employee class, the employee’s Spouse class, the employee’s emergency contact, and so on…




Employee…Employee…

Reuse of Person class

Container to managetimeliness and historyincluding NextUpdateDateelement


#6,7 periods for update#6,7 periods for update



Payroll processing is one example of schemas supporting batch processing …..

Any metadata instance that refers to a Batch Job will use this class.

Legal Dept. must sometimes approve release of HR data in a batch.

ApprovalForRelease class reused here & elsewhere…


#8#8



We can manage distribution of HR data to approved subscribers…

This might be a dump of HR data to be used by someone internally….

ApprovalForRelease class

HR Certification ElementHRCertification is a binary

signature, an HR Stamp of Authenticity for that data it is referring to…..


Who it goes to, where, etc.#2#2



Human ResourcesHuman Resources The WhitePage class is used by HR to help people find each other. We reuse the employee class entirely. However, the IsPrivate element, set to True by default, can be set by the Employee for certain classes. Some, they cannot, such as their Payroll information, or work phone. 3,4,5

We expect an application layer, like the metadata instance server to not even release anything that is marked IsPrivate


Organizing principle is “Aboutness” Organizing principle is “Aboutness” Search Index Search Index

Borrows Descriptive elements from CM Borrows Descriptive elements from CM Adds index term, navigation, relevance and Adds index term, navigation, relevance and

access access Search categories through filteringSearch categories through filtering

NavigationNavigation Nested structure allows local menu sitesNested structure allows local menu sites Controllable access Controllable access

Search & NavigationSearch & Navigation

ToneDeaf, IncToneDeaf, Inc..



Personal Security through PersonalizationInfo content classPersonal Security through PersonalizationInfo content class

END USERSEND USERS



Personalize view with page settings. Also, content through Personalize view with page settings. Also, content through subscriptions, task list, and search history.subscriptions, task list, and search history.

END USERSEND USERS



Use of vocabulary with Use of vocabulary with related terms.related terms.

ToneDeafSubjectTaxonomy ToneDeafSubjectTaxonomy uses:uses:

- Related terms for Related terms for Package, Phone, AboutPackage, Phone, About

- Entry terms for Northwest, Entry terms for Northwest, SecuritySecurity

END USERSEND USERS



Content Creator, ContactContent Creator, Contact

Content Dates and CommentsContent Dates and Comments

END USERSEND USERS



Quickly find common items using best bets and relevance Quickly find common items using best bets and relevance based ranking. URL provides links to company resourcesbased ranking. URL provides links to company resources

END USERSEND USERS



Structure of schema focuses on a logical back-end Structure of schema focuses on a logical back-end construction with a Product class for what ToneDeaf sells. construction with a Product class for what ToneDeaf sells.

END USERSEND USERS



Can identify an employee with ID. Contact can be made with Can identify an employee with ID. Contact can be made with email, cell phone, job title, and you can track their job skills.email, cell phone, job title, and you can track their job skills.

END USERSEND USERS



Work tasks description along with project nameWork tasks description along with project name

END USERSEND USERS



To provide content through HR that could be coupled with To provide content through HR that could be coupled with PersonalizationInfo by an application. Note EmployeeID.PersonalizationInfo by an application. Note EmployeeID.

END USERSEND USERS



User Feedback through Workflow content class User Feedback through Workflow content class that can be modified through an application.that can be modified through an application.

END USERSEND USERS



Lessons Learned – Zeta TeamLessons Learned – Zeta Team Need a single architect responsible for the overall design Need a single architect responsible for the overall design

and framework. and framework. Do Taxonomy First Do Taxonomy First

If you do work on it, stick with it!If you do work on it, stick with it! Layout Elements after Taxonomy completeLayout Elements after Taxonomy complete

Aggregate Element sets and ideas from the team.Aggregate Element sets and ideas from the team. Agreement IS difficultAgreement IS difficult

Takes Patience and Rework! Takes Patience and Rework! Use SchemaLogic as a repository tool, not as an Use SchemaLogic as a repository tool, not as an

architectural design tool.architectural design tool. Generalization vs. ComplicationGeneralization vs. Complication -How useful is the -How useful is the

general solution? Generalization and reuse are useful general solution? Generalization and reuse are useful methodologies if you really need to reuse something. If methodologies if you really need to reuse something. If not, you’re just adding more work and complexity to not, you’re just adding more work and complexity to your project.your project.



Most important lesson learned:

Once it's out of the horse, it can't be put back in!

QUESTIONS?

tonedeaf, inc. group zeta group zeta a metadata proposal james boaz duane mccollum kim piira nina...

Documents

group zetacollect

group zetaintegrationits

content creation

publicationsegment content

contentchannel content

product content class

internal web content

group zeta administrative