Scope

Team BetaTeam BetaFinal PresentationFinal Presentation

Ken AbrahamsenKen AbrahamsenSandi KruszenskiSandi Kruszenski

John TangJohn TangSheila UnderwoodSheila Underwood

Shih-Kai WengShih-Kai Weng

IMT 589, Winter 2006IMT 589, Winter 2006

ScopeScope

3

KUWAT Sports Card Inc.KUWAT Sports Card Inc.

• A sports trading card company

– “Provide Customers and Consumers with Sports and Entertainment Products that Reflect Our Commitment to Rich Set Content, Innovative Design, Quality Craftsmanship, and Authenticity.”

• The cornerstone of business is based on sports trading cards

• Around 200 employees• Employees consist of Marketing, Sales, Back

Office and Product Development

4

Purpose of Enterprise Metadata Purpose of Enterprise Metadata ProjectProject

• Promote sharing of resources and enhanced information access

• Foster interoperability of resources and build a sustainable infrastructure

• Increase data quality • Simplification of changes • Reduce operational costs• Enable metadata reusability

ApproachApproach

6

ApproachApproach

• Began with a ‘Bottom-Up’ analysis– Identified requirements based on role

group priorities

• Verified schema with a second ‘Top-Down’ analysis

• Captured analysis results in written documentation and artifacts as digital images

7

ApproachApproachSchema DevelopmentSchema Development

• Decide On Organization• Review Role Group Metadata Elements• Allocate / Use Metadata Elements

– Assign, Shuffle, Argue, Bang Collective Heads, Re-Assign, Disagree, Scrap, Re-Do, Add / Remove Elements, Deliberate, Bang Heads (Again, But With More Vigor), Tweak, and Ultimately Settle Into Final Schema…

– Oh, And Feedback From Mike…

8

ApproachApproachDevelopment Of Our Web SiteDevelopment Of Our Web Site

9

ApproachApproachDevelopment Of Our Schema Development Of Our Schema

10

ApproachApproachTask AssignmentsTask Assignments

The SchemaThe Schema

Search and NavigationSearch and Navigation

13


14


1. Search by attributes such as subject, type, people, date, location, organizational structure

15


2. Robust controlled vocabularies

3. Support both searching and browsing

Example: A document about vacation and sick time.

16


4. Provides ability to track and display users previous searches

“Team should show that they considered this requirement and made a reasonable decision to either address this in the metadata or leave it to be addressed to the search technology”

We’re leaving it to the browser

17


5. Provides useful descriptions of documents

18


6. Faceted categories to support multiple views for browsing

19


7. Does not preclude use of any hardware platform or server software under consideration for future development.

It does not.It does not.

Human ResourcesHuman Resources

21


1. Provides unique identifier for individuals

2. Provides role based security (also distribution control)

3. Protects personal privacy and sensitive data

Peopleuserid

employee.organizationemployee.titlevocabulary: CEO, CFOManager, Analyst, Assistantemployee.manager

users.rights.accessrights(HR has authority control for employees)

22


3. Provides primacy control

4. Supports aggregations of data

Contentcontent.date.availablecontent.date.createdcontent.date.modifiedcontent.date.valid (range)accessrightscontent.versioncreatorpublisher (dc)relation (dc)source (dc)

23


5. Provides mechanism to perform HR related tasks in timely manner

6. Provides structure which supports offline processing

Peopledate.cycleupdatedate.freeze

End UserEnd User

25

End UserEnd User

1. End user should be able to search information by subject/content and physical description (title, format, responsible parties, coverage, date created…).

26

End UserEnd User

2. End user should be able to browse through information in an orderly or hierarchical fashion, such as by category or location.

27

End UserEnd User

3. End user should be able to protect their personal information and/or confidential project from being altered or viewed by unrelated personnel.

28

End UserEnd User

4. The information posted on the website should be current and authentic.

29

End UserEnd User

5. Ability to customize the view of information according to personal needs

– It’s about navigation

30

End UserEnd User

6. Ability to share information with users with same interest, in same organizations, in same units, in same projects.

31

End UserEnd User

7. Ability to affect changes within the schema that would better satisfy your needs.

– We don’t offer this function through the KUWAT portal

– However, the user can submit their request to the Integration team

Content ManagementContent Management

33

Content ManagementContent ManagementAudience DefinitionAudience Definition

• Supports the definition of audiences for content items and publications. Content items and groupings can be marked for the attention of public, internal or both, so that target audiences can search for content particular to them.

• Schema Component:– Root Class: KUWAT Sport Cards

• Class: Content– Element: accessrights– Vocabulary: public, internal, both

34

Content ManagementContent ManagementContent PurposeContent Purpose

• Define the content purpose to enable significant user groups to easily access to the type of information they need (examples include product information, FAQs, technical support information)


• Class: Content– Element: subject.category– Vocabulary: product information, FAQs, technical support

information

35

Content Management Content Management Output FormatOutput Format

• Specifies the output formats (such as web, print, physical file) for the content, and allows segmentation of content for reassembly to different publications, which must be defined in the system (for example, a content item such as a product description might be included in an online product guide, a print brochure, and a sales training guide in .pdf format).


• Class: Product– Element: content.format.file– Vocabulary: Defined by RFC2045 and RFC2046

36

Content ManagementContent ManagementContent DescriptionContent Description

• Support for physical description for the content (i.e., File Size, Create Date, Last Modified Date, Version, File Type, Application, etc.)

• Schema Components:– Root Class: KUWAT Sport Cards

• Class: Content– Element: content.format.file.size– Element: content.date.created– Element: content.date.modified– Element: content.version– Element: content.format.file – Application is implicit based on content.format.file value

37

Content ManagementContent ManagementWorkflowWorkflow

• Supports flexible workflow for processes including approval, revision, publishing, retirement of content. Workflow can be based on attributes of content as well as the role and organizational placement of individuals involved in the workflow processes.

• Schema Components:– Root Class: KUWAT Sport

Cards• Class: Content

– Element: content.approve– Element: content.version– Element:content.date.valid


Cards• Class: People

– Element:user.type– Element:employee.title

38

Content ManagementContent ManagementContent OrganizationContent Organization

• User can identify the principal subject matter of the documentation and its location within a category structure (such as product name and version). This provides support for a content organization structure to discover and display the content in a hierarchical form.


Cards• Class: Content

– Element: content.description– Element: subject.keyword– Element: subject.category– Element: content.version

• Schema Components:– Root Class: KUWAT Sport Cards

• Class: Product– Sub Class: Identifier

» Element: product.name» Element: product.version» Element:

KUWAT.edition.type

39

Content ManagementContent ManagementAccess ControlAccess Control

• Provide the means to control the authority of users for appropriate access right such as add, edit, delete or read to content items.


• Class: People– Element: users.access.rights

» Vocabulary: add, edit, delete or read

– Sub Class: userid

» Element: user.type

40

Content Management Content Management Digital Rights ManagementDigital Rights Management

• Supports the indication of the digital rights attached to the content being published.


• Class: Content– Sub class:digital.rights

» Element: usage (Vocab: display, print, play, execute)» Element: reuse (Vocab: modify, except, annotate,

aggregate)» Element: transfer (Vocab: sell, lend, give, lease)

IntegrationIntegration

42

Project Team

KUWAT Cards Inc. Metadata Support

webweb

1. Send Request For Service (RFS) to Integration Team

4. Sign Customer Support Agreement (CSA)

5. Kick off meeting between Web analyst and project team

Cost Analysis

6. Perform statement of work

7. Completion of Exit Criteria

8. Customer follow up / interview

Request For Service Process

2. Receive RFS and assign to focal

3. Gather requirements, Develop Proposal


43

IntegrationIntegrationGather requirements, Develop ProposalGather requirements, Develop Proposal

1. Define Needs• Hardware/Software requirements• Stakeholder supports• Skill requirements

2. Define Applications• What are the requirements for the tool?• How will it integrate with what we already have?

3. Define Usage• How will the tool be used?• Who are the potential users?

44

Project Team


webweb

1. Send Request For Service (RFS) to Integration TeamCost

Analysis










45

IntegrationIntegrationCustomer Support AgreementCustomer Support Agreement

1. Identifies administrative ownership of content

2. Approves/Disapprove the Project

3. Sign-off for buy-in with the right stakeholders

46

Project Team webweb

1. Send Request For Service (RFS) to Integration TeamCost

Analysis











47

IntegrationIntegrationDefine Metadata Tag between Web Define Metadata Tag between Web

Analyst and Project TeamAnalyst and Project Team

Integration Metadata Elements1. Display Content

2. Accessibility

3. Access Control

4. Encryption

5. Administrative Ownership

6. Controlled Vocabularies

7. Version Control

8. Change Request

48

1. Supports content format-type declaration, and, where applicable, allows for selection of content based on application device and display characteristics.

IntegrationIntegrationDisplay Content ElementsDisplay Content Elements

49

2. Complies with organizational standards for accessibility.

Add: Accessibility for disability

IntegrationIntegrationAccessibilityAccessibility

50

IntegrationIntegrationAccess ControlAccess Control

3. Complies with access control policies for the organization, and allows content owners to designate permissions for viewing and modifying.

51

IntegrationIntegrationEncryptionEncryption

4. Supports mandatory encryption of values according to organizational privacy and security policies to prevent the display of sensitive employee information.

52

IntegrationIntegrationAdministrative OwnershipAdministrative Ownership

5. Identifies business unit administrative ownership of content.

53

IntegrationIntegrationAdministrative Ownership (Con’t)Administrative Ownership (Con’t)

5. Identifies business unit administrative ownership of content.

54

IntegrationIntegrationControlled VocabularyControlled Vocabulary

6. Supports extensibility of schema and controlled vocabularies.

55

IntegrationIntegrationVersion ControlVersion Control

7. Provides ability to identify version requested and to respond appropriately.

56

IntegrationIntegrationChange RequestChange Request

7. Supports process for comprehensive schema lifecycle management from request to change, to version control and implementation.

57

Change Board Committee


webweb

1. Send Request For Change (RFC) to Integration Team


4. Approve / Disapproved of Change


Cost Analysis




Request For Change Process


4a. Disapprove of Change

CustomerCustomer

4b. Approved of Change

Change Request (con’t)Change Request (con’t)

ObstaclesObstacles

59

ObstaclesObstacles

• List of Elements ≠ Schema– We quickly identified our elements– Working that into a Schema was hard

• We kept getting the same feedback from Mike “It’s a good start…”

60

ObstaclesObstacles

• SchemaLogic– At first, this seemed like a good tool to help us

identify inconsistencies and “holes” in our schema

– And while it worked, it did help– However it was down so much of the quarter

that we didn’t get to use it much– Inconsistencies and gaps are difficult to

identify in a spreadsheet

61

ObstaclesObstacles

• Team Distraction– Like everyone else in the cohort, our team

was distracted by the sheer amount of work this quarter

– Planning for our capstone– And by issues in the other class– The good news is that our team handled this

obstacle pretty well

62

ObstaclesObstacles

• TRW (The Real World)– Outside of UW, our team was especially busy

this quarter• Ken’s continuing Company X saga• Sandi with EOY financials• John with his new job• Sheila’s organizational changes• Shawn’s project in biostatistics department

Lessons LearnedLessons Learned

64

Lessons LearnedLessons Learned

• Facets vs. Hierarchical?

• Gathering Requirements

• Why we should leave metadata to the experts?

65

Lessons LearnedLessons LearnedFacets vs. HierarchicalFacets vs. Hierarchical

• Pick your poison.

• Don’t spend too much time picking one.

• Develop your schema early

• Then modified as needed

• Respect others point-of-view

• Be flexible

66

Lessons LearnedLessons LearnedGathering RequirementsGathering Requirements

• Take good notes of what your role group intention.

• Keep in touch with your role group throughout the process.

• Work together as a team.

67

Lessons LearnedLessons LearnedMetadata ExpertMetadata Expert

• Examine the reading assignments carefully.

• Solicit feedback from Mike!

ResourcesResources

69

ResourcesResources

– Tannenbaum, Adrienne. (2001). Metadata Solutions: Using Metamodels, Repositories, XML, and Enterprise Portals to Generate Information on Demand (Addison-Wesley).

– Noy, N. & McGuiness, D. (n.d.). Ontology development 101: A guide to creating your first ontology. Retrieved December 16, 2005 from Stanford University, Deborah L. McGuiness web site: http://www.ksl.stanford.edu/people/dlm/papers/ontology101/ontology101-noy-mcguinness.html

http://www.ksl.stanford.edu/people/dlm/papers/ontology101/ontology101-noy-mcguinness.html

http://www.ksl.stanford.edu/people/dlm/papers/ontology101/ontology101-noy-mcguinness.html

70

ResourcesResources

– Boxes and Arrows Retrieved Feb. 28, 2006 from http://www.boxesandarrows.com – Accessibility and Metadata, By: Vashti Zarach.

Retrieved Feb. 28, 2006 from http://www.cetis.ac.uk/members/x4l/articles/copy_of_template

– World Wide Web Consortium(Last modified: Feb. 12, 2006). Retrieved Feb. 12, 2006 from http://www.w3.org/

– New Zealand Government Locator Service (NZGLS) Metadata Schema Compliance Study. (2001, December). Retrieved December 16, 2005 from http://www.e-government.govt.nz/docs/nzgls-compliance-study/nzgls-compliance-study.pdf.

http://www.boxesandarrows.com/

http://www.cetis.ac.uk/members/x4l/articles/copy_of_template

http://www.w3.org/

http://www.e-government.govt.nz/docs/nzgls-compliance-study/nzgls-compliance-study.pdf

http://www.e-government.govt.nz/docs/nzgls-compliance-study/nzgls-compliance-study.pdf

71

ResourcesResources

• UK e-Government Metadata Standard Version 2.0 http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=768

http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=768

http://www.govtalk.gov.uk/schemasstandards/metadata_document.asp?docnum=768

Metadata Structures and Metadata Structures and ApplicationsApplications

Questions ??

Thank you !!

Documents

Scope