Scope

1. Team BetaFinal PresentationKen AbrahamsenSandi KruszenskiJohn TangSheila UnderwoodShih-Kai WengIMT 589, Winter 2006

2. Scope

3. 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 Project • 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

5. Approach

6. Approach • 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. ApproachSchema 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. ApproachDevelopment Of Our Web Site

9. ApproachDevelopment Of Our Schema

10. ApproachTask Assignments

11. The Schema

12. Search and Navigation

13. Search and Navigation

14. Search by attributes such as subject, type, people, date, location, organizational structure Search and Navigation

15. Robust controlled vocabularies Support both searching and browsing Search and Navigation Example: A document about vacation and sick time.

16. Provides ability to track and display users previous searches Search and Navigation “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. Search and Navigation • Provides useful descriptions of documents

18. Faceted categories to support multiple views for browsing Search and Navigation

19. Search and Navigation • Does not preclude use of any hardware platform or server software under consideration for future development. It does not.

20. Human Resources

21. Human Resources • Provides unique identifierfor individuals • Provides role based security(also distribution control) • Protects personal privacy and sensitive data

22. Human Resources • Provides primacy control • Supports aggregations of data

23. Human Resources • Provides mechanism to perform HR related tasks in timely manner • Provides structure which supports offline processing

24. End User

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

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

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

28. The information posted on the website should be current and authentic. End User

29. End User • Ability to customize the view of information according to personal needs • It’s about navigation

30. Ability to share information with users with same interest, in same organizations, in same units, in same projects. End User

31. End User • 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

32. Content Management

33. 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 Content ManagementAudience Definition

34. 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) Schema Component: Root Class: KUWAT Sport Cards Class: Content Element: subject.category Vocabulary: product information, FAQs, technical support information Content ManagementContent Purpose

35. 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). Schema Component: Root Class: KUWAT Sport Cards Class: Product Element: content.format.file Vocabulary: Defined by RFC2045 and RFC2046 Content Management Output Format

36. 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 Content ManagementContent Description

37. 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 Content ManagementWorkflow • Schema Components: • Root Class: KUWAT Sport Cards • Class: People • Element:user.type • Element:employee.title

38. 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. Schema Components: Root Class: KUWAT Sport Cards Class: Content Element: content.description Element: subject.keyword Element: subject.category Element: content.version Content ManagementContent Organization • Schema Components: • Root Class: KUWAT Sport Cards • Class: Product • Sub Class: Identifier • Element: product.name • Element: product.version • Element: KUWAT.edition.type

39. Provide the means to control the authority of users for appropriate access right such as add, edit, delete or read to content items. Schema Component: Root Class: KUWAT Sport Cards Class: People Element: users.access.rights Vocabulary: add, edit, delete or read Sub Class: userid Element: user.type Content ManagementAccess Control

40. Supports the indication of the digital rights attached to the content being published. Schema Component: Root Class: KUWAT Sport Cards 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) Content Management Digital Rights Management

41. Integration

42. Integration Request For Service Process • Send Request For Service (RFS) to Integration Team Project Team Cost Analysis web 4. Sign Customer Support Agreement (CSA) 3. Gather requirements, Develop Proposal 2. Receive RFS and assign to focal KUWAT Cards Inc. Metadata Support 5. Kick off meeting between Web analyst and project team 6. Perform statement of work 7. Completion of Exit Criteria 8. Customer follow up / interview

43. IntegrationGather requirements, Develop Proposal • Define Needs • Hardware/Software requirements • Stakeholder supports • Skill requirements • Define Applications • What are the requirements for the tool? • How will it integrate with what we already have? • Define Usage • How will the tool be used? • Who are the potential users?

44. Integration Request For Service Process • Send Request For Service (RFS) to Integration Team Project Team Cost Analysis web 4. Sign Customer Support Agreement (CSA) 3. Gather requirements, Develop Proposal 2. Receive RFS and assign to focal KUWAT Cards Inc. Metadata Support 5. Kick off meeting between Web analyst and project team 6. Perform statement of work 7. Completion of Exit Criteria 8. Customer follow up / interview

45. IntegrationCustomer Support Agreement • Identifies administrative ownership of content • Approves/Disapprove the Project • Sign-off for buy-in with the right stakeholders

46. Integration Request For Service Process • Send Request For Service (RFS) to Integration Team Project Team Cost Analysis web 4. Sign Customer Support Agreement (CSA) 3. Gather requirements, Develop Proposal 2. Receive RFS and assign to focal KUWAT Cards Inc. Metadata Support 5. Kick off meeting between Web analyst and project team 6. Perform statement of work 7. Completion of Exit Criteria 8. Customer follow up / interview

47. IntegrationDefine Metadata Tag between Web Analyst and Project Team Integration Metadata Elements • Display Content • Accessibility • Access Control • Encryption • Administrative Ownership • Controlled Vocabularies • Version Control • Change Request

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

49. Complies with organizational standards for accessibility. Add: Accessibility for disability IntegrationAccessibility

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