1. SchemaServer Overview Tools for Enterprise Metadata Management and Synchronization Prepared for the University of Washington Information School Applied Metadata Class Gary Carlson garyc@schemalogic.com

2. SchemaLogic at-a-Glance Software and Services to:  Organize how information is tagged, exchanged & retrieved  Control, reconcile and synchronize shared metadata  Create and manage an Enterprise Metadata framework, based on common metadata model and shared repository Example Projects:  Standardize shared vocabulary  Create XML Schema library  Enterprise taxonomy management  Reference data management  Reconcile DBMS schema  Synchronize content management systems  Support federated search and portal initiatives

3. Babe Issue: Inconsistent Structures & Semantics Cust_ID Customer# Client_no CUST1 Severity = 1 Sev_Code = A One Concept can have many different expressions One Expression can refer to many different concepts

4. Solution encompasses Structure & Taxonomy Reconcile metadata definitions in common information model Structural Metadata Taxonomic Metadata NameString BirthdateDateTime EmpIdInteger Retail Division Finance Operations Marketing G&A N. America Europe Asia-Pacific Division Database, XML, XSD, DTD, Web Forms, MARC, Dublin Core, EDI standards, etc Authority Lists, Thesauri, Taxonomies, Controlled Vocabularies, Ontologies, Facets. Pick Lists, etc

5. Taxonomy Vocabularies/Pick Lists Database Schema Catalog XML Schema Library Location/Stewardship Dictionary/Thesauri Relationships/Associations Data/Content Layer Data Consumer Layer Descriptive info, Categorization info, Structural info, Navigational info, Re-use info, Retrieval info… METADATA Layer Reference Data

6. Enterprise issues Individual systems and initiatives can probably take care of themselves, once data structures need to be shared across more than one system, or cross a boundary then… Content management/integration Taxonomy reconciliation Standard vocabularies Data warehouse/reporting teams Reconcile for BI Reference data mgt XML developers Reuse of XML Schema Approved changes synchronized Enterprise Information Architects Model information flow Many-to-one mapping, standards

7. Onto SchemaServer… First some administrative details Login (see URL and login on sheet) –http://www.schemalogic.net/uw_xxxx/http://www.schemalogic.net/uw_xxxx/ –Go to Users screen –Change password –Correct name if necessary –Type in e-mail Guest account on each database

8. The Driver’s License A collection of concepts (elements) Each element has its own use, description, and data format. –Exp. Date = Date/Time –Name = String –Eye Color = Controlled List –Etc Each element is re-usable in different systems, forms, etc

9. Elements – Data Containers Element Properties Describe usage, data type, identify the element Element ID A Global Unique Identifier is the ultimate identifier for this object Data Type Define the constraints on legal values for this element…What you can put in this container.

10. Element - Data Type Data Type describes the “allowed values” or constraints for this element. “Vocabulary” elements use vocabularies defined in SchemaServer as their constraint. See the HairColor element. HairColor element is of datatype vocabulary. Vocabulary = Color It is further refined such that only the terms in the terms in the Hair vocabulary view

11. Content Classes - Collections of Elements Describe: Web Forms XSDs Database schemas Content Types etc… Inherit from above Content Classes inherit elements from their parents

12. Content Classes Add/Modify/Delete Add Elements Remove Elements View as XSD/XML/XDR

13. Vocabularies Describes a conceptual domain Geography – color – keywords – video formats - etc Collection of terms and relationships between the terms. Supports most ANSI z39.5 features Supports full localization Extensible term relationship types Can be built of the three standard relationship types

14. Vocabularies – Creation Vocabulary Properties describe the vocabulary itself, not the terms within the vocabulary.

15. Vocabulary – Terms Terms are entities unto themselves – may live in multiple vocabularies Have their own properties May be localized Are created in the context of a vocabulary Inbound and outbound relationships

16. Building a Vocabulary Add a new term to the root term Add an existing term Drag and drop a term from a different vocabulary Create a polyhierarchy Delete a term ----------------- Add an Entry (synonym term)

17. The Whole Shootin’ Match…

18. Questions Add/Modify/Delete –Elements Data types Vocabulary elements –Vocabularies –Vocabulary terms –Content Classes Add and Remove elements