Meta Manager 4. User s Manual. Revision 4.0. Prepared by: Compusult Limited 40 Bannister Street Mount Pearl, Newfoundland A1N 3C9

Meta Manager 4 User s Manual Revision 4.0 Prepared by: Compusult Limited 40 Bannister Street Mount Pearl, Newfoundland A1N 3C9 Telephone: (709) 745-7914 Fax: (709) 745-7927 Internet: management@compusult.nf.ca Document No. 901-003 June 27, 2003 Produced under licence from Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources (Crown Copyrights Reserved) by Compusult Limited 1998-2003

Meta Manager Version 4.0 Produced under licence from Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources. Copyright Compusult Limited 1998-2003 (Crown Copyrights Reserved) All rights reserved. This software was not developed for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It is the customer s responsibility to take all appropriate measures to ensure the safe use of such applications if the programs are used for such purposes. This software/documentation is provided under license agreement containing restrictions on use and disclosure; it is also protected by copyright law. Reverse engineering of the software is prohibited. If this software/documentation is delivered to a U.S. Government Agency of the Department of National Defense, then it is delivered with Restricted Rights and the following legend is applicable: Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988). Compusult Limited, P.O. Box 1000, 40 Bannister Street, Mount Pearl, NF, Canada, A1N 3C9 If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with Restricted Rights, as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987). The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Compusult Limited does not warrant that this document is error-free. Meta Manager TM is a trademark of Compusult Limited. All other products or company names are used for identification purposes only and may be trademarks of their respective owners. by Compusult Limited 1998-2003 - Document No. 901-003 ii

CONTENTS CHAPTER 1 Introduction 1-1 1.1 Audience...1-1 1.2 Definitions, Acronyms and Abbreviations...1-1 1.3 Purpose...1-2 1.4 Meta Manager Operation...1-2 1.5 Systems and Network Infrastructure...1-2 1.6 Meta Manager Components...1-3 1.7 How to Use This Manual...1-4 1.8 Conventions...1-4 CHAPTER 2 The Z39.50 Protocol and Associated Profiles 2-1 2.1 The Z39.50 Protocol...2-1 2.1.1 A Brief History of Z39.50...2-2 2.1.2 What Does Z39.50 Do?...2-3 2.1.2.1 Searching a Database...2-4 2.1.2.2 Retrieving Records from a Database...2-4 2.1.3 Using Z39.50 Over the Internet...2-4 2.1.4 The Clearinghouse Concept...2-5 2.2 What is a Profile?...2-7 2.2.1 The GEO Profile...2-7 2.2.1.1 What is the FGDC Metadata Standard...2-8 2.2.1.2 Z39.50 Specifications for GEO...2-8 2.2.1.3 Z39.50 Services...2-9 2.2.1.3.1 Search...2-9 2.2.1.3.2 Retrieval...2-10 2.2.2 The GILS Profile...2-11 2.2.2.1 What is the GILS Metadata Standard?...2-13 2.2.2.2 Z39.50 Specifications for GILS...2-13 2.2.2.3 Z39.50 Services...2-14 2.2.2.3.1 Search...2-14 2.2.2.3.2 Retrieval...2-15 2.2.3 Organization of Metadata Standards...2-16 2.2.3.1 Operators and Relations...2-18 by Compusult Limited 1998-2003 - Document No. 901-003 iii

CHAPTER 3 Installing Meta Manager 3-1 3.1 Overview Of Meta Manager Components...3-1 3.2 Microsoft Windows Installation Instructions...3-1 3.2.1 Meta Manager Server Installation Instructions for Microsoft Access...3-1 3.2.1.1 Before You Begin Installing...3-1 3.2.1.1.1 Software Items...3-1 3.2.1.1.2 Hardware and Firmware Items...3-2 3.2.1.2 Procedure...3-2 3.2.2 Meta Manager Server Installation Instructions for Oracle...3-2 3.2.2.1 Before You Begin Installing...3-2 3.2.2.1.1 Software Items...3-3 3.2.2.1.2 Hardware and Firmware Items...3-3 3.2.2.2 Procedure...3-3 3.2.3 Meta Manager Server Installation Instructions for SQL Server...3-4 3.2.3.1 Before You Begin Installing...3-4 3.2.3.1.1 Software Items...3-4 3.2.3.1.2 Hardware and Firmware Items...3-5 3.2.3.2 Procedure...3-5 3.2.4 Meta Manager Administrator Installation Instructions...3-5 3.2.4.1 Before You Begin Installing...3-5 3.2.4.1.1 Software Items...3-6 3.2.4.1.2 Hardware and Firmware Items...3-6 3.2.4.2 Procedure...3-6 3.3 UNIX Installation Instructions for Oracle...3-6 3.3.1 Before You Begin Installing...3-7 3.3.1.1 Software Items...3-7 3.3.1.2 Hardware and Operating System...3-7 3.3.2 Procedure...3-7 3.3.3 Removal of Meta Manager from Your System...3-10 3.4 Unix Installation Instructions for Sybase...3-10 3.4.1 Before You Begin Installing...3-10 3.4.1.1 Software Items...3-11 3.4.1.2 Hardware and Operating System...3-11 3.4.2 Procedure...3-11 3.4.3 Removal of Meta Manager from Your System...3-14 by Compusult Limited 1998-2003 - Document No. 901-003 iv

CHAPTER 4 Meta Manager Server 4-1 4.1 Meta Manager Server on Windows NT 4.0 or Higher...4-3 4.1.1 Starting the Meta Manager YAZ Z39.50 Server...4-3 4.1.2 Stopping the Meta Manager YAZ Z39.50 Server...4-3 4.2 Meta Manager Server on UNIX...4-4 4.2.1 Starting the Meta Manager Server on UNIX...4-4 4.2.2 Stopping the Meta Manager Server on UNIX...4-4 CHAPTER 5 Meta Manager Administrator 5-1 5.1 First-Time Use of the System...5-1 5.1.1 Configuring the Master Collection...5-3 5.2 Mapping Data to the Metadata Standard...5-4 5.2.1 Creating a New Data Collection...5-4 5.2.2 Adding Tables to a Collection...5-6 5.2.2.1 Adding Tables to the Meta Manager Database (MS Access)...5-6 5.2.2.2 Adding Tables to the Meta Manager Database (Oracle, Sybase and SQL Server)5-8 5.2.3 Creating Table Relationships...5-9 5.2.4 Configuring/Editing a Data Collection...5-12 5.2.4.1 Mapping Elements in a Collection Using Database Values...5-13 5.2.4.2 Mapping Elements in a Collection Using Fixed Values...5-15 5.2.4.3 Mapping Elements in a Collection Using GCMD Keywords...5-16 5.3 Defining Search Parameters...5-18 5.3.1 Search Parameters for Simple Elements...5-18 5.3.2 Search Parameters for Compound Elements...5-18 5.4 Copying a Collection...5-21 5.5 Importing a Data Collection...5-21 5.6 Globally Renaming Tables in a Data Collection...5-23 5.7 Deleting a Collection...5-23 5.8 Collection Properties...5-24 5.9 Metadata Mapping Reports...5-25 5.10 Syntax Checker...5-26 5.10.1 Add New SQL Functions...5-26 5.10.2 Edit SQL Functions...5-27 5.11 Server Parameters...5-28 5.11.1 Adding a New Server...5-28 5.11.2 Editing or Deleting an Existing Server...5-30 5.12 Licence Information...5-31 by Compusult Limited 1998-2003 - Document No. 901-003 v

CHAPTER 6 Tutorial 6-1 6.1 Lesson 1 - Verifying Your Installation...6-3 6.1.1 What Did You Do...6-5 6.1.2 What Did You Learn...6-5 6.2 Lesson 2 - Connecting and Testing Your Server with a Compusult Gateway...6-6 6.2.1 What Did You Do...6-12 6.2.2 What Did You Learn...6-13 6.3 Lesson 3 - Configuring the Master Meta Manager Collection...6-14 6.3.1 What Did You Do...6-18 6.3.2 What Did You Learn...6-19 6.4 Lesson 4 - Creating a New Meta Manager Collection...6-20 6.4.1 What Did You Do...6-22 6.4.2 What Did You Learn...6-22 6.5 Lesson 5 - Configuring a Meta Manager Collection for Enhanced Text Searching...6-23 6.5.1 What Did You Do...6-24 6.5.2 What Did You Learn...6-24 6.6 Lesson 6 - Creating Database Table Relationships...6-25 6.6.1 What Did You Do...6-27 6.6.2 What Did You Learn...6-28 6.7 Lesson 7 - Configuring a New Meta Manager Collection...6-29 6.7.1 What Did You Do...6-38 6.7.2 What Did You Learn...6-39 6.8 Lesson 8 - Mapping Compound Elements Using Search Overrides...6-40 6.8.1 What Did You Do...6-45 6.8.2 What Did You Learn...6-45 6.9 Lesson 9 - Globally Changing Data Element Mappings...6-46 6.9.1 What Did You Do...6-46 6.9.2 What Did You Learn...6-46 6.10 Lesson 10 - Executing the Meta Manager Report...6-47 6.11 Lesson 11 - Configuring the Windows NT/2000 Meta Manager Server Registry...6-48 6.11.1 What Did You Do...6-49 6.11.2 What Did You Learn...6-49 CHAPTER 7 Troubleshooting Tips 7-1 7.1 Server Tips...7-1 7.2 Administrative Interface Tips...7-2 by Compusult Limited 1998-2003 - Document No. 901-003 vi

CHAPTER 1 Introduction 1.1 Audience This document is written for users of Meta Manager, Version 4. With Meta Manager, providers of SQLbased geospatial data holdings can map their SQL-based geospatial metadata to a metadata standard and enable access to the database using standard Z39.50 client/server software. 1.2 Definitions, Acronyms and Abbreviations ANSI - American National Standards Institute AVHRR - Advanced Very High Resolution Radiometer CEONet - Canadian Earth Observation Network CNIDR - Center for Networked Information Discovery & Retrieval FGDC - Federal Geographic Data Committee GCMD - Global Change Master Directory GEO - Geographic GILS - Global Information Locator Service GRS - Generic Record Syntax HRV - High Resolution in the Visible HTML - HyperText Markup Language HTTP - Hyper Text Transfer Protocol LANDSAT - Land Satellite NISO - National Information Standards Organization NSDI - National Spatial Data Infrastructure ODBC - Open Database Connectivity RDBMS - Relational Database Management System SGML - Standard Generalized Markup Language SQL - Structured Query Language SUTRS - Simple Unstructured Text Record Syntax TCP/IP - Transmission Control Protocol/Internet Protocol TM - Thematic Mapper by Compusult Limited 1998-2003 - Document No. 901-003 1-1

Introduction URL - Uniform Resource Locator USMARC - United States Machine Readable Cataloging WRS - World Referencing System WWW - World Wide Web XML - Extensible Markup Language 1.3 Purpose Meta Manager supports mapping of RDBMS holdings to various metadata standard profiles. Currently, Meta Manager supports search and retrieval of metadata entries and related data sets using the GEO and GILS Profiles. Meta Manager can also be configured to support other metadata standards such as the National Biological Information Infrastructure (NBII) Profile. In the Internet environment, the server component of Meta Manager acts primarily as a direct access point to information stored within SQL databases. These databases can then be accessed through a compliant Z39.50 client. This document was written as a reference/instructional guide to the use of Meta Manager. 1.4 Meta Manager Operation Meta Manager is intended to be used in operational environments that wish to promote and provide access to geomatics data and/or metadata as well as global information resources. These environments include: education, government and private industry. 1.5 Systems and Network Infrastructure Systems and network infrastructure will vary, depending upon the organization using Meta Manager. Implementers of the system must provide a UNIX-based server utilizing either SUN Solaris, DEC OSF, LINUX, or IRIX, or Microsoft Windows NT 4.0 or higher. Server sites must be connected to the Internet via a dedicated, high-speed data connection. Organizations having firewall or security restrictions on direct Internet connections may choose to select one of the following options: 1. Allow restricted Z39.50 traffic through the firewall to the Meta Manager server. 2. Position a server containing a mirrored copy of the SQL database (including all metadata, data, and Metadata Standard mappings) outside the firewall. 3. Position a Meta Manager server outside the firewall and allow SQL*Net/ODBC read-only access through the firewall. Meta Manager is searched using a Z39.50 client (usually a WWW Browser) on a personal computer or workstation. The Meta Manager Server must be registered in a clearinghouse with an appropriate client to by Compusult Limited 1998-2003 - Document No. 901-003 1-2

Introduction enable users to search the metadata holdings. Administrators have the option of creating their own Clearinghouse using a product such as CNIDR s Stateful Gateway, Version 2 (downloadable from http:// www.cnidr.org) or using an existing clearinghouse such as the one provided by the Canadian Earth Observation Network (CEONet located at http://ceonet.ccrs.nrcan.cg.ca), or the Federal Geographic Data Committee (NSDI located at http://www.fgdc.gov/clearninghouse/clearinghouse.html). Option 1: Restricted Z39.50 Traffic SQL Server Option 2: Metadata Updates Snap Shots Firewall External SQL Metadata Meta Manager Server Firewall Internet Option 3: SQL*Net/ODBC Access Firewall Meta Manager Server FIGURE 1 External Access 1.6 Meta Manager Components Meta Manager will interface with an existing SQL RDBMS and is comprised of the following three components: An install script for installation of Meta Manager. The install script prompts the user for configuration information regarding the targeted platform. Once the information has been entered and verified by the user, the script will proceed to perform the installation of all components. A de-install module is included with the installation script to allow users to remove Meta Manager and its associated components. An administration application for Microsoft Windows that maintains metadata mappings and configuration within the SQL RDBMS. This application provides users with a standard method of making their system catalogs and data holdings available, as desired, to the client. It contains all of the facilities necessary for mapping the internal SQL database to the selected metadata standard. Server software, an extension of the Z39.50 server, is provided. The server side acts primarily as a direct access point to information stored within relational metadata databases. These databases can then be accessed through a GEO-compliant client without changing the internal dictionaries and definitions of the target database. The communication taking place between the server and the client application is precisely defined within the Z39.50 protocol. by Compusult Limited 1998-2003 - Document No. 901-003 1-3

Introduction 1.7 How to Use This Manual The various sections of this document contain the following information: Chapter 1 An alphabetical listing of acronyms and abbreviations that may be unfamiliar to users; an overview of systems and network options; Meta Manager components; conventions used within this manual; and, instructions for reporting problems with Meta Manager. Chapter 2 An overview of the FGDC and GILS Metadata Profiles and Z39.50 standards and the GEO profile combined view. Chapter 3 Detailed instructions for installing or de-installing Meta Manager. Chapter 4 An overview of the YAZ Z39.50 server software. Chapter 5 An overview of Meta Manager functionality. Chapter 6 A tutorial guide to the use of Meta Manager. Chapter 7 Meta Manager troubleshooting tips. 1.8 Conventions This manual uses the following typographical conventions: Boldfaced strings represent literals that should be typed exactly as they appear, or menu items that should be selected. Italicized strings represent variable information to be provided by the user. An ellipsis (...) indicates that additional arguments are optional. <Key> represents a key on the keyboard. by Compusult Limited 1998-2003 - Document No. 901-003 1-4

CHAPTER 2 The Z39.50 Protocol and Associated Profiles Meta Manager provides a complete solution for creating and defining new and/or mapping existing geospatial metadata definitions and geospatial datasets according to Metadata standards, based on the Z39.50 search and retrieval protocol. The Meta Manager software can interface with target information that is managed by Relational Database Management Systems (RDBMS) which contain the spatial data and attribute information. Both client and server applications utilize ODBC drivers that allow connectivity to the database. These include: Oracle; Microsoft Access; and, Microsoft SQL Server. In essence, the Meta Manager software enables suppliers with holdings maintained within relational databases to become suppliers with direct interoperability to other suppliers and clients on the Internet. Once connected to a supplier, users supported by appropriate clients, which understand the metadata profile being used, may navigate through the holdings. Meta Manager suppliers support searching and browsing of their holdings. 2.1 The Z39.50 Protocol Much of the following material was extracted from a Z39.50 brochure which can be viewed in its entirety at: http://www.cni.org/pub/niso/docs/z39.50-brochure/ ANSI/NISO Z39.50 is the American National Standard Information Retrieval Application Service Definition and Protocol Specification for Open Systems Interconnection. The National Information Standards Organization (NISO), an American National Standards Institute (ANSI) accredited standards developer that serves the library, information, and publishing communities, approved the original standard in 1988 (referred to as Z39.50-1988 or Version 1). NISO published a revised version of the standard in 1992 (referred to as Z39.50-1992 or Version 2). ANSI/NISO Z39.50 defines a standard way for two computers to communicate for the purpose of information retrieval. Z39.50 makes it easier to use large information databases by standardizing the procedures and features for searching and retrieving information. Specifically, Z39.50 supports information retrieval in a distributed, client and server environment where a computer operating as a client submits a search request (i.e., a query) to another computer acting as an information server. Software on the server performs a search on one or more databases and creates a result set of records that meet the criteria of the search request. The server returns records from the result set to the client for processing. The by Compusult Limited 1998-2003 - Document No. 901-003 2-1

The Z39.50 Protocol and Associated Profiles power of Z39.50 is that it separates the user interface on the client side from the information servers, search engines, and databases. Z39.50 provides a consistent view of information from a wide variety of sources, and it offers client implementors the capability to integrate information from a range of databases and servers. ANSI/NISO Z39.50 can be implemented on any platform. This means that Z39.50 enables different computer systems -- with different operating systems, hardware, search engines, database management systems -- to interoperate and work together seamlessly. A Z39.50 implementation enables one interface to access multiple systems providing end users with nearly transparent access to other systems. Users access multiple systems with the familiar commands and displays of their own local systems. New commands and search techniques do not have to be learned. The results of the search are presented on the local system -- again, in the formats and styles users are accustomed to. One of the strengths of ANSI/NISO Z39.50 is that it is an American National Standard. NISO developed and maintains Z39.50 using consensus procedures approved by ANSI, the principal coordinator of voluntary standardization in the United States. Z39.50 is not a proprietary standard and will continue to be responsive to the needs of the implementors that use the standard and the information consumers that benefit from its implementation. 2.1.1 A Brief History of Z39.50 Computers and telecommunications networks offer the potential to share data in electronic format. The challenge has been to develop a mechanism that would standardize communication between existing computer systems. NISO responded to this challenge by establishing a Standards Committee in 1979 to work on an information retrieval protocol. This work culminated in Z39.50-1988. Also beginning in the late 1970s funding by the Council on Library Resources (CLR) supported the development of an experimental protocol as part of the Linked System Project (LSP) for searching bibliographic databases and transferring records among the Library of Congress, the Online Computer Library Center (OCLC), the Research Libraries Group (RLG), and the Washington (now Western) Library Network (WLN). This Linked Systems Protocol laid the groundwork for the Z39.50 protocol. Shortly after the approval of the standard in 1988, a group of Z39.50 implementors began work to enhance and expand the utility of the standard. NISO balloted a revised version of Z39.50 in 1992. Continuing development of the standard by implementors has resulted in the third version of the standard (Draft Version 3). Work in the ISO on information retrieval standards resulted in ISO approval in 1991 of two International Standards that are companions to Z39.50: ISO 10162, Search and Retrieve Application Service Definition and ISO 10163-1, Search and Retrieve Protocol Specification. ANSI/NISO Z39.50-1992 harmonized the U.S. standard and the international standards so that the U.S. standard became a compatible superset of the International Standards. In early 1994, international standards developers made a crucial decision to begin the process of adopting Z39.50 as the International Standard. No longer will there be different national and international standards that must be harmonized. Rather, Z39.50 will provide the basis for the International Standard for information retrieval. by Compusult Limited 1998-2003 - Document No. 901-003 2-2

The Z39.50 Protocol and Associated Profiles 2.1.2 What Does Z39.50 Do? Z39.50 recognizes that information retrieval consists of two primary components -- selection of information based upon some criteria and retrieval of that information, and it provides a common language for both activities. Z39.50 standardizes the manner in which the client and the server communicate and interoperate even when there are differences between computer systems, search engines, and databases. Z39.50 is an applications-layer protocol originally modelled within the Open Systems Interconnection (OSI) Basic Reference Model developed by the International Organization for Standardization (ISO). Applications-layer protocols support the communications requirements of and interact directly with computer programs residing on clients and servers that perform specific operations. Indeed, as an applications-layer protocol, Z39.50 has proven largely independent of the transport mechanisms that underlie it. Z39.50 is now widely used in the Internet environment over the Transmission Control Protocol/Internet Protocol (TCP/IP) transport service. Distributed client/server architecture provides the foundation for Z39.50 communication and information retrieval specifications. Software for end-user interaction and display (the client) is separate from the software that manages the information, performs the search, and returns the results (the server). Z39.50 does not address the user interface (e.g., its look and feel ), but there are protocol specifications and procedures that pertain to the Z39.50 client (referred to in the standard as the Z39.50 origin ) such as its initiation of an information retrieval query and how it requests specific operations from the server. There are also protocol specifications and procedures that pertain to the Z39.50 server (referred to in the standard as the Z39.50 target ) such as its manipulation of results sets and the formats in which it returns records to the client. A series of messages passing between the client and server (defined by what the standard calls the Initialization Facility) establish a connection, initiate a Z39.50 session, and negotiate expectations and limitations on the activities that will occur (e.g., maximum size of the records that will be transferred from the server to the client, the version of the protocol supported, etc.). After these agreements are negotiated, the client may submit a query. The Z39.50 client translates the query into a standardized representation and passes it to a Z39.50 server (defined by the Search Facility). The server executes the search against a database(s), and a result set is created. The client can then ask for records from the result set or request from the server additional processing of the result set (defined by the Retrieval Facility). Upon receipt of the records, the client may process the records and display records to the user. The extent to which a client can perform additional processing on retrieved records (e.g., combining records from several separate searches) will depend on the user interface software since it is separate from the Z39.50 client software. Each database residing on information servers can have unique characteristics. For example, databases may differ in the way they store data and in the access points available for searching. The records in each of the databases may also have different structures and consist of different data elements. The objective of Z39.50 is to support computer-to-computer communication in standard and mutually understandable terms and support the transfer of data between the systems independent of the structure, content, or format of the data in a particular system. However, in individual implementations, servers may be limited to specific formats of data that can be exported and the access points that are supported for searching. by Compusult Limited 1998-2003 - Document No. 901-003 2-3

The Z39.50 Protocol and Associated Profiles 2.1.2.1 Searching a Database When a database is searched, the client passes a query to the server. The query contains search terms (e.g., terms that the user has identified to be matched against access points in the database) and attributes of those search terms (e.g., specifying the terms as an author or title, specifying if the terms are to be truncated, etc.). Queries can include different attribute types. For example, if a user wants to search for an author's name, a use attribute specifies the search term as author. If the user wants to search for all books published after a certain date, a use attribute specifies the search term is a date of publication and a relation attribute specifies that the user wants all dates of publication greater than a particular date. ANSI/NISO Z39.50 enumerates these attribute types and their values in registered attribute sets. Standardized and mutually recognized attribute sets allow implementors a common basis for intersystem communication. After the server executes a search of a database, the server creates a result set consisting of those records that match the criteria of the query. Clients can request that servers return those records from a result set, or they can issue additional searches that further qualify a result set or use result sets as arguments in subsequent searches. 2.1.2.2 Retrieving Records from a Database When the user wants to display records listed in the result set, ANSI/NISO Z39.50 provides choices about which data elements (i.e., element sets) from the database record the user can request. It also gives choices about the format for transferring the record (i.e., a record syntax) from the server to the client. Z39.50 registers standardized element set names and record syntaxes to support client/server communication for this aspect of information retrieval. 2.1.3 Using Z39.50 Over the Internet Originally developed for use in computer communications networks using Open Systems Interconnection (OSI) protocols, ANSI/NISO Z39.50 is now successfully operational in the environment of the Internet. In 1992, a group of implementors (sponsored by the Coalition for Networked Information) established the Z39.50 Interoperability Testbed (ZIT) to make Z39.50 implementations work over the Internet, and to identify and address issues of interoperability among Z39.50 implementations. Interoperability testing of various Z39.50 implementations through the ZIT made it clear that the transport services (i.e., the Transmission Control Protocol/Internet Protocol [TCP/IP]) of the Internet could be used successfully for the protocol. Using Z39.50 over the Internet is a major step forward. The Internet is a widely deployed network of networks connecting several million host computers and millions of users worldwide. The protocol suite that supports the Internet (i.e., TCP/IP) is readily available and used; it is a ubiquitous connectivity tool. The Internet is home to massive stores of key information resources and connects millions of users that need to access those resources. Awareness of the protocol by individuals and organizations is increasing because of the many operational Z39.50 implementations now used for information retrieval. While the standard had its origins in the bibliographic community of libraries and bibliographic utilities, the increasing awareness by other communities is sparking new Z39.50 initiatives. The following shows the range of applications for which Z39.50 may be used: by Compusult Limited 1998-2003 - Document No. 901-003 2-4

The Z39.50 Protocol and Associated Profiles The Government Information Locator Service (GILS) is intended to help the public locate and access information throughout the U.S government. GILS will use Z39.50 to provide a seamless connection between distributed GILS servers. The Consortium for the Computer Interchange of Museum Information (CIMI) is examining Z39.50 to assist CIMI in its goals of developing museum resources on digital networks and assuring standards-based open interchange of museum information. National Spatial Data Infrastructure is a Federal initiative established for the discovery and retrieval of geospatial data. A technical working group is developing a Z39.50 attribute set for spatial query and retrieval of spatially referenced data and documents. The Canadian Earth Observation Network (CEONet) is an initiative by the Canadian government to create a national infrastructure for providing access to Earth Observation (EO) archives and other complementary spatial databases. Z39.50 Gateways for World Wide Web and Gopher enable the users of these two popular network tools to search Z39.50 servers. The 1992 publication of Version 2, the new features in the Draft Version 3, the interoperability testbed and its confirmation that the protocol works effectively in the Internet, solid experience by Z39.50 developers and implementors, and increased awareness by information providers and consumers are focusing attention on the central role of Z39.50 for information retrieval in the national and global information infrastructure. 2.1.4 The Clearinghouse Concept The Z39.50 protocol is based upon the Clearinghouse concept. by Compusult Limited 1998-2003 - Document No. 901-003 2-5

The Z39.50 Protocol and Associated Profiles? Decentralized Searchable Servers Containing Metadata and/or Data FIGURE 2 Clearinghouse Overview The diagram illustrated above illustrates a decentralized system of searchable Internet servers containing structured metadata and data where each server is a peer in the network. Searching for information based on geographic location in traditional library information systems has been relegated to geographic classification codes and, for cataloged maps, a coordinate reference. The ability to provide searchable geographic characteristics of mapped and non-map-related holdings can be provided through a set of extended geographic coordinates associated with the holdings. These coordinates, when understood as part of a searchable attribute set within the Z39.50 information retrieval standard, provide a new and consistent way to search and retrieve data/metadata based on geography. by Compusult Limited 1998-2003 - Document No. 901-003 2-6

The Z39.50 Protocol and Associated Profiles 2.2 What is a Profile? A Profile is the statement of function(s) and the environment within which it is used, in terms of a set of one or more standards, and where applicable, identification of chosen classes, subsets, options, and parameters of those standards. It is a set of implementor agreements providing guidance in applying a standard interoperably in a specific limited context. Meta Manager currently provides support for the following two profiles: The GEO Profile, which is implemented by integrating the Federal Geographic Data Committee (FGDC) metadata standard and the ANSI Z39.50 information retrieval standard. The GEO Profile can be viewed at: http://www.blueangeltech.com/standards/geoprofile/geo22.htm The GILS (Global Information Locator Service) profile. One of the roots of GILS is in the Global Change Research Program, where the focus is on the global information infrastructure needed for long-term access to environmental data and information. This work provided a base for a Government Information Locator Service initiative in the United States. As this was developing, a Global Information Society initiative began under the auspices of the G7. Within the G7 initiative, the U.S. led a project on Environment and Natural Resources Management with a goal to gain consensus on a Global Information Locator Service. The consensus reached was to employ the GILS Profile. From the perspectives of standards and technology, the Global Information Locator Service is no different than the Government Information Locator service. More information on GILS can be viewed at: http://www.gils.net Each of these profiles is described next. 2.2.1 The GEO Profile Some of the following material for the GEO Profile was extracted from Version 2.2 of the Z39.50 Application Profile for Geospatial Metadata or GEO. Last updated on May 27, 2000, the complete profile can be viewed at: http://www.blueangeltech.com/standards/geoprofile/geo22.htm The GEO Profile is a geospatial metadata infrastructure that provides data suppliers with the means to: document existing data holdings using a well-defined standard; support discovery of existing data sets that are maintained in discrete catalogs by disparate organizations; and, provide detailed lineage and background information to accompany a data transfer. This GEO Profile is implemented by integrating the FGDC metadata standard and the ANSI Z39.50 information retrieval standard. by Compusult Limited 1998-2003 - Document No. 901-003 2-7

The Z39.50 Protocol and Associated Profiles 2.2.1.1 What is the FGDC Metadata Standard In the United States, the National Spatial Data Infrastructure (NSDI) encompasses policies, standards, and procedures for organizations to cooperatively produce and share geospatial data. The Federal Geographic Data Committee (FGDC) has assumed leadership in the evolution of the NSDI in cooperation with state and local governments, academia and the private sector in the US. The FGDC Standards Working Group (SWG) has developed the FGDC Standards Reference Model that provides guidance to the FGDC Subcommittees and Working Groups on standards development. The model defines the expectations of FGDC standards, describes different types of geospatial standards and documents the FGDC standards process. The standard provides specifications for: terminology of data elements and compound elements; definitions for this terminology; and, information about values to be provided for the data elements. The standard also provides information about terms that are: mandatory; mandatory under certain conditions; and, optional (provided at the discretion of the data provider). 2.2.1.2 Z39.50 Specifications for GEO At a minimum, GEO clients and servers must support Z39.50 Version 2 as specified in Z39.50-1995. GEO requires support for the objects listed below, some of which are not defined in Z39.50-1995. No Version 3 services are required for implementation of the GEO Profile. Several object classes are assigned at the level immediately subordinate to ANSI-standard-Z39.50, including: 3 = attribute set definitions 4 = diagnostic definitions 5 = record syntax definitions 13 = database schema definitions. GEO requires support of the following objects: Bib-1 Diagnostic Set {ANSI-standard-Z39.50 4 1} Bib-1 Attribute Set {ANSI-standard-Z39.50 3 1} GILS Attribute Set {ANSI-standard-Z39.50 3 5} GEO Attribute Set {ANSI-standard-Z39.50 3 9} GEO Schema {ANSI-standard-Z39.50 13 4} by Compusult Limited 1998-2003 - Document No. 901-003 2-8

The Z39.50 Protocol and Associated Profiles GRS-1 Record Syntax {ANSI-standard-Z39.50 5 105} HTML Record Syntax {ANSI-standard-Z39.50 5 109 3} SUTRS Record Syntax {ANSI-standard-Z39.50 5 101} XML Record Syntax {ANSI-standard-Z39.50 5 109 10} and optional support of the following objects: SGML Record Syntax {ANSI-standard-Z39.50 5 109 9} USMARC Record Syntax {ANSI-standard-Z39.50 5 10} 2.2.1.3 Z39.50 Services There are three Z39.50 (Version 2) services that are required for conformance: Init, Search, and Present. No additional services are required for conformance to the GEO Profile. Other Z39.50 services, however, may be provided optionally by servers and used by clients. Standard Z39.50 Init Service negotiation procedures control the use of all services. In addition, GEOconformant clients and servers must specify the implementation id, name, and version within the Z39.50 Init Service. 2.2.1.3.1 Search GEO clients and servers are required to support the Z39.50 Type-1 query. Support for the Boolean operators AND, OR, and AND-NOT is also required. GEO servers should expect to process queries consisting of Boolean combinations of textual, temporal, and spatial search terms. Attribute Set The GEO Profile requires clients and servers to support the GEO Attribute Set. The GEO Attribute Set is a registered object with an Attribute Set OID of {ANSI-standard Z39.50 3 9}. GEO servers must also support the Bib-1 and GILS Attribute Sets to a limited extent. That is, GEO servers must recognize the Bib-1 and GILS Attribute Sets to the extent that a Bib-1 or GILS client may pass the Attribute Set OID in a query and a GEO server may receive and process a query with the OID. The GEO Attribute Set imports the Use, Structure, Relation, and Truncation Attribute Types from the Bib-1 Attribute Set. In addition, the GEO Attribute Set imports selected Attributes from the Bib-1 and GILS Attribute Sets, where the semantic meaning is equivalent. Thus, search of GEO servers on common Bib-1 Attributes by clients familiar with Bib-1 should be successful. The GEO Profile defines additional Use, Structure, and Relation Attributes to facilitate the searching of geographic and spatial information. Each Use Attribute defined in the GEO Attribute Set corresponds in name and semantics to a record element of the GEO Schema. GEO Servers are required to support a mandatory set of attribute combinations from the GEO Attribute Set as specified in Annex B. GEO servers are required to recognize the attribute combination, and a search must always result in a valid result set (which could contain zero records). GEO servers should never by Compusult Limited 1998-2003 - Document No. 901-003 2-9

The Z39.50 Protocol and Associated Profiles return any of the following Bib-1 diagnostics when a query includes the mandatory attribute combinations: Unsupported Attribute Type (113) Unsupported Use Attribute (114) Unsupported Relation Attribute (117) Unsupported Structure Attribute (118) Unsupported Attribute Combination (123) When a GEO server receives a query term containing attribute types, values, or combinations that are not supported by the server, the server should fail the search (search status = failure) and return an appropriate Bib-1 diagnostic. If other terms in the query can be processed by the server, the server may also indicate that a subset of search results is available (result set status = subset). A GEO server may, if appropriate to its database, support additional attribute types, values, and combinations from the GEO Attribute Set. 2.2.1.3.2 Retrieval This section describes the components and procedures used by Z39.50 to return records in response to a query. Schema The GEO Profile specifies a GEO Schema (see Annex C). The GEO Schema is a registered object with an OID of {ANSI-standard-Z39.50 13 4}. A schema in Z39.50 can be modified and may evolve over time, and it is reasonable to expect the GEO Schema will evolve. Element Sets GEO servers are required to support three element set names: B (Brief), S (Summary) and F (Full). GEO servers will interpret the use of the element set names to identify the following elements from the GEO Schema (marked with their SGML tags in parentheses): B: includes the Title element. S: includes the following elements: Title, Online Linkage, Bounding Coordinates, Extent, Publication Date, Beginning Date, Ending Date, Browse Graphic, Entity Type Label, Attribute Label, and Data Set G-Polygon. The Browse Graphic should appear as groups of Browse Graphic File Name, Browse Graphic File Description, and Browse Graphic File Type. F contains all elements available in the record. The server should include in the retrieved record all of the elements for which there is data available in the database record and which can be encoded in the requested record syntax (e.g., some type of locally-defined binary data may not be encodable in a USMARC or SUTRS record). Optionally, servers may support additional element set names, including: A: includes the Title and Abstract elements by Compusult Limited 1998-2003 - Document No. 901-003 2-10

The Z39.50 Protocol and Associated Profiles A GEO server is required to return the following diagnostic from the Bib-1 Diagnostic Set when it receives a request for an element set name that is not supported by the server: Element Set Name Not Valid (25) Record Syntaxes The GEO Profile requires support for the following Record Syntaxes: GRS-1 can be used to encapsulate more complex bundles of information including images, related documents, video, or other ancillary information for further processing by the client. GRS-1 could also be used to encapsulate an Entry in SGML along with the reference to, or even inclusion of, a DTD. GRS-1 is defined in Z39.50. HTML is used to obtain a GEO Entry that is formatted by the server for eventual display by a Web browser. SUTRS is used to display a GEO Entry in simple text. SUTRS is defined in Z39.50. XML can be used to exchange GEO Entries between servers or for loading into a metadata editor or presentation system for further processing. For GEO Entries in HTML and SUTRS Record Syntaxes, it is recommended that GEO servers follow the guidelines outlined for the preferred display format. HTML is the default Record Syntax to return when the client has not specified a preferred record syntax. For purposes of interoperability, servers may support other record syntaxes including: SGML, which can be used to exchange GEO Entries between servers or for loading in a metadata editor or presentation system for further processing; and, USMARC: The element of a GEO Entry can be mapped into USMARC using a formal mapping of the FGDC Content Standards for Digital Geospatial Metadata to USMARC. When a GEO-conformant server is unable to return a record in the requested record syntax, the server should return an appropriate diagnostic from the Bib-1 Diagnostic Set, such as: Record Not Available in Requested Syntax (238) Record Syntax Not Supported (239) 2.2.2 The GILS Profile The following material was extracted from Version 2 of Application Profile for the Global Information Locator Service (GILS). The complete profile, last updated on November 24, 1997, can be viewed at: http://www.gils.net/prof_v2.html The GILS profile was a response to the need for users to identify, locate, and access or acquire publicly available Federal information resources, including electronic information resources. by Compusult Limited 1998-2003 - Document No. 901-003 2-11

The Z39.50 Protocol and Associated Profiles The current GILS initiative builds upon a previous study, which was conducted for the Office of Management and Budget, the National Archives and Records Administration, and the General Services Administration. The study recommended that each agency establish a network-accessible locator that describes its information resources. The study also recommended that agencies use Z39.50 as the appropriate information retrieval protocol to achieve a distributed, standards-based Government Information Locator Service. The GILS Profile resulted from the work of a group comprising experts in Z39.50 implementations, system implementations, and information organization, and representatives of Federal agencies. The specifications included in the GILS Profile reflect the consensus of this group and input from a range of stakeholders. The GILS Profile fully specifies the use of ANSI/NISO Z39.50 by the GILS. In addition, the GILS Profile provides the specifications for the overall GILS application relating to the GILS Core including other aspects of GILS-conformant servers that are outside the scope of Z39.50. The current version of the GILS Profile focuses on requirements for a GILS server operating in the Internet environment. GILS clients will be able to interconnect with any GILS server, and these clients will behave in a manner that allows interoperability with the GILS server. Clients that support Z39.50 but do not implement the GILS Profile will be able to access GILS records with less than full GILS functionality. The GILS Profile addresses many aspects of the GILS (e.g., intersystem interactions and information interchange) but does not specify user interface requirements, the internal structure of databases that contain GILS Locator Records, or search engine functionality. The GILS Profile supports search and retrieval of GILS Locator Records contained in GILS servers by users in the Internet environment. A GILS server accessed using Z39.50 in the Internet environment acts primarily as a pointer to information resources. Some of these information resources pointed to by GILS Locator Records, as well as the GILS server itself, may be available electronically through other communications protocols including the common Internet protocols that facilitate electronic information transfer such as remote login (Telnet), File Transfer Protocol (FTP), and electronic mail (SMTP/MIME). The use of these protocols or other communications paths is outside the scope of the GILS Profile. Once connected to a GILS server, users supported by appropriate clients that understand the GILS Profile may navigate through single or multiple servers. GILS servers will support searching (i.e., accept a search query and return a result set or diagnostic messages) and may support browsing (i.e., accept a well-known search query and return a list of Locator Records in brief display format). Although the GILS Profile addresses GILS servers only, it is understood that clients have roles in the execution of these activities (e.g., browsing is also a client function in the sense of how it interprets and presents GILS data). by Compusult Limited 1998-2003 - Document No. 901-003 2-12

The Z39.50 Protocol and Associated Profiles 2.2.2.1 What is the GILS Metadata Standard? GILS provides users with a means of finding information located in local and remote systems. Users find information by formulating system independent queries at the desktop and transmitting these to a remote database containing GILS records. The queries are presented to the remote database in an international standard language for information retrieval called Z39.50. The Z39.50 standard provides rules and procedures for the exchange of information between two systems independent of what hardware or software those systems run on. It allows users to search one or more databases and to receive a consolidated set of responses to each search query. Recognizing that Z39.50 implementations will not be prevalent at the user s desktop, government information providers typically provide a Web/Z39.50 gateway to this information service. These gateways include support for the Internet-HTTP standard, supported by World Wide Web browsers, and thereby provide access to information for anyone who has a Web browser. 2.2.2.2 Z39.50 Specifications for GILS GILS requires support of various objects, listed below. Several object classes are assigned at the level immediately subordinate to ANSI-standard-Z39.50, including: 3 = attribute set definitions 4 = diagnostic definitions 5 = record syntax definitions 13 = database schema definitions 14 = tagset definitions GILS requires support of the following objects: GILS attribute set {ANSI-standard-Z39.50 3 5} Bib-1 diagnostic set {ANSI-standard-Z39.50 4 1} USMARC record syntax {ANSI-standard-Z39.50 5 10} SUTRS record syntax {ANSI-standard-Z39.50 5 101} GRS-1 record syntax {ANSI-standard-Z39.50 5 105} GILS schema {ANSI-standard-Z39.50 13 2} tagset-m {ANSI-standard-Z39.50 14 1} tagset-g {ANSI-standard-Z39.50 14 2} by Compusult Limited 1998-2003 - Document No. 901-003 2-13

The Z39.50 Protocol and Associated Profiles 2.2.2.3 Z39.50 Services There are three Z39.50 (Version 2) services that are required for conformance: Init, Search, and Present. No additional services are required for conformance to the GILS Profile. Other Z39.50 services, however, may be provided optionally by servers and used by clients. Standard Z39.50 Init Service negotiation procedures control the use of all services. 2.2.2.3.1 Search The GILS application will support Z39.50 Type 1 queries which are general purpose Boolean query structures. Attribute Set The GILS Attribute Set is a superset of the Bib-1 Attribute set and consists of all Bib-1 Attributes and additional Use Attributes that are defined for GILS elements. The newly defined GILS Use Attributes are well-known and correspond semantically to GILS Core Elements. The GILS Attribute Set is a registered object. GILS servers must support a limited number of Use Attributes as follows. (Note: The Use Attribute name is listed followed by the Use Attribute number and the corresponding GILS element.) Use Attributes: Title (4, Title); Local Number (12; Local Control Number); Author-name corporate (1005; Originator); Date/Time Last Modified (1012; Date of Last Modification); Record Source (1019; Record Source); Distributor Name (2001; Distributor Name); Subject Terms Controlled (2002; Subject Terms Controlled); Local Subject Index (29; Subject Terms Uncontrolled); Any (1016), Anywhere (1035) Structure Attributes: Word (2), URx (104), Date (5), Word List (6) Relation Attributes: Less Than (1), Less Than or Equal (2), Equal (3), Greater Than or Equal (4), Greater Than (5), Not Equal (6) GILS servers should never return any of these four diagnostic messages: Unsupported Use Attribute, Unsupported Structure Attribute, Unsupported Relation Attribute, or Unsupported Attribute Type when a query includes the combinations of required GILS Attributes. GILS servers may optionally support a spatial search. For this purpose, the following attributes are available: Use Attributes: West Bounding Coordinate (2038); East Bounding Coordinate (2039); North Bounding Coordinate (2040); South Bounding Coordinate (2041) Structure Attribute: Coordinate (200) A server may support many different sets of records, only some of which might include some of the GILS Core Elements. When a query includes a Use Attribute which does not occur in the particular set of by Compusult Limited 1998-2003 - Document No. 901-003 2-14

The Z39.50 Protocol and Associated Profiles records to be searched, the server should not fail the search but should locate no records for that Use Attribute. Well-Known Search To provide support for browsing GILS Locator Records, there is a well-known search consisting of the following GILS Attributes: Use Attribute: Local Number; Structure Attribute: URX; and a term of zero length. GILS servers that support browsing of records will create a result set of one or more GILS Locator Records that provide the necessary information to allow clients to offer menu-like displays of GILS Locator Records or other information and information resources. The Browse in the GILS context involves only the Search and Present Services of Z39.50. Browse is used informally in the GILS Profile, and it is not related nor should it be confused with the Browse Facility or Scan Service of Z39.50. 2.2.2.3.2 Retrieval This section describes the components and procedures used by Z39.50 to return records in response to a query. Schema The GILS Schema is a registered object. The schema describes and/or defines tagsets used and an abstract record structure for a Locator Record. A schema in Z39.50 can be modified and may evolve over time, and it is reasonable to expect the GILS Schema will evolve. The GILS Schema uses elements from tagset-m, tagset-g and defines in a GILS tagset additional elements as necessary. The GILS Profile specifies tagtypes to identify tagset-m elements (tagtype = 1), tagset-g elements (tagtype =2), and the elements defined by the GILS tagset (tagtype = 4). Another tagtype (tagtype=3) is used to identify arbitrary string tags for locally defined elements. The GILS tagset element numbering begins with number 1. Elements can be nested and the tagging notation (i.e., the tag path) will reflect the nesting. All well-known GILS Schema elements have assigned numeric tags. String-tags (i.e., text) may be used in the GILS Schema to label those elements that are not well-known (i.e., locally defined). Element Sets Names GILS servers will support Element Sets Names. GILS servers will interpret the use of the Element Set Names required by the GILS Profile to identify the following elements from the GILS Schema: The primitive element set name G contains at least Title, Control Identifier, Originator, Local Control Number and Cross Reference Support for primitive element set name F, is required by the Z39.50 standard, however, its usage is not addressed by this profile, and its use, within this profile, is discouraged. by Compusult Limited 1998-2003 - Document No. 901-003 2-15

The Z39.50 Protocol and Associated Profiles The server should include in a retrieved record all of the elements specified by the element set name for which there is data available in the database record and which can be encoded in the requested record syntax (e.g., some types of locally defined binary data may not be encodable in a USMARC or SUTRS record). Record Syntaxes GILS servers are required to support the following three record syntaxes: USMARC -- an implementation of ANSI/NISO Z39.2 and maintained by the Library of Congress Generic Record Syntax (GRS-1) -- defined in Z39.50 Simple Unstructured Text Record Syntax (SUTRS) -- defined in Z39.50 The GILS Application Profile contains a mapping of Core Elements to USMARC for use in the USMARC record syntax. However, since the data transformation is not fully reversible and requires interpretation, the record source is responsible for encoding the USMARC record(s). The data in GILS Locator Records do not always map clearly into USMARC records, particularly when agencies add their own locally defined fields to the GILS Locator Record. This means that construction of USMARC records is subject to local interpretation. Therefore, GILS Locator Records in USMARC format obtained from other than the original record source should be considered non-definitive. The original source of the GILS Locator Record can be identified by examining the Original Control Identifier field of the record. For interchange, GRS-1 records are to be treated as the complete and canonical representation; SUTRS and USMARC should be viewed as derivative records from these canonical representations and as such are not as complete or precise. 2.2.3 Organization of Metadata Standards Metadata Standards are organized in a hierarchy of compound elements and data elements that define the information content for metadata to document a set of data. For the FGDC Metadata Standard, the starting point is metadata. The compound element metadata is composed of other compound elements representing different concepts about the data set. Each of these compound elements has a numbered section in the standard. In each numbered section, these compound elements are defined by other compound elements and data elements. The section contact information is a special section that specifies the data elements for contacting individuals and organizations. This section is used by other sections and is defined once for convenience. For example: Compound Element Metadata is composed of other Compound Elements: Identification Information Data Quality Information Spatial Data Organization Information Spatial Reference Information by Compusult Limited 1998-2003 - Document No. 901-003 2-16

The Z39.50 Protocol and Associated Profiles Compound Element Identification Information is composed of other Compound Elements: Citation Description Time Period of Content Status Compound Element Identification Information is also composed of Data Elements: Access Constraints Use Constraints Note: Data Elements constitute the lowest decomposition of a section of the standard. Each section begins with the name and definition of the compound element that defines the section. The name and definition are followed by production rules that define this compound element in terms of data elements, either directly or by the use of intermediate compound elements. Document Type Definition Element definitions are usually grouped into a formal specification for the structure of an SGML document which is known as a Document Type Definition. In technical documentation such as the FGDC Metadata report, it is essential that sections and subsections are appropriately nested and cross-references resolved. This permits the matching of metadata reports against predefined rule sets. The Document Type Definition for the FGDC GEO Profile can be viewed at http://www.fgdc.gov/ metadata/fgdc-std-001998.dtd. The Document Type Definition for the GILS Profile can be viewed at http://www.gils.net/list/xml.dtd. An image map of the content standard for the FGDC Metadata standard is shown in Figure 3. This map illustrates the top level of the FGDC Metadata Standard hierarchy. by Compusult Limited 1998-2003 - Document No. 901-003 2-17

The Z39.50 Protocol and Associated Profiles FIGURE 3 FGDC Metadata Standard Image Map Hierarchy 2.2.3.1 Operators and Relations Compound Elements A compound element is a group of data elements and other compound elements. All compound elements are described by data elements, either directly or through intermediate compound elements. Compound elements represent higher-level concepts that cannot be represented by individual data elements. The form for the definition of compound elements is identified as Compound element name -- definition. Type: compound where the type of compound uniquely identifies the compound elements in the lists of terms and definitions. Production Rules A production rule specifies the relationship between a compound element, its data elements and other (lower-level) compound elements. Each production rule has a left side (identifier) and a right side (expression) connected by the symbol =, meaning that the term on the left side is replaced by or produces the term on the right side. Terms on the right side are either other compound elements or by Compusult Limited 1998-2003 - Document No. 901-003 2-18

The Z39.50 Protocol and Associated Profiles individual data elements. By making substitutions using matching terms in the production rules, one can explain higher-level concepts using data elements. Data Elements A data element is a logically primitive item of data. The entry for a data element includes the name of the data element, the definition of the data element and a description of the values that can be assigned to the data element. The form for the definition of the data elements is: Data element name -- definition. Type: Domain: The information about the values for the data elements shall include a description of the type of the value and a description of the domain of the valid values. The type of the data element describes the kind of value to be provided. The valid choices for type of data element are integer for integer numbers, real for real numbers, text for ASCII characters, date for day of the year, and time for time of the day. The domain describes valid values that can be assigned to the data element. The domain may specify: a list of valid values; references to lists of valid values; or, restrictions on the range of values that can be assigned to a data element. The domain also may note that the domain is free from restrictions and any values that can be represented by the type of the data element can be assigned. Unrestricted domains are represented by the use of the word free followed by the type of the data element (that is, free text, free date, free real, free time, free integer). Some domains can be partly, but not completely, specified. by Compusult Limited 1998-2003 - Document No. 901-003 2-19

CHAPTER 3 Installing Meta Manager This section provides instructions for installing Meta Manager on Microsoft Windows and UNIX platforms, as well as procedures for configuring the application. 3.1 Overview Of Meta Manager Components A Meta Manager application consists of the following components. Data and Metadata - The data and metadata to be mapped, searched and published by Meta Manager. This component usually already exists. Meta Manager Database - The database tables that contain metadata and metadata mappings used internally by Meta Manager. The Meta Manager database facilitates the link between the Meta Manager Server, the data to be searched, and the metadata standard to which the data is mapped. Meta Manager Server - The Meta Manager Server accepts Z39.50 search requests. The server is configured to accept requests on a user-specified port, and to use a user-specified Meta Manager database to determine the mappings between the data to be searched and the metadata standard. Meta Manager Administrator - The Meta Manager Administrator is the tool used to update the Meta Manager database. It allows the user to define the mappings between the data and metadata and the desired metadata standard. 3.2 Microsoft Windows Installation Instructions 3.2.1 Meta Manager Server Installation Instructions for Microsoft Access 3.2.1.1 Before You Begin Installing Meta Manager needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following hardware and software sub-sections. 3.2.1.1.1 Software Items The following software items will be required: 1. Windows NT 4.0 or higher. 2. A Microsoft Access database. by Compusult Limited 1998-2003 - Document No. 901-003 3-1

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3. Meta Manager software for the target platform (downloadable from http:// www.metadatamanager.com). 4. A Z39.50 client such as CNIDR s Stateful Gateway (downloadable from http://www.cnidr.org). You can use the Meta Manager test gateway for testing access to your datasets. 5. Netscape Navigator or Microsoft Internet Explorer 3.2.1.1.2 Hardware and Firmware Items The following hardware will be required: 1. Pentium with 32 MB RAM plus 2 MB hard disk space. 3.2.1.2 Procedure 1. Download the Meta Manager Server installation software (available at http:// www.metadatamanager.com). You will be required to enter a username and password. The downloadable file is a self-extracting executable. 2. Double-click the self-extracting executable. The Meta Manager Server window will be displayed. The Install Shield Wizard will now guide you through the Meta Manager Server setup, prompting for answers in each screen. Respond by clicking the Next or Yes button. 3. Click Next to continue to the Choose Destination Location screen. To accept the default location folder (c:\program Files\Compusult Web Enterprise Suite\Meta Manager) click the Next button. To choose another location folder, click the Browse button, select another folder and click Next to continue. The setup procedure will now begin installation of the Meta Manager Server. 4. In the Meta Manager Install window, enter the Meta Manager Licence Key. This key is used by the server on start-up. A licence key can be obtained by contacting Compusult Limited at (709) 745-7914 or licence@compusult.nf.ca. Enter the ODBC DSN for the Meta Manager and Tutorial database files. Choose a Z39.50 Server Port number on which the server will listen for Z39.50 search requests. Enter the Instance Name of the server. This name will show up in the registry and in services under the control panel. 5. Click OK. Setup will resume installation of the Meta Manager Server. Click the Finish button and restart the computer. After restarting the computer, the server will be listening for requests on the chosen port. 3.2.2 Meta Manager Server Installation Instructions for Oracle 3.2.2.1 Before You Begin Installing Meta Manager needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following hardware and software sub-sections. by Compusult Limited 1998-2003 - Document No. 901-003 3-2

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3.2.2.1.1 Software Items The following software items will be required: 1. Windows NT 4.0 or higher. 2. An Oracle database. Prior to the installation of Meta Manager for Oracle, a database user must be created to contain the metadata used by the server. Meta Manager Oracle accounts should be created as follows: create user <username> identified by <password> default tablespace <default> temporary tablespace <temporary> quota unlimited on <default>; To apply the create table, view, index, sequence, cluster, session and db link options, enter the following: grant connect to <username>; To apply the create trigger, procedure, and other options not included in the grant connect command, enter the following: grant resource to <username>; If the demo/tutorial is to be installed, a separate database user must be created. Note that both database users must be accessible via the same Oracle connect string. 3. Meta Manager software for the target platform (downloadable from http:// www.metadatamanager.com). 4. A Z39.50 client such as CNIDR s Stateful Gateway (downloadable from http://www.cnidr.org). You can use the Meta Manager test gateway for testing access to your datasets. 5. Netscape Navigator or Microsoft Internet Explorer 3.2.2.1.2 Hardware and Firmware Items The following hardware will be required: 1. Pentium 32 MB RAM plus 20 MB hard disk space. 3.2.2.2 Procedure 1. Download the Meta Manager Server installation software (available at http:// www.metadatamanager.com). You will be required to enter a username and password. The downloadable file is a self-extracting executable. by Compusult Limited 1998-2003 - Document No. 901-003 3-3

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 2. Double-click the self-extracting executable. The Meta Manager Server window will be displayed. The Install Shield Wizard will guide you through the rest of the setup process. Continue to click the Next or Yes button at the bottom of the screens to proceed with the installation process. 3. Click Next to continue to the Choose Destination Location screen. You can select the default destination directory (c:\program Files\Compusult Web Enterprise Suite\Meta Manager) by clicking the Next button or you can select another folder by clicking the Browse button, selecting the desired folder, and clicking the Next button. The setup program will begin installation of the Meta Manager Server. 4. In the Meta Manager Install window, enter the Meta Manager Licence Key. This key is used by the server on start-up. A licence key can be obtained by contacting Compusult Limited at 1-888-388-8180 or licence@compusult.nf.ca. Enter the ODBC DSN for the Meta Manager and Tutorial database files. Enter the Meta Manager database login name in the Meta Manager Login field and, if you choose to install the tutorial, enter the tutorial database login name in the Tutorial Login field. Enter the port number on which the server will listen for Z39.50 search requests in the Z39.50 Server Port field. Enter the instance name of the server in the Instance Name field. This name will show up in the registry and in services under the control panel. The setup program will verify database connectivity. Note: If you choose to install the tutorial, the server is initially configured to use the database corresponding to the Tutorial DSN. 5. Click OK then Finish to finish the installation. After restarting the computer, the server will be listening for requests on the chosen port. 3.2.3 Meta Manager Server Installation Instructions for SQL Server 3.2.3.1 Before You Begin Installing Meta Manager needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following hardware and software sub-sections. 3.2.3.1.1 Software Items The following software items will be required: 1. Windows NT 4.0 or higher. 2. An SQL Server database. 3. Meta Manager software for the target platform (downloadable from http:// www.metadatamanager.com). 4. A Z39.50 client such as CNIDR s Stateful Gateway (downloadable from http://www.cnidr.org). You can use the Meta Manager test gateway for testing access to your datasets. 5. Netscape Navigator or Microsoft Internet Explorer by Compusult Limited 1998-2003 - Document No. 901-003 3-4

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3.2.3.1.2 Hardware and Firmware Items The following hardware will be required: 1. Pentium with 32 MB RAM plus 2 MB hard disk space. 3.2.3.2 Procedure 1. Download the Meta Manager Server installation software (available at http:// www.metadatamanager.com). You will be required to enter a username and password. The downloadable file is a self-extracting executable. 2. Double-click the self-extracting executable. The Meta Manager Server window will be displayed. The Install Shield Wizard will guide you through the rest of the setup process. Continue to click the Next or Yes button at the bottom of the screens to proceed with the installation process. 3. Click Next to continue to the Choose Destination Location screen. You can select the default destination directory (c:\program Files\Compusult Web Enterprise Suite\Meta Manager) by clicking the Next button or you can select another folder by clicking the Browse button, selecting the desired folder, and clicking the Next button. The setup program will begin installation of the Meta Manager Server. 4. In the Meta Manager Install window, enter the Meta Manager Licence Key. This key is used by the server on start-up. A licence key can be obtained by contacting Compusult Limited at 1-888-388-8180 or licence@compusult.nf.ca. Enter the ODBC DSN for the Meta Manager and Tutorial database files. Enter the SQL Server host machine name in the SQL Server Host Location field and, if you choose to install the tutorial, check the Install Tutorial? box. Select either Windows NT authentication or SQL Server authentication. The Metaman and Tutorial database username fields will be pre-filled. Enter the Metaman password, and if applicable the Tutorial password, in the Password fields. Enter the port number on which the server will listen for Z39.50 search requests in the Z39.50 Server Port field. Enter the instance name of the server in the Instance Name field. This name will show up in the registry and in services under the control panel. The setup program will verify database connectivity. Note: If you choose to install the tutorial, the server is initially configured to use the database corresponding to the Tutorial DSN. 5. Click OK then Finish to finish the installation. After restarting the computer, the server will be listening for requests on the chosen port. 3.2.4 Meta Manager Administrator Installation Instructions 3.2.4.1 Before You Begin Installing The Meta Manager Administrator software needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following hardware and software sub-sections. by Compusult Limited 1998-2003 - Document No. 901-003 3-5

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3.2.4.1.1 Software Items 1. Microsoft Windows. 2. Oracle Client to connect to an Oracle database. 3. ODBC to set up system data sources. 3.2.4.1.2 Hardware and Firmware Items 1. Pentium 32 MB RAM plus 10 MB hard disk space. 3.2.4.2 Procedure 1. Download the Meta Manager Administrator software (available at http:// www.metadatamanager.com). You will be required to enter a username and password. The downloadable file is a self-extracting executable. 2. Double-click the self-extracting executable. The Install Shield will guide you through the Meta Manager Administrator setup. You will be required to respond to prompts by clicking either the Next or Yes buttons until you reach the Choose Destination Location screen. You can accept the default folder (c:\program Files\Compusult Web Enterprise Suite\Meta Manager) in which to install Meta Manager or you can click on the Browse button to select a different folder. Once a folder has been selected, click the Next button to continue. 3. In the Select Program Folder screen, program icons will be added to the default Meta Manager program folder. To choose a different program folder, select one from the list. Click the Next button to continue. The Meta Manager Administrator will now begin to install. When Install Shield has completed the setup, click the Finish button to dismiss the Setup program. 4. Meta Manager can be started by selecting Programs, Compusult Web Enterprise Suite, Meta Manager from the Windows Start Menu. 3.3 UNIX Installation Instructions for Oracle This section explains how to install Meta Manager on a UNIX platform and how to begin configuring the application for your needs. Before you install Meta Manager, you should be logged in as the root user, unless: you plan to install Meta Manager on a port greater than 1024; and, the location where you plan to install Meta Manager (the server root directory) is writable with your current login status. The oracle account(s) used by Meta Manager must be pre-created, have connect and resource privileges, and enough tablespace quota to store the fgdc data. by Compusult Limited 1998-2003 - Document No. 901-003 3-6

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3.3.1 Before You Begin Installing Meta Manager needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following sub-sections. 3.3.1.1 Software Items The following software items will be required: 1. Oracle Release 7.1.6 or later. 2. Meta Manager Installation Software (downloadable from http://www.metadatamanager.com). 3. A Z39.50 client such as CNIDR s Stateful Gateway, Version 2 (downloadable from http:// www.cnidr.org). 4. Netscape Navigator or Microsoft Internet Explorer. 3.3.1.2 Hardware and Operating System The following hardware will be required: 1. Any CPU running a supported UNIX operating system: Sun (Solaris 2.3 or better) DEC OSF/1 3.2 DEC UNIX Linux 2. Minimum 32 MB RAM. 64 MB or more is recommended for servers that will handle a high volume of traffic. 3. 5 MB of free hard disk space. 3.3.2 Procedure 1. Download the Meta Manager Installation package, available at http://www.metadatamanager.com. 2. Unzip and extract the contents of the downloaded file into a temporary installation directory. 3. Verify that the installation directory contains three files and six subdirectories as follows: LICENCE - A file describing the restrictions on the use of the toolkit. README - A file describing the contents of the toolkit. bin/ - A subdirectory containing the de-install script. metaman/ - A subdirectory containing the toolkit database components. doc/ - A subdirectory containing the toolkit documentation. install - A shell script that will install the toolkit. server/ - A subdirectory containing the Meta Manager Z39.50 server component by Compusult Limited 1998-2003 - Document No. 901-003 3-7

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager tutorial/ - A subdirectory containing the tutorial database component. 4. Verify that the doc subdirectory contains the following document: users_manual.pdf - User s Manual (PDF format). The PDF file can be viewed using the freely downloadable Adobe Acrobat Reader program (Version 3.0 or later). 5. In the directory into which the toolkit was extracted (e.g., /tmp/mminst), execute the following command:./install. The following message and prompt will be displayed: /************************************************************************* / Meta Manager / Installation Script / Version 4.3 / / Copyright Compusult Limited - 1998-2003 / /************************************************************************* Enter license key? 6. Enter the Meta Manager licence key. This key is used by the server on start-up and can be obtained by contacting Compusult Limited at (709) 745-7914 or licence@compusultl.nf.ca. The following prompt will be displayed: Enter Meta Manger destination directory? 7. Enter the pre-created location for the toolkit (e.g., /apps/metaman4_0_1). The following prompt will be displayed: Enter value for ORACLE_HOME? 8. Enter the location of the oracle installation (e.g., /u01/app/oracle/product/7.3.2). The following prompt will be displayed: Use SQL*Net to access database [yes]?. 9. To access a local database, answer no and go to Step 10. To access an external database using SQL*Net, answer yes and go to Step 12. 10. The following prompt will be displayed: Enter the value for ORACLE_SID? 11. Enter the SID of the Oracle database that you are using (e.g., ORCL). Go to Step 15. 12. The following prompt will be displayed: Enter value for TNS_ADMIN? 13. Enter the location of the TNS administration files (e.g., /u01/app/oracle/admin/network/admin). The following prompt will be displayed: SQL*Net TNS Name for database? 14. Enter the TNS name (e.g., mydb). 15. The following prompt will be displayed: Enter Username for DB account to house Toolkit database components? 16. Enter the name of the pre-created DB account (e.g., mmadmin). The following prompt will be displayed: Enter password for DB account mmadmin? by Compusult Limited 1998-2003 - Document No. 901-003 3-8

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 17. Enter the accounts password (e.g., mmadmin). The following message and prompt will be displayed: Verifying Oracle connectivity with information provided... Success. Enter port number for the Z39.50 YAZ Server? 18. Enter the TCP/IP port number you wish to use for your Z39.50 server (e.g., 9999) The following messages and prompt will be displayed: You have provided all the information required for the initial installation of the Meta Manager. Please standby as the pieces are installed. Installing Meta Manager Oracle database components... Success. Installing Meta Manager Z39.50 server components... Success. Installing Meta Manager Documentation Components... Success. Would you like to install the Meta Manager tutorial? (Y/N) [N] 19. Enter Y if you wish to have the tutorial tables installed. The following messages and prompt will be displayed. Enter the Username for the tutorial account? 20. Enter the pre-created db account name for the tutorial (e.g., mmtut). The following messages and prompt will be displayed. Enter the Password for the tutorial account? 21. Enter the account s password (e.g., mmtut). The following messages and prompt will be displayed Verifying Oracle connectivity for tutorial/tutorial... Success. Import: Release 7.3.2.1.0 - Production on Mon Mar 30 10:29:26 1998 Copyright (c) Oracle Corporation 1979, 1994. All rights reserved. Connected to: Oracle7 Server Release 7.3.2.1.0 - Production Release With the distributed and Spatial Data options PL/SQL Release 2.3.2.0.0 - Production Export file created by EXPORT:V07.01.06 via conventional path.. importing table "AGENCY" 7 rows imported.. importing table "ELEMENT_MAPPINGS" 642 rows imported.. importing table "KEYWORD_LOOKUPS" 1023 rows imported.. importing table "KEYWORD_THEMES" 1 rows imported.. importing table "METADATA_COLLECTIONS" 2 rows imported.. importing table "METADATA_ELEMENTS" 642 rows imported.. importing table "METADATA_GROUPS" 242 rows imported.. importing table "METADATA_STANDARDS" 1 rows imported.. importing table "METADATA_TEMP" 442 rows imported.. importing table "PRESENT_SETS" 3 rows imported.. importing table "PRESENT_SET_ELEMENTS" 692 rows imported.. importing table "S57DATA" 75 rows imported.. importing table "S57METADATA" 76 rows imported.. importing table "SEARCH_OVERRIDE_ELEMENTS" 5 rows imported.. importing table "SQL_SEARCH_RESULTS" 0 rows imported.. importing table "TABLE_LINKS" 2 rows imported.. importing table "TEMP_TABLE" 121 rows imported Import terminated successfully without warnings. You have successfully installed Meta Manager onto your system You now have to use the Meta Manager Administration interface to describe your Oracle-based datasets so that the Z39.50 server can make them available. Once you have described one or more datasets using the administrative interface, you can start the Z39.50 server with the command: /apps/metamanager/bin/rc.toolkit start by Compusult Limited 1998-2003 - Document No. 901-003 3-9

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager The Unix portion of the installation is now complete. If you are planning to use the Windows 95/98/NT/ 2000 Administration module, see Chapter 5. 3.3.3 Removal of Meta Manager from Your System This section describes the uninstall process that will allow you to remove Meta Manager and its associated components. Procedure: 1. Execute the command /apps/metamanager/bin/deinstall. The following message and prompt will be displayed: You are about to remove Meta Manager. Type YES if you are sure you wish to do this: 2. Enter YES. The following messages will be displayed. You have selected to remove Meta Manager. Please standby as the pieces are de-installed. Removing Meta Manager Oracle database components... Success. Removing Meta Manager Z39.50 server components... Success. You have successfully removed Meta Manager. $ Meta Manager has now been removed from your system. 3.4 Unix Installation Instructions for Sybase This section explains how to install Meta Manager on a UNIX platform for Sybase and how to begin configuring the application for your needs. Before you install Meta Manager, you should be logged in as the root user, unless: you plan to install Meta Manager on a port greater than 1024; and, the location where you plan to install Meta Manager (the server root directory) is writable with your current login status. The Sybase account(s) used by Meta Manager must be pre-created, have Create Database privileges, and enough database device space allocated to store the database transactions and FGDC data. (Use a 50 MB device or higher.). The Model database must also have the select into/bulkcopy/pllsort option set to on. 3.4.1 Before You Begin Installing Meta Manager needs specific software and hardware. Before you can run the installation, you must comply with the requirements in the following sub-sections. by Compusult Limited 1998-2003 - Document No. 901-003 3-10

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 3.4.1.1 Software Items The following software items will be required: 1. Sybase Adaptive Server Enterprise Version 11.5 or higher. 2. Meta Manager Installation Software (downloadable from http://www.metadatamanager.com). 3. A Z39.50 client such as CNIDR s Stateful Gateway, Version 2 (downloadable from http:// www.cnidr.org). 4. Netscape Navigator or Microsoft Internet Explorer. 3.4.1.2 Hardware and Operating System The following hardware will be required: 1. Any CPU running a supported UNIX operating system: Sun (Solaris 2.3 or better) DEC OSF/1 3.2 DEC UNIX Linux 2. Minimum 32 MB RAM. 64 MB or more is recommended for servers that will handle a high volume of traffic. 3. 5 MB of free hard disk space. 3.4.2 Procedure 1. Download the Meta Manager Installation package, available at http://www.metadatamanager.com. 2. Unzip and extract the contents of the downloaded file into a temporary installation directory. 3. Verify that the installation directory contains three files and five subdirectories as follows: LICENCE - A file describing the restrictions on the use of the toolkit. README - A file describing the contents of the toolkit. bin/ - A subdirectory containing the de-install script. metaman/ - A subdirectory containing the toolkit database components. doc/ - A subdirectory containing the toolkit documentation. install - A shell script that will install the toolkit. server/ - A subdirectory containing the Meta Manager Z39.50 server component. tutorial/ - A subdirectory containing the tutorial database component. 4. Verify that the doc subdirectory contains the following document: users_manual.pdf - User s Manual (PDF format). by Compusult Limited 1998-2003 - Document No. 901-003 3-11

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager The PDF file can be viewed using the freely downloadable Adobe Acrobat Reader program (Version 3.0 or later). 5. In the directory into which the toolkit was extracted (e.g., /tmp/mminst), execute the following command:./install. The following message and prompt will be displayed: //************************************************************************* / Meta Manager / Installation Script / Version 4.3 / / Copyright Compusult Limited - 1998-2003 / /************************************************************************* Enter license key? 6. Enter the Meta Manager licence key. This key is used by the server on start-up and can be obtained by contacting Compusult Limited at (709) 745-7914 or licence@compusult.nf.ca. The following prompt will be displayed: Enter Meta Manger destination directory? 7. Enter the pre-created location for the toolkit (e.g., /apps/metaman4_0_1). The following prompt will be displayed: If you already have an existing set of database objects (e.g. from a prior installation of Meta Manager), Meta Manager can use the existing objects instead of creating new ones. Do you wish to use an existing set of database objects [no]? 8. If you have an existing set of database objects for Meta Manager enter yes, otherwise enter no. The following prompt will be displayed: Enter value for SYBASE_HOME? 9. Enter the location of the Sybase installation (e.g., /apps/sybase). 10. The following prompt will be displayed: Enter Username for DB account to house Toolkit database components? 11. Enter the name of the pre-created DB account (e.g., mmadmin). The following prompt will be displayed: Enter password for DB account mmadmin? 12. Enter the accounts password (e.g., mmadmin). The following prompt will be displayed: Enter server for DB account? 13. Enter the server on which you wish to install the Meta Manager database (e.g. metaman). The database that will be installed is called metaman. You may change this later if you wish. The following prompt will be displayed: Enter device name for database? 14. Enter the pre-created device name to store the transaction information for the metaman database. The following message and prompt will be displayed: Verifying SYBASE connectivity with information provided... Success Enter port number for Z39.50 YAZ Server? by Compusult Limited 1998-2003 - Document No. 901-003 3-12

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager 15. Enter the TCP/IP port number you wish to use for your Z39.50 server (e.g., 9999) The following messages and prompt will be displayed: You have provided all the information required for the initial installation of the Meta Manager. Please standby as the pieces are installed. CREATE DATABASE: allocating 12800 pages on disk metaman Backup Server session id is: 109. Use this value when executing the sp_volchanged system stored procedure after fulfilling any volume change request from the Backup Server. Backup Server: 6.28.1.1: Dumpfile name metaman010300e7a2 section number 1 mounted on disk file /etc/rc3.d/met_backup Backup Server: 4.58.1.1: Database metaman: 1398 kilobytes LOADed. Backup Server: 4.58.1.1: Database metaman: 25606 kilobytes LOADed. Backup Server: 4.58.1.1: Database metaman: 25614 kilobytes LOADed. Backup Server: 3.42.1.1: LOAD is complete (database metaman). Use the ONLINE DATABASE command to bring this database online; SQL Server will not bring it online automatically. Database metaman is now online. Success. Installing Meta Manager Z39.50 Server Components... Installing Meta Manager Documentation Components... Success. Would you like to install the Meta Manager tutorial? (Y/N) [N]? 16. Enter Y if you wish to have the tutorial tables installed. The following messages and prompt will be displayed. Enter the Username for tutorial account? 17. Enter the pre-created db account name for the tutorial (e.g., mmtut). The following prompt will be displayed. Enter the Password for tutorial account? 18. Enter the account s password (e.g., mmtut). The following prompt will be displayed Enter server for tutorial account? 19. Enter the server name on which you wish to install the tutorial database. The default database name will be tutorial. You may change this later if you wish. The following prompt will be displayed: Enter device name for tutorial database? 20. Enter the pre-created device name to store the transaction information for the tutorial database. The following message will be displayed: Verifying Sybase connectivity for sa/sybase...create DATABASE: allocating 12800 pages on disk metaman Backup Server session id is: 111. Use this value when executing the sp_volchanged system stored procedure after fulfilling any volume change request from the Backup Server. Backup Server: 6.28.1.1: Dumpfile name tutorial010360cc15 section number 1 mounted on disk file /etc/rc3.d/tut_backup Backup Server: 4.58.1.1: Database tutorial: 1432 kilobytes LOADed. Backup Server: 4.58.1.1: Database tutorial: 13830 kilobytes LOADed. Backup Server: 4.58.1.1: Database tutorial: 25608 kilobytes LOADed. Backup Server: 4.58.1.1: Database tutorial: 25616 kilobytes LOADed. Backup Server: 3.42.1.1: LOAD is complete (database tutorial). Use the ONLINE DATABASE command to bring this database online; SQL Server will not bring it online automatically. Database tutorial is now online. You have successfully installed the Meta Manager onto your system. You now have to use the Meta Manager Administrator to describe your Oracle based datasets so that the Z39.50 server can make them available. Once you have described one or more datasets using the Meta Manager Administrator, you can start the Z39.50 server with the command: /users/denise/testing/bin/rc.toolkit start by Compusult Limited 1998-2003 - Document No. 901-003 3-13

User s Manual User s Manual - Revision 4.0 June 27, 2003 Installing Meta Manager The Unix portion of the installation is now complete. If you are planning to use the Windows 95/98/NT/ 2000 Administration module, see Chapter 5. 3.4.3 Removal of Meta Manager from Your System This section describes the uninstall process that will allow you to remove Meta Manager and its associated components. Procedure: 1. Execute the command /apps/metamanager/bin/deinstall. The following message and prompt will be displayed: You are about to remove Meta Manager. Type YES if you are sure you wish to do this: 2. Enter YES. The following messages will be displayed. You have selected to remove Meta Manager. Please standby as the pieces are de-installed. Removing Meta Manager Oracle database components... Success. Removing Meta Manager Z39.50 server components... Success. You have successfully removed Meta Manager. $ Meta Manager has now been removed from your system. by Compusult Limited 1998-2003 - Document No. 901-003 3-14

CHAPTER 4 Meta Manager Server A modified version of the YAZ Z39.50 server software for UNIX or Windows NT/2000 platforms is provided. The server side is mapped onto the interface of the specific database management system. The communication taking place between the server and the client application is precisely defined within the Z39.50 protocol. The YAZ Z39.50 server is fully configured and integrated with the Meta Manager software and requires no user intervention, other than starting and stopping the Z39.50 server application software as required. The following diagram provides an overview of the operation of the Z39.50 server software: by Compusult Limited 1998-2003 - Document No. 901-003 4-1

Meta Manager Server Data Clearinghouse WWW Client Z39.50 Client Other Metadata Standard Profile- Aware Clients WWW Server HTTP Z39.50 Gateway Meta Manager Z39.50 Front-End Server (YAZ) Result Formatting (e.g., XML, SUTRS, USMARC) RPN Metadata Standard Query Z39.50 Back-End Server Metadata Standard Result Set SQL to Metadata Standard Metadata Standard SQL Mappings SQL Metadata Data Warehouse SQL to Metadata Standard Mappings Execute Query RPN to SQL FIGURE 4 SQL and Metadata Standard Profile Interface by Compusult Limited 1998-2003 - Document No. 901-003 4-2

Meta Manager Server Queries will be generated, either through a WWW Client via a Z39.50 Gateway or through a Z39.50 client, known as the Origin. This facilitates all communication functions relating to initiating a search, sending a query and requesting the return of records. The Z39.50 server part is known as the Target. It initiates the processes that will ultimately interface with the SQL database in the remote system and responds to messages received from the Origin system. A searcher enters a query into the local system using that system s set of menus and command language. The Z39.50 Origin module (located in the local system) translates the query into a standardized format as defined by the Z39.50 information retrieval protocol and sends it to a Z39.50 server. The Z39.50 server uses a custom facility (RPN to SQL) which will access the SQL database to perform metadata-to-sql translations. The query is executed against the SQL database system. The results of the query are formulated and translated from SQL to the metadata standard. The formulated results are then returned to the Z39.50 server as a full, summary or brief result set and then returned to the Z39.50 origin. 4.1 Meta Manager Server on Windows NT 4.0 or Higher Meta Manager for Windows NT/2000 creates a Windows NT/2000 service that is the YAZ Z39.50 server (MetaManagerServer.exe). This service starts upon restarting the machine, or any user with administrative privileges can start the service from the Windows Control Panel. 4.1.1 Starting the Meta Manager YAZ Z39.50 Server To start the Meta Manager YAZ Z39.50 server, perform the following procedure: Procedure 1. Login as a user with administrative privileges. 2. Select Control Panel from Settings on the Windows NT/2000 Start Menu. 3. Double-click the Services icon. For Windows 2000, first select Administrative Tools. 4. Select MetaManager from the list of the services and select the Start button. Note: The installation process configures Windows NT/2000 to automatically start the Meta Manager Server. 4.1.2 Stopping the Meta Manager YAZ Z39.50 Server To stop the Meta Manager YAZ Z39.50 Server, perform the following procedure: Procedure 1. Login as a user with administrative privileges. 2. Select Control Panel from Settings on the Windows NT/2000 Start Menu. 3. Double-click the Services icon. For Windows 2000, first select Administrative Tools. 4. Select MetaManager from the list of the services and select the Stop button. by Compusult Limited 1998-2003 - Document No. 901-003 4-3

Meta Manager Server 4.2 Meta Manager Server on UNIX Prior to installing Meta Manager, an application directory was created on the target Unix platform for the purpose of containing the application software. During the installation process, a bin directory was created in the application directory and this directory contains the Meta Manager YAZ Z39.50 Server executable software. 4.2.1 Starting the Meta Manager Server on UNIX To start the Meta Manager YAZ Z39.50 server, perform the following procedure: Procedure 1. Move to the application directory specified during the installation process. 2. Move to the bin directory (i.e., cd bin). 3. To start the Meta Manager YAZ server, type the command rc.toolkit start. The message Starting Z39.50 Server on port port# will be displayed. 4.2.2 Stopping the Meta Manager Server on UNIX To stop the Meta Manager YAZ Z39.50 Server on UNIX, perform the following procedure: Procedure 1. Move to the application directory specified during the installation process. 2. Move to the bin directory (i.e., cd bin). 3. To start the Meta Manager YAZ server, type the command rc.toolkit stop. The message Stopping Z39.50 Server: pid# will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 4-4

CHAPTER 5 Meta Manager Administrator Meta Manager provides data administrators with the ability to maintain metadata mappings and configurations within an SQL RDBMS. This application provides users with a standard way of making their system catalogs and data holdings available to the client. It contains all of the facilities necessary for mapping the internal SQL database to metadata standard profiles. 5.1 First-Time Use of the System After installing Meta Manager, the SQL database will be populated with metadata standard profile-to- SQL mapping tables. A Master collection for each of the supported metadata standards is provided. Each of the mappable elements has a default state of un-mapped. The Master collection is a template that is used to store values that are common to all collections. Each new collection is created by copying the Master collection template. Any mappings that will be applicable to every dataset should be mapped within the Master collection. A mapping in the Master collection will be reflected in the corresponding global element of any other collections. All Meta Manager Administrator communications are performed using an appropriate ODBC driver. Before using Meta Manager Administrator, an ODBC Data Source Name must be configured to point to the database containing the Meta Manager Server database. The data and metadata database tables to be mapped using Meta Manager must be accessible to the Meta Manager RDBMS account. For example, the Meta Manager Oracle and SQL user must have select privileges on any table that is to be mapped. When Meta Manager s internal tables are contained in an MS Access database (*.mdb file) the tables to be searched must either be in, or linked to, the Meta Manager mdb file. Meta Manager Administrator provides an Attach Tables facility to create links from the Meta Manager mdb file to tables in other mdb files. To run Meta Manager Administrator, perform the following procedure: Procedure 1. Start Meta Manager Administrator by selecting Programs/Compusult Web Enterprise Suite/Meta Manager from the Windows Start Menu. The ODBC Data Source form will appear. The ODBC DSN field will be filled with the name of the last successful collection made in Meta Manager Administrator. by Compusult Limited 1998-2003 - Document No. 901-003 5-1

Meta Manager Administrator FIGURE 5 ODBC Data Source Form 2. If applicable, enter a valid Username and Password to access the database. 3. Select the down-arrow button next to the ODBC DSN field to retrieve a list of previously used data sources and select the required data source to connect to the database. Note: If the required data source cannot be found in the list, click on the ODBC DSN button to get a list of all the available data sources. Select the data source name configured for the database containing the Meta Manager database tables. If connecting to an Oracle database, the Oracle8 ODBC Driver Connect screen will appear as illustrated in Figure 6. If applicable, enter a valid Username and Password to access the database and select OK. FIGURE 6 Oracle8 ODBC Driver Connect 4. Select OK on the ODBC Data Source screen. The ODBC Data Source screen will be dismissed and Meta Manager will connect to the target database. The main Meta Manager window will be displayed as shown in Figure 7. by Compusult Limited 1998-2003 - Document No. 901-003 5-2

Meta Manager Administrator FIGURE 7 Meta Manager Main Window 5.1.1 Configuring the Master Collection The Master collection is the template related to a particular metadata standard profile from which all other collections are created. Modifications made to the Master collection will be reflected in any new collections created. Modifications to the structure of the Master collection tree representation of the Metadata Standard will be reflected in new collections created, but will not affect the structure of existing collections. For example, the metadata compound element Browse_Image is repeatable. Duplicating this object in the Master collection will result in only new collections having the corresponding Browse_Image duplicated. Mappings made in the Master collection will always be reflected in subsequently created collections. If a non-global element is deleted in a non-master collection, and the corresponding element is mapped in the Master, the Master mapping can, optionally, be reflected in the non-master collection. by Compusult Limited 1998-2003 - Document No. 901-003 5-3

Meta Manager Administrator Configuring the Master collection involves mapping data elements with values that relate to all collections. Note that only the data elements described in the metadata standard being used can be mapped. Mappings in the Master collection will usually, but not necessarily, be constant values. 5.2 Mapping Data to the Metadata Standard Meta Manager was specifically designed to work with SQL repositories that contain supplier metadata and data. The internal data definitions include full table and column information along with server-side validation of foreign key constraints, check conditions, primary keys, etc. This information is accessed to allow Meta Manager users to map their internal definitions of metadata and data to the metadata standard profile representations. SQL Internal Data and Metadata Definitions GEO / GILS Profile Query INTERSECTING TABLES Metadata Standard FIGURE 8 Metadata and SQL Metadata Mappings Data administrators are provided the ability to map these internal formats contained within an SQL database to a metadata standard, in particular the mapping of Z39.50 Use Attributes, the fields that can be searched in the target database. The metadata standard profiles define a Use Attribute for each of the searchable fields in the metadata standard. 5.2.1 Creating a New Data Collection A single Meta Manager database account can contain multiple, distinct data collections. When creating new collections, the primary table and its primary key field need to be specified. The primary table, and any other tables to be searched, needs to be accessible by the Meta Manager database account. Meta Manager provides a facility to add tables to the Meta Manager database.when the Meta Manager database account is housed in a Microsoft Access database, this provides the means necessary to make the external database tables to be searched visible to the Meta Manager user. by Compusult Limited 1998-2003 - Document No. 901-003 5-4

Meta Manager Administrator To create a new data collection, perform the following procedure: Procedure 1. Start Meta Manager. The ODBC Data Source dialog box will be displayed. 2. Connect to the Meta Manager database by providing or selecting the ODBC DSN configured for the database, and, if applicable, a Username and Password. 3. Select New... from the Collection menu located at the top of the screen. The Collection - New form will appear as shown in Figure 9. FIGURE 9 Collection - New Form 4. Select the Standard Name from the pull-down list. 5. Enter the name of the new collection in the Collection Name field. 6. Click the Next... button located at the bottom of the form. The Add Tables form will appear (see Figure 10). FIGURE 10 Add Tables (Oracle or Sybase) Form 7. To add an MS Access database table, enter the filename (*.mdb file) in the Database File field, or click the Open button to select a file. To add an SQL Server database table, select a catalog name from the Catalog field pull-down list. by Compusult Limited 1998-2003 - Document No. 901-003 5-5

Meta Manager Administrator Note: The Database File field will appear on the Add Tables form when connected to an MS Access database (see Figure 13). The Catalog field will appear on the Add Tables form when connected to an SQL Server database (see Figure 15). These fields will not appear on the form when connected to an Oracle or Sybase database. 8. The Tables list box will be populated with tables contained in the database file. Highlight the table(s) to be added from this list and select the >> button located between the Tables list and the Meta Manager Tables list. The tables added will now be appended to the list of tables in the Meta Manager Database. To remove tables from the Meta Manager Tables list, select the << button. 9. Click the Next button located at the bottom of the form. The Collection - New form will appear with the Collection Name field filled with the name provided in Step 5. The form will also contain fields for the primary Table Name and the Primary Key Field (see Figure 11). FIGURE 11 Collection - New Form 10. Select the primary Table Name to be searched from the pull-down list. 11. Select the Primary Key Field for the primary table from the pull-down list. 12. Select the Save button located at the bottom of the form. A message confirming that the collection was created will be displayed. Select OK. The confirmation dialog box will be dismissed and the new collection will open. The newly created collection is a copy of the Master collection. That is, all elements mapped and Search Overrides defined in the Master are correspondingly mapped and defined in the newly created collection. Note that, as long as an element is flagged as global, all modifications made to that element in the Master collection are reflected in the new collection. 5.2.2 Adding Tables to a Collection The Meta Manager database must be able to reference the database tables that are to be mapped. The Meta Manager Add Tables facility provides the means to create references to external database tables in the Meta Manager Database. Any database field that is to be mapped must have the database table containing that field attached to the Meta Manager database prior to being mapped. 5.2.2.1 Adding Tables to the Meta Manager Database (MS Access) For MS Access, the Add Tables facility attaches the selected tables from an external database to the Meta Manager database. The following procedure explains how to add MS Access tables. by Compusult Limited 1998-2003 - Document No. 901-003 5-6

Meta Manager Administrator Procedure 1. Launch Meta Manager and connect to the database to which the external tables are to be attached. 2. Select Open... from the Collection menu (or click the Open toolbar button) and select the Metadata Standard and the Collection name from the Select Collection to Open screen. 3. Click the OK button at the bottom of the screen. The metadata tree structure for the collection will be loaded from the database. 4. The Add Tables routine can be invoked by selecting Add Tables... from the Collection menu located on the main window menubar, by selecting the Add Tables... toolbar button in the main window, or by selecting Properties... from the Collection menu and then clicking the Add Tables... button on the Collection - Properties form (see Figure 12). The Add Tables form will be displayed as illustrated in Figure 13. FIGURE 12 Collection - Properties Form 5. Enter the filename (*.mdb file) in the Database File field, or click the Open button to select the file containing the table(s) to attach. 6. The Tables list box will be populated with tables contained in the database file. Highlight the table(s) to be added from this list and select the >> button located between the Tables list and the Meta Manager Tables list. The tables will be attached to the list of tables in the Meta Manager database. To remove tables from the Meta Manager Tables list, select the << button. by Compusult Limited 1998-2003 - Document No. 901-003 5-7

Meta Manager Administrator FIGURE 13 Add Tables Form (MS Access) 7. Click the Close button located at the bottom of the form. The Add Tables screen will be dismissed and the tables will be added to the Meta Manager database. 5.2.2.2 Adding Tables to the Meta Manager Database (Oracle, Sybase and SQL Server) Using an Oracle or SQL Server database, the Meta Manager Add Tables facility will append the selected table name(s) to the list of table names in a collection. The table name(s) are then available if database linkages need to be defined using the Relationships facility. To add an Oracle, Sybase or SQL Server database table to the Meta Manager database, perform the following procedure: 1. Launch Meta Manager and connect to the database to which the external tables are to be attached. 2. Select Open... from the Collection menu (or click the Open toolbar button) and select the Metadata Standard and the Collection name from the Select Collection to Open screen. 3. Click the OK button at the bottom of the screen. The metadata tree structure for the collection will be loaded from the database. 4. Select Add Tables... from the Collection menu located on the main window menubar (or select the Add Tables toolbar button in the main window). The Add Tables form will be displayed as illustrated in Figure 14 for Oracle and Sybase and Figure 15 for SQL Server. The Add Tables form for SQL Server has an additional Catalog pull-down list containing all the database names available to the current user. by Compusult Limited 1998-2003 - Document No. 901-003 5-8

Meta Manager Administrator FIGURE 14 Add Tables Form (Oracle or Sybase) FIGURE 15 Add Tables Form (SQL Server) 5. Highlight the tables to be added to the Meta Manager database from the Tables list and click the >> button located between the Tables list and the Meta Manager Tables list. The selected tables will be added to the Meta Manager Tables list. To remove tables from the Meta Manager Tables list, click the << button. 6. Click the Close button located at the bottom of the form. The Add Tables screen will be dismissed and the tables will be added to the Meta Manager database. 5.2.3 Creating Table Relationships Often, the database fields mapped to elements in the standard are Lookup Values that refer to more useful and descriptive values in another table. For example, if a field in the Primary Table is an ID field that is a key into another database table, you can define the relationship between the Primary Table and the Secondary Table. by Compusult Limited 1998-2003 - Document No. 901-003 5-9

Meta Manager Administrator In some cases, the metadata associated with a Meta Manager collection is stored in a primary table and the data items (geographic extents, time period, file names, etc.) are stored in a secondary table. In this case, a one-to-many relationship will exist. The Relationships component of Meta Manager will provide the ability to define the database linkages that are required when the metadata being searched is distributed across a number of tables. Elements can be mapped to database fields from any table related to the primary table of the collection. In order to do this, the links between tables in the target data model must be explicitly defined within Meta Manager. Note that any tables defined in the Meta Manager Relationships must ultimately be linked to the primary table of the collection. Primary Collection Table Primary Metadata Definitions One-to-Many One-to-One Secondary Table Geographic Extents File Format Definitions etc. Look-up Table Content Information FIGURE 16 Table Linkages Procedure 1. Load the collection for which the table relationships are to be defined. Select Open... from the Collection menu at the top of the screen. The Select Collection to Open dialog box will appear. 2. Select the desired Metadata Standard and Collection from the respective lists and select the OK button located at the bottom of the screen. The metadata tree for the selected collection will be loaded from the database. by Compusult Limited 1998-2003 - Document No. 901-003 5-10

Meta Manager Administrator 3. Select Relationships... from the Collections menu located at the top of the screen (or select the Relationships toolbar button on the main window). The Table Links form will appear as shown in Figure 17. FIGURE 17 Table Links Form The fields associated with the Table Links form are defined as follows: Optional Table1 Table2 Column1 Column2 Indicates whether every row in Table1 has at least one corresponding row in Table2. First linked table. Second linked table. The column in Table1 that will refer to a column in Table2. The column in Table2 that will refer to a column in Table1. Relationship Description of the relationship between the first and second linked table. 4. Select the New button located at the bottom of the form. The Table Links - New form will appear as shown in Figure 18. FIGURE 18 Table Links - New Form The fields associated with the Table Links - New form are defined as follows: by Compusult Limited 1998-2003 - Document No. 901-003 5-11

Meta Manager Administrator Collection Table1 Table2 Column1 Column2 Relationship Optional The relevant collection. First linked table. Second linked table. The column in Table1 that will refer to a column in Table2. The column in Table2 that will refer to a column in Table1. Description of the relationship between Table1 and Table2. Indicates whether every row in Table1 has at least one corresponding row in Table2. 5. Select the two tables to be linked using the Table1 and Table2 drop-down lists. 6. Using the respective option menus, select the column from Table1 that will refer to a column in Table2 and the column in Table2 that will refer to the column in Table1. 7. Select the relationship type from the Relationship drop-down list. The descriptions provided refer to how Table1 is related to Table2. 8. Indicate whether rows exist in Table2 for all rows in Table1 from the Optional drop-down list. 9. Select the Save button located at the bottom of the form. The Table Links - New form will be dismissed and a confirmation window will appear. 10. Click OK in the confirmation window. The grid on the Table Links form will be updated with the new relationship. 5.2.4 Configuring/Editing a Data Collection Data administrators can map the metadata standard to the corresponding data in the database. In addition, field mappings may have to be updated from time to time. A tree representation of the metadata standard used for the selected collection is displayed on the left side of the screen and the attributes of the currently selected element are displayed on the right. Operations can be performed on an element by right-clicking on the element in the tree. Only data elements as defined in the metadata standard can be mapped. Compound elements can be duplicated if the metadata standard defines the element as repeatable. Certain compound elements can have Search Overrides defined for them, see Section 5.3. Note that an element can be mapped with a Fixed or Database value. In general, if an element in the standard is associated with a constant value for each record in the dataset, the Fixed radio button of the Element Mapping form should be selected. An element would be mapped with a Database value if the element were associated with a particular field in a table in the database. For example, the element Publication_Date for the FGDC GEO Profile would probably be mapped to a Date field in the database. Element mappings may require symbol substitutions due to XML limitations. If an incorrect symbol is used in an element mapping and a search is performed on the web page, the corresponding HTML output by Compusult Limited 1998-2003 - Document No. 901-003 5-12

Meta Manager Administrator may be created incorrectly. The following is a list of symbol substitutions to use when mapping metadata elements: Symbol Substitution Symbol & & < < > > " The procedure for mapping elements of a metadata standard to fields in a database are described below. 5.2.4.1 Mapping Elements in a Collection Using Database Values Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database containing the collection to be mapped. 2. Select Open... from the Collection menu located at the top of the screen (or click the Open toolbar button). The Select Collection to Open dialog box will appear. 3. Select the Metadata Standard and Collection to be mapped from the respective lists and select the OK button located at the bottom of the screen. The collection will be loaded from the database. Prior to mapping any data elements, establish the relationships between the tables in the dataset using Meta Manager s Relationships facility as described in Section 5.2.3. 4. Navigate to the desired data element to be operated on. If the element is not mapped, the only available operation on that element will be New Mapping... If the element is currently mapped and the metadata standard defines the element as repeatable, the Edit Mapping... and New Mapping... operations will be available. Select the desired operation from the menu and the default database mapping Element Mapping form will appear as illustrated in Figure 19. FIGURE 19 Element Mapping Form (Database Values) by Compusult Limited 1998-2003 - Document No. 901-003 5-13

Meta Manager Administrator The fields associated with the Element Mapping form when the Database radio button is selected are as follows: Data Type: Text Search: Table Name: Display Value: Search Value: Search Mask: This is the native database storage type of the information provided in the other fields. This field should be set to the general text data type of the database if you are using the Fixed radio button. This field allows the user to specify the elements that are to be used in the Full Text search on the Web page. Initially, the elements will default to how they are defined in the standard. In order to add a mapped element to the Enhanced Text Search, this field must be set to INCLUDE and the Auto Harvest option must be set in the Collection Properties (see Section 5.8). This is the database table that contains the column(s) that will be mapped to the selected element. The Select button can be used to get a list of the tables associated with the collection being edited. This is the column from the selected table that will be presented to the client when this element is retrieved.this value can be a simple column name from the selected table, or it can be any valid SQL select construct (e.g., to_char(user.table.date_field, YYYY/MM/DD ), user.table.first_name user.table.last_name). This is the column (or any valid SQL where clause item) that will be used when searching on the associated Use Attribute. This is the SQL construct (if any) that must be applied to the value presented in the search request by the client before it can be compared to the Search Value. (e.g., Z39.50 dates are passed as YYYYMMDD, they must be converted to a database DATE format if a native DATE field is being used. This would require a search mask such as to_date( %s, YYYYMMDD ). The %s is replaced with the value passed in the search request.) Note: to_date( %s, YYYYMMDD ) is the default search mask if the Data Type of the element is DATE. 5. The Database radio button will be selected by default. Click on the down-arrow located next to the Table Name field and select the table that contains the column that will be mapped to the selected element. 6. Click on the down-arrow located next to the Display Value field and select the column that will be mapped to the selected element. 7. Click on the down-arrow located next to the Search Value field and select the column that will be searched for the selected element. 8. If applicable, enter the Search Mask to be applied to the value presented in the search request. 9. Select the Save button. The Element Mapping form will disappear and a message box will be displayed confirming the database update. 10. Click OK to dismiss the confirmation box. The Meta Manager main window will be updated to reflect the new mapping. by Compusult Limited 1998-2003 - Document No. 901-003 5-14

Meta Manager Administrator 5.2.4.2 Mapping Elements in a Collection Using Fixed Values 1. Launch the Meta Manager application and connect to the Meta Manager database containing the collection to be mapped. 2. Select Open... from the Collection menu located at the top of the screen (or click the Open toolbar button). The Select Collection to Open dialog box will appear. 3. Select the Metadata Standard and Collection to be mapped from the respective lists and select the OK button located at the bottom of the screen. The collection will be loaded from the database. Prior to mapping any data elements, establish the relationships between the tables in the dataset using Meta Manager s Relationships facility as described in Section 5.2.3. 4. Navigate to the desired data element to be operated on. If the element is not mapped, the only available operation on that element will be New Mapping... If the element is currently mapped and the metadata standard defines the element as repeatable, the Edit Mapping... and New Mapping... operations will be available. Select the desired operation from the menu and the default database mapping Element Mapping form will appear as illustrated in Figure 19. 5. Select the Fixed radio button. The Element Mapping form will now appear as illustrated in Figure 20. FIGURE 20 Element Mapping Form (Fixed Values) The fields associated with the Element Mappings form when entering a fixed mapping are explained as follows: Data Type: Text Search: This field should be set to standard text datatype of the database being searched. For example, if the underlying database is Oracle, the datatype value should be VARCHAR2. This field allows the user to specify the elements that are to be used in the Full Text search on the Web page. Initially, the elements will default to how they are defined in the standard. In order to add a mapped element to the Enhanced Text Search, this field must be set to INCLUDE and the Auto Harvest option must be set in the Collection Properties (see Section 5.8) by Compusult Limited 1998-2003 - Document No. 901-003 5-15

Meta Manager Administrator Fixed Value: This is the fixed string that constitutes the value for this element. If the element being defined is a GCMD (Global Change Master Directory) Keyword, you can use the Keywords... button to access the Global Change Master Directory Keywords form (see Section 5.2.4.3). 6. Enter the text to be mapped to the selected element in the Fixed Value field or click the Notepad... button and enter the text in Notepad. If text is entered in the Notepad feature, it will appear in the Fixed Value field on the Element Mapping form when Notepad is dismissed. 7. Select the Save button located at the bottom of the form. The Element Mapping form will be dismissed and a message confirming that the data has been saved will appear. 8. Click OK in the confirmation dialog box. The grid located on the Meta Manager main window will be updated to reflect the data entered. 5.2.4.3 Mapping Elements in a Collection Using GCMD Keywords This feature, found in mapping Fixed Value elements, allows the user to select common keywords for the Keywords group elements. The procedure for mapping Fixed Value elements using the GCMD Keywords feature is described next. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database containing the collection to be mapped. 2. Select Open... from the Collection menu located at the top of the screen (or click the Open toolbar button). The Select Collection to Open dialog box will appear. 3. Select the Metadata Standard and Collection to be mapped from the respective lists and select the OK button located at the bottom of the screen. The collection will be loaded from the database. Prior to mapping any data elements, establish the relationships between the tables in the dataset using Meta Manager s Relationships facility as described in Section 5.2.3. 4. Navigate to the desired data element to be operated on. If the element is not mapped, the only available operation on that element will be New Mapping... If the element is currently mapped and the metadata standard defines the element as repeatable, the Edit Mapping... and New Mapping... operations will be available. Select the desired operation from the menu and the default database mapping Element Mapping form will appear as illustrated in Figure 19. 5. Select the Fixed radio button. The Element Mapping Form will now appear as illustrated in Figure 20. 6. Click the Keywords... button. The Global Change Master Directory Keywords form will be displayed as shown in Figure 21. by Compusult Limited 1998-2003 - Document No. 901-003 5-16

Meta Manager Administrator FIGURE 21 Global Change Master Directory Keywords Form 7. Click the down-arrow button next to the Theme field and select the theme from the drop-down list. 8. Click the down-arrow button next to the Category field and select a category from the drop-down list. The selection will appear in the Keyword String field. 9. If applicable, click the down-arrow button next to the Topic field and select a topic from the dropdown list. The selected topic will be appended to the Keyword String field. Note: Each selection chosen in a drop-down list will result in a new set of categories available for the drop-down list immediately below it. 10. If applicable, click the down-arrow button next to the Term field and select a topic from the dropdown list. The selected term will be appended to the Keyword String field. 11. If applicable, click the down-arrow button next to the Variable field and select a variable from the drop-down list. The selected variable will be appended to the Keyword String field. 12. Select the Save button. The Global Change Master Directory Keywords form will be dismissed. The value from the Keyword String field will now appear in the Fixed Value field on the Element Mapping form. 13. Select the Save button located at the bottom of the Element Mapping form. The form will be dismissed and a message confirming that the data has been saved will appear. 14. Click OK in the confirmation dialog box. The grid located on the Meta Manager main window will be updated to reflect the data entered. by Compusult Limited 1998-2003 - Document No. 901-003 5-17

Meta Manager Administrator 5.3 Defining Search Parameters 5.3.1 Search Parameters for Simple Elements Meta Manager provides the ability to define a Search Value for simple elements. When mapping simple elements, there is a Search Value field on the Element Mapping form where a search value can be defined to restrict searches of the datasets. For more information on this topic, see Section 5.2.4.1. 5.3.2 Search Parameters for Compound Elements Meta Manager provides the ability to define a Search Override for certain compound elements. A Search Override provides a way to restrict searches of your datasets based on a Geographic Search, a Date Search or a Text Search. If either the Time_Period_of_Content or the Bounding_Coordinates Search Overrides are not defined, then any search from a clearinghouse against these fields would return the first 1000 records. Time_Period_of_Content is a compound element as defined by the GEO Profile, hence it cannot be mapped to a field in a dataset in the same sense as a data element. Likewise for the TimePeriod compound element defined by the GILS Profile. To provide a means for dataset searches to be restricted by Time_Period_of_Content and TimePeriod, a Date Search Override must be assigned to these groups. In a similar way, a Geographic Search Override must be defined on the compound element Bounding_Coordinates found in both the GEO and GILS Profiles before spatial searches can be performed on the dataset. Geographic Search - Bounding Box The following database fields must be mapped: Minimum Latitude Database Field - Meta Manager MIN LAT Minimum Longitude Database Field - Meta Manager MIN LONG Maximum Latitude Database Field - Meta Manager MAX LAT Maximum Longitude Database Field - Meta Manager MAX LONG Geographic Search - Corner The following database fields must be mapped: Lower Left Latitude Database Field - Meta Manager LL LAT Lower Left Longitude Database Field - Meta Manager LL LONG Upper Left Latitude Database Field - Meta Manager UL LAT Upper Left Longitude Database Field - Meta Manager UL LONG Upper Right Latitude Database Field - Meta Manager UR LAT Upper Right Longitude Database Field - Meta Manager UR LONG Lower Right Latitude Database Field - Meta Manager LR LAT by Compusult Limited 1998-2003 - Document No. 901-003 5-18

Meta Manager Administrator Lower Right Longitude Database Field - Meta Manager LR LONG Geographic Search - Point The following database fields must be mapped: Latitude Database Field - Meta Manager LAT Longitude Database Field - Meta Manager LONG Date Search - Date The following database field must be mapped: Date Database Field - Meta Manager DATE Text Search - Text The following database field must be mapped: Text Database Field - Meta Manager TEXT Procedure 1. Launch the Meta Manager application, connect to the Meta Manager database housing the data to be mapped and open the desired collection. The following steps will demonstrate the process for configuring a search override for a geographic bounding box. 2. Navigate to the compound element Bounding_Coordinates located at the path Metadata/ Identification_Information/Spatial_Domain for the FGDC GEO Profile. Right-click on the element (or select Edit and Search Override from the main menu) and select Search Override... from the menu. The Search Overrides - Bounding_Coordinates form will be displayed as shown in Figure 22. by Compusult Limited 1998-2003 - Document No. 901-003 5-19

Meta Manager Administrator FIGURE 22 Search Overrides - Bounding_Coordinates Form At the top of the form inside the title bar will be the metadata group for which a search override is being defined. The Table and Search Type selection boxes provide selection of the table name and search type. The rows in the grid below will be updated according to the selection of Search Type. The fields associated with the Search Override Definition form are explained as follows: Type: The type of search value, either fixed or database. Search Value: Override Element Type: Search Mask: Field Type: The appropriate column from the search table for the corresponding Override Element Type. This value will come from either a field in the table (if Type database is selected) or will be entered by the user (if Type Fixed is selected). One of the override element types defined within Meta Manager (auto-filled by the selection of Search Type). This is the SQL construct (if any) that must be applied to the value presented in the search request by the client before it can be compared to the Search Value. (e.g., Z39.50 dates are passed as YYYYMMDD, they must be converted to a database DATE format if a native DATE field is being used. This would require a search mask such as to_date( %s, YYYYMMDD ). The %s is replaced with the value passed in the search request.) Note: to_date( %s, YYYYMMDD ) is the default search mask if the Data Type of the element is DATE. The database field type (i.e., NUMBER, CHAR, DECIMAL, etc.). Note: If the search value type is fixed, the Field Type will be VARCHAR2. 3. Click inside the first row of the grid under the Type field. If the database option is chosen, a selection box will appear in the row to choose a Search Value from the table. If applicable, enter the Search Mask to apply to the search value entered on the web site. If the fixed option is selected in the Type field, enter a value in the Search Value field. The Field Type field will be automatically filled, based on the values in the Type and Search Value fields. Continue this process for each row in the grid. by Compusult Limited 1998-2003 - Document No. 901-003 5-20

Meta Manager Administrator 4. Select the Save button located at the bottom of the screen. The Search Overrides - Bounding Coordinates window will disappear and a message confirming that the database has been updated will appear. Click OK to dismiss the confirmation dialog box and return to the Meta Manager main window. 5.4 Copying a Collection Data administrators can copy a collection from a database to a new collection in a database, preventing the user from repeating all the mappings involved in creating a collection. This function also ensures that any tables required for the new collection are accessible to the current Meta Manager user. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database in which the collection to be copied resides. 2. Select Open... from the Collection menu located on the main window menubar. The Select Collection to Open dialog box will appear. 3. Select a Metadata Standard and the Collection to copy from the respective lists. The Metadata Tree structure for the collection will be loaded from the database. 4. Select Copy... from the Collection menu located on the main window menubar. The Collection Copy - New Collection Data form will appear as shown in Figure 23. FIGURE 23 Collection Copy - New Collection Data Form 5. Enter the new collection name in the Collection field on the Collection Copy form and select Copy. A box will be displayed indicating the copy progress. Once the copy is complete, the box will disappear and the newly copied collection will open. 5.5 Importing a Data Collection Data administrators can import collections from a remote Meta Manager database to the currently active database. This prevents the user from repeating all the mappings involved in creating a collection. However, this function only imports the Meta Manager mappings, it does not import any tables that the collection requires. The administrator of the collections must ensure any required tables become accessible to the current Meta Manager user. by Compusult Limited 1998-2003 - Document No. 901-003 5-21

Meta Manager Administrator Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database in which the new collection will reside. 2. Select Import from the Collection menu located at the top of the screen. The ODBC Data Source to Import From dialog box will appear as shown in Figure 24. FIGURE 24 ODBC Data Source to Import From 3. Provide the information to log in to the remote database that contains the collection to import and select OK. The Select Collection to Import screen will appear. 4. Select the metadata standard and then the collection to import, then select OK. Meta Manager will now load the collection into memory. 5. Provide a name for the new collection in the Collection Import form (see Figure 25) and select Import. This name can be the same as the remote collection, if desired. Meta Manager will now import the collection into the active database. When the collection has been successfully imported, Meta Manager will open the new collection. FIGURE 25 Collection Import Form by Compusult Limited 1998-2003 - Document No. 901-003 5-22

Meta Manager Administrator 5.6 Globally Renaming Tables in a Data Collection Data administrators can globally rename the tables used in a collection. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database in which the collection to be updated resides. 2. Select Rename Table... from the Tools menu located at the top of the screen. The Rename Table dialog box, containing a drop-down list for metadata standards and collections, will appear as illustrated in Figure 26. FIGURE 26 Rename Table Form 3. Select the desired Standard and Collection. 4. Select the Table Name from the pick list provided. 5. Provide the New Table Name and select Save. Meta Manager will now globally change the table name for the selected collection, except where the table name is embedded in a complex SQL function such as decode or to_date. 6. Repeat Step 1 to Step 5 for each table name you wish to change. 7. Click the Close button to return to the main Meta Manager window. 5.7 Deleting a Collection Data administrators can delete a collection from the Meta Manager database. The procedure for deleting a collection is as follows: by Compusult Limited 1998-2003 - Document No. 901-003 5-23

Meta Manager Administrator Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database in which the collection to be deleted resides. 2. Select Open... from the Collection menu located on the main window menubar. The Select Collection to Open dialog box will appear. 3. Select a Metadata Standard and the Collection name to delete from the respective lists. The Metadata Tree structure for the collection will be loaded from the database. 4. Select Delete from the Collection menu located on the main window menubar. A message asking for confirmation to delete the collection will appear. 5. Click the Yes button to delete the collection. A message box will appear confirming the database has been updated. Click OK to dismiss the confirmation message box and return to the Meta Manager main window. 5.8 Collection Properties Data administrators can use the collection properties facility to rename a collection, to add tables to a collection, to change a collection s primary table or primary key, or to add Enhanced Text Searching to the collection using the Auto Harvest option. The Enhanced Text Search takes every text field mapped in the collection and compares it to a search value in a keyword list, resulting in faster searching of the collection. When the Auto Harvest option is selected, the Modification Date Field must also be filled with a date data type from the Primary Table, otherwise the Auto Harvest will not work. Whenever an element is mapped or updated and it s Text Search Field is set to INCLUDE (see Section 5.2.4.1 and Section 5.2.4.2). the Auto Harvest option will update the keyword list for the Enhanced Text Search. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the metadata mappings that you wish to view or edit. 2. Select Open... from the Collection menu located on the main window menubar. The Select Collection to Open dialog box will appear. 3. Select a Metadata Standard and the Collection name to open. The Metadata Tree structure for the collection will be loaded from the database. 4. Select Properties... from the Collection menu. The Collection - Properties dialog box will appear as illustrated in Figure 27. by Compusult Limited 1998-2003 - Document No. 901-003 5-24

Meta Manager Administrator FIGURE 27 Collection - Properties Dialog Box 5. To change the name of the collection, enter a new name in the Collection Name field. To change the primary table for the collection, select the down-arrow button located next to the Table Name field and select a table from the drop-down list. To change the primary key, select the down-arrow button located next to the Primary Key Field and select a new primary key from the drop-down list. To add or change the modification date, select the down-arrow button located next to the Modification Date Field. A drop-down list will appear displaying fields from the primary table. The Modification Date field must be a date data type from the table. To turn on/off Auto Harvest, click on the down-arrow button next to the Auto Harvest Field and select Yes or No. To add a table to the collection, click the Add Tables... button. The Add Tables form will appear (see Section 5.2.2). 6. Select the Save button located at the bottom of the Collection - Properties form. The form will disappear and a dialog box confirming the update to the database will appear. 7. Select OK in the confirmation box to return to the Meta Manager main window. 5.9 Metadata Mapping Reports A data collection report can be generated to list all of the metadata standards group and element definitions. The report is structured to provide a hierarchical view of a data collection mapped to the metadata standard. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the metadata mappings for which you want a report. 2. Select Report... from the Collection menu located at the top of the screen (or select the Reports... toolbar button). The Open Report form will appear as shown in Figure 28. by Compusult Limited 1998-2003 - Document No. 901-003 5-25

Meta Manager Administrator FIGURE 28 Open Report Form 3. Select the Metadata Standard Name from the pull-down list. 4. Select the Collection Name of the collection for which you want a report. 5. Select the Report type you want and click the Generate button located at the bottom of the screen. 6. The Meta Manager report will appear for that collection. When finished viewing the report, select Exit from the File menu located at the top of the screen. 5.10 Syntax Checker The syntax checker attempts to verify the display value and search value after the user completes each definition. Functions are compared to entries in the database table Metadata_SQL_functions to validate the name of the function and the number of parameters. The syntax checker will also ensure that the user has the correct matching brackets and/or quotes. 5.10.1 Add New SQL Functions This routine provides the ability to add a new SQL function to Meta Manager for use when referencing tables in the database. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the data to be mapped. 2. Select Syntax Checker... from the Tools menu located at the top of the screen. The Syntax Checker Functions form will appear as shown in Figure 29. by Compusult Limited 1998-2003 - Document No. 901-003 5-26

Meta Manager Administrator FIGURE 29 Syntax Checker Functions Form 3. Click the New button located at the bottom left of the form. The Add Syntax Checker Function form will be displayed as shown in Figure 30. FIGURE 30 Add Syntax Checker Function Form 4. Enter the new Function Name and the Number of Parameters the function requires and select Save. The Add Syntax Checker Function form will disappear and a message confirming that the function has been added will appear. Click OK to dismiss the message box and return to the Syntax Checker Functions form. The new function will now be displayed in the functions list. 5.10.2 Edit SQL Functions This routine provides the ability to modify or delete existing functions in Meta Manger. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the data to be mapped. 2. Select SyntaxChecker... from the Tools menu located at the top of the screen. The Syntax Checker Functions form will be displayed (see Figure 29). by Compusult Limited 1998-2003 - Document No. 901-003 5-27

Meta Manager Administrator 3. Highlight the function to edit and click the Edit button located at the bottom of the form. The Modify Syntax Checker Function form will appear as shown in Figure 31 FIGURE 31 Modify Syntax Checker Function Form 4. To delete the selected function, select the Delete button. A message box will appear asking for confirmation to delete the selected function. Select Yes to confirm or No to abort. To edit an existing function, make the necessary changes in the Number of Parameters and/or Function Name fields and select the Save button. The Modify Syntax Checker Function window will disappear and a message box confirming the changes will be displayed. Click OK to return to the Syntax Checker Functions form. The changes made will be reflected in the Functions list box. 5.11 Server Parameters The Server Parameters routine enables modification of the zserver registry keys set within the Meta Manager environment. Note: The Server Parameters routine is only available if a Meta Manager server has been installed. 5.11.1 Adding a New Server Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the data to be mapped. 2. Select Server Parameters... from the Tools menu located at the top of the screen. The Server List form will be displayed as shown in Figure 32. by Compusult Limited 1998-2003 - Document No. 901-003 5-28

Meta Manager Administrator. FIGURE 32 Server List Form 3. Click the New button located at the bottom of the form. The New Server Parameters form will be displayed as illustrated in Figure 33. FIGURE 33 New Server Parameters Form 4. The Meta Manager - Server Parameters form will update values located under the key HKEY_LOCAL_MACHINE/SOFTWARE/Compusult Limited/Meta Manger/Server. The fields associated with the New Server Parameters form are as follows: Server Name: User Name: Password: The name of the server to which Meta Manager connects. The username to access the database containing the Meta Manager database tables. The password to access the database containing the Meta Manager database tables. by Compusult Limited 1998-2003 - Document No. 901-003 5-29

Meta Manager Administrator ODBC DSN: TCP Port: MetaData Profile: Log Info: Maximum Results: The data source name configured for connectivity to the database containing the Meta Manager tables. The port number used by the Meta Manager Server. This should be the same value that you entered when installing the Meta Manager software. The profile to be used by the Meta Manager Server. This allows the user to select the type of logging information for Meta Manager. If Default Messages is selected, only the basic information is logged. If Default Messages with Debug Info is selected, both log information and debugging is obtained. Otherwise, the user can select to have no log information. The maximum number of results to return for a given search. 5. Enter the information for the Server Name, User Name, Password, ODBC DSN, TCP Port, MetaData Profile and Maximum Results fields. 6. Select the Save button located at the bottom of the form. A message box will appear confirming the installation of the new server and the update of the registry keys. 7. Click the OK button to dismiss the confirmation dialog box and return to the Server List form. The new server added will appear under the Server Name heading on the Server List form. 8. Click the Close button on the Server List form to return to the Meta Manager main window. 5.11.2 Editing or Deleting an Existing Server Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the data to be mapped. 2. Select Server Parameters... from the Tools menu located at the top of the screen. The Server List form will be displayed as shown in Figure 32. 3. Select the name of the server under the Server Name heading on the Server List form and click the Edit button. The Edit Server Parameters form will appear with the Server Name field filled with the name of the server to edit or delete (see Figure 34). by Compusult Limited 1998-2003 - Document No. 901-003 5-30

Meta Manager Administrator FIGURE 34 Edit Server Parameters Form 4. To edit the server parameters, enter any new information into the appropriate fields on the form and select the Save button. The Edit Server Parameters form will disappear and the Server List form will be displayed. Click the Close button to return to the Meta Manager main window. 5. To delete the server and its parameters, click the Delete button located at the bottom of the Edit Server Parameters form. A message box will be displayed asking for confirmation to delete the server and its registry entries. 6. Click the Yes button to confirm the deletion of the server and return to the Server List form. 7. Click the Close button to return to the Meta Manager main window. 5.12 Licence Information The Licence Information form provides the ability to enter, modify or retrieve the Meta Manager licence for a server. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database for which to enter server information. 2. Select Licence Information... from the Help menu located on the main window menubar. The Licence Information form will be displayed as illustrated in Figure 35. by Compusult Limited 1998-2003 - Document No. 901-003 5-31

Meta Manager Administrator FIGURE 35 Licence Information Form 3. Select the Server Name from the drop-down list. 4. Enter the Licence Key in the appropriate field. 5. Click the Save button. The licence key will be verified and the Licence Information form will disappear. by Compusult Limited 1998-2003 - Document No. 901-003 5-32

CHAPTER 6 Tutorial This tutorial serves as an introduction and overview to using Meta Manager. It describes, in step-by-step instructions, the features of Meta Manager and provides the necessary background required for creating and mapping your own metadata standard-enabled collections. It also includes directions for setting up and administering the database configurations. In this tutorial, the FGDC GEO Profile is used for demonstration purposes. There are differences between interaction with Oracle and Microsoft Access. Meta Manager provides the ability to use internal database functions. Functions such as TO_CHAR and TO_DATE can be utilized for searching and display purposes. When using database functions, refer to the appropriate database documentation for correct usage and syntax. The tutorial consists of eleven lessons, all using the FGDC GEO Profile: Lesson 1 - Verifying Your Installation Lesson 2 - Connecting and Testing Your Server with a Compusult Gateway Lesson 3 - Configuring the Master Meta Manager Collection Lesson 4 - Creating a New Meta Manager Collection Lesson 5 - Configuring a Meta Manager Collection for Enhanced Text Searching Lesson 6 - Creating Database Table Relationships Lesson 7 - Configuring a New Meta Manager Collection Lesson 8 - Mapping Compound Elements Using Search Overrides Lesson 9 - Globally Changing Data Element Mappings Lesson 10 - Executing the Meta Manager Report Lesson 11 - Configuring the Windows NT/2000 Meta Manager Server Registry The tutorial is presented as an option during the install process and must be installed prior to performing the exercises. You will also require the RDBMS tutorial account username and password for logging into the system. This tutorial assumes that you have used the username mmdemo and password mmdemo for the tutorial account. If you are using Microsoft Access, a username and password is not required. The tutorial account contains the following tables: MONTANA - An Oracle table containing descriptions of Maps of Montana. This table was created using information extracted from the Montana State Library National Resource Information System. S57METADATA - A table containing S57 hydrographic chart products and metadata information. S57DATA - A table containing geographic extents and S57 file format definitions. by Compusult Limited 1998-2003 - Document No. 901-003 6-1

Tutorial AGENCY - A table containing agency and contact information for products contained in the S57METADATA table. S57METADATA Product and Metadata Definitions One-to-One Many-to-One S57DATA Geographic Extents File Format Definitions AGENCY Agency and Contact Information Preconfigured Meta Manager Collection MONTANA FIGURE 36 Tutorial Database Configuration This tutorial is meant to be completed sequentially. In each lesson, you ll build upon the results of the previous lesson. If you jump ahead, you may not have the data screens you need to perform the tasks being covered in that lesson. The tutorial assumes that you are using the Meta Manager administrative interface in a Microsoft Windows 95/98/NT/2000 environment and that the software has been successfully installed. by Compusult Limited 1998-2003 - Document No. 901-003 6-2

Tutorial 6.1 Lesson 1 - Verifying Your Installation The Meta Manager tutorial has a preconfigured collection, MAPS OF MONTANA. This collection is provided for the purpose of verification of the installation process. Procedure 1. Launch the Meta Manager application. The ODBC Data Source form will be displayed (see Figure 37). FIGURE 37 ODBC Data Source Form 2. If applicable, enter a valid Username and Password to access the Database. To log onto the SQL Server tutorial database, use the username and password you entered during the installation process or none if you used Windows Authentication. 3. Select the down-arrow button next to the ODBC DSN field to retrieve a list of previously used data sources and select the required data source to connect to the database. Note: If the required data source cannot be found in the list, click on the ODBC DSN button to get a list of all the available data sources. Select the data source name configured for the database containing the Meta Manager database tables. If connecting to an Oracle database, the Oracle8 ODBC Driver Connect dialog box will appear as illustrated in Figure 38. If connecting to an SQL Server database, the SQL Server Login dialog box will appear as illustrated in Figure 39. If applicable, enter a valid Username and Password to access the database and select OK. FIGURE 38 Oracle 8 ODBC Driver Connect by Compusult Limited 1998-2003 - Document No. 901-003 6-3

Tutorial FIGURE 39 SQL Server Login 4. Select OK on the ODBC Data Source screen. The ODBC Data Source screen will be dismissed and Meta Manager will connect to the target database. The main Meta Manager window will be displayed as shown in Figure 40. Main Menu Bar FIGURE 40 Meta Manager Main Window by Compusult Limited 1998-2003 - Document No. 901-003 6-4

Tutorial 5. Select Open... from the Collection pull-down menu located on the main window menu bar. The Select Collection to Open dialog box will appear as illustrated in Figure 41. FIGURE 41 Select Collection to Open 6. Select the metadata standard FGDC GEO Profile from the Metadata Standard pull-down list. 7. Select the collection MAPS OF MONTANA from the Collection pull-down list. Meta Manager will now load the metadata tree. 6.1.1 What Did You Do In this lesson you went through the process of launching the application and verifying the installation. 6.1.2 What Did You Learn How to launch the client-side application. by Compusult Limited 1998-2003 - Document No. 901-003 6-5

Tutorial 6.2 Lesson 2 - Connecting and Testing Your Server with a Compusult Gateway Compusult Limited has provided a simple gateway for testing and verifying Meta Manager applications and installations. This gateway is provided solely for the purpose of testing and should not be used as a clearinghouse. Procedure 1. Launch your WWW Browser and open the url http://www.metadatamanager.com. The Meta Manager web site will be displayed. 2. Select the Support button. The Meta Manager Customer Support page will be displayed. Select the link Meta Manager Configuration Tester/Gateway. The Clearinghouse User Login page will be launched as illustrated in Figure 42. FIGURE 42 Clearinghouse User Login Page by Compusult Limited 1998-2003 - Document No. 901-003 6-6

Tutorial 3. Enter the Meta Manager support username and password that was supplied by Compusult Limited and select the Login button located at the bottom of the page. The Meta Manager Gateway page will be displayed. 4. Select the Maintenance button. The Add/Edit Clearinghouse Databases page will be displayed. 5. Select the Add button. The Enter new database information page will be displayed as illustrated in Figure 43. FIGURE 43 Enter New Database Information Page by Compusult Limited 1998-2003 - Document No. 901-003 6-7

Tutorial Each of the fields on the page must be filled in. The definition of the fields are as follows: Server - This is the hostname of the machine running your Meta Manager Server Software. This should be the same value that you entered when installing the Meta Manager software. Port - This is the port number that is used to connect to your Meta Manager Server. This should be the same value that you entered when installing the Meta Manager software. Name - The name of the dataset. This is the collection name that you entered when configuring the Meta Manager software for this collection. In this case, enter the value MAPS OF MONTANA. Ensure that you use all capitals. Search Description - This is the label that will be displayed for your dataset in the list of datasets on the WWW page. In this case, enter the value Maps of Montana. Online - Whether this collection will be available for online searching. Profile Format - The Metadata Standard that this collection follows. Begin Date/End Date - This is the date range that the collection data falls under. MinLat/MaxLat/MinLong/MaxLong - These fields specify the bounding geographic coordinates that a search will fall under. Choose Server Profile - Displays Options available for Summary and Full Present Sets. 6. Select the Submit button located at the bottom of the page. Your server and gateway configuration will be stored and the Select Databases to Search page will be displayed as illustrated in Figure 44. by Compusult Limited 1998-2003 - Document No. 901-003 6-8

Tutorial FIGURE 44 Select Databases to Search Page 7. Select the Maps of Montana entry check box. 8. Select the Search button. The gateway software will now connect to your local server and database and a Clearinghouse Search Specification page will be presented (see Figure 45). by Compusult Limited 1998-2003 - Document No. 901-003 6-9

Tutorial FIGURE 45 Clearinghouse Search Specification Page 9. Select the Use Spatial Coverage toggle button and select the Search button located at the bottom of the page. The Results Summary page appears as in Figure 46. by Compusult Limited 1998-2003 - Document No. 901-003 6-10

Tutorial FIGURE 46 Results Summary Page by Compusult Limited 1998-2003 - Document No. 901-003 6-11

Tutorial 10. Select the checkbox corresponding to the Maps of Montana collection and select the Results button. All records in the database are retrieved and displayed as illustrated in Figure 47. FIGURE 47 Search Results Page The page illustrated above contains a link to the datasets hit during the query process. Selecting one of the Full Result Set links will generate a full metadata presentation. 6.2.1 What Did You Do In this lesson you registered the Maps of Montana metadata collection in the Compusult Limited test gateway. You also used an ISITE WWW Browser client to issue queries against the Maps of Montana metadata collection. by Compusult Limited 1998-2003 - Document No. 901-003 6-12

Tutorial 6.2.2 What Did You Learn In order for your database to be searchable by clearinghouses, the database server must be registered with the clearinghouse. After the collection is registered, users can search your database by using a client connected to a clearinghouse/gateway. The most common implementation of clearinghouse client search software is WWW Browser-based. Once a Meta Manager collection has been mapped, you can use the Compusult Limited test gateway for verification of the collections prior to registration in a clearinghouse. by Compusult Limited 1998-2003 - Document No. 901-003 6-13

Tutorial 6.3 Lesson 3 - Configuring the Master Meta Manager Collection The Meta Manager Master Collection contains the definitions of FGDC Compound Elements and Data Elements that will be used throughout all collections that are mapped to the standard. Each time you create a new GEO Profile collection, the Master Collection is copied with the default mappings. Procedure 1. Launch the Meta Manager application. The ODBC Data Source form will be displayed (see Figure 48). The ODBC DSN field will be filled with the name of the last successful connection made in Meta Manager Administrator. FIGURE 48 ODBC Data Source Form 2. If applicable, enter a valid Username and Password to access the database. Note: a username and password is not required for the Microsoft Access tutorial database. 3. Select the down-arrow button next to the ODBC DSN field to retrieve a list of previously used data sources and select the required data source to connect to the database. Note: If the required data source cannot be found in the list, click on the ODBC DSN button to get a list of all the available data sources. Select the data source name configured for the database containing the Meta Manager database tables. If connecting to an Oracle database, the Oracle8 ODBC Driver Connect dialog box will appear as illustrated in Figure 49. If connecting to an SQL Server database, the SQL Server Login dialog box will appear as illustrated in Figure 50. If applicable, enter a valid Username and Password to access the database and select OK. by Compusult Limited 1998-2003 - Document No. 901-003 6-14

Tutorial FIGURE 49 Oracle 8 ODBC Driver Connect FIGURE 50 SQL Server Login 4. Select OK on the ODBC Data Source screen. The ODBC Data Source screen will be dismissed and Meta Manager will connect to the target database. 5. Select Open... from the Collections drop-down menu in the main window menu bar (or click the Open toolbar button). The Select Collection to Open dialog box will appear, as illustrated in Figure 51. FIGURE 51 Select Collection to Open Form by Compusult Limited 1998-2003 - Document No. 901-003 6-15

Tutorial 6. Select the metadata standard FGDC GEO Profile from the Metadata Standard pull-down list in the Select Collection to Open dialog box. 7. Select the collection Master from the Collection list box in the Select Collection to Open dialog box. Meta Manager will now load the metadata tree as shown in Figure 52. FIGURE 52 Meta Manager Tree Control The following steps will guide you through the process of mapping GEO Profile Data Elements to Fixed Values (constant values that are not mapped to database Tables). 8. To expand the metadata tree, select the + next to Metadata Group. The left side of the screen is a tree representation of the metadata standard. The right side of the screen displays the properties and mappings of the currently selected element. 9. Select the data element Publication_Place in the tree, located at the path Metadata/ Data_Quality_Information/Lineage/Source_Information/Source_Citation/ Citation_Information/Publication_Information. Select New Mapping... from the Edit menu located at the top of the screen. The Element Mapping screen will appear as shown in Figure 53. Alternatively, you may right-click on the Publication_Place data element and select New Mapping... from the menu. by Compusult Limited 1998-2003 - Document No. 901-003 6-16

Tutorial FIGURE 53 Element Mapping Form (Database Values) 10. Select the Fixed toggle field. The Fixed Value text box will be displayed in the Element Mapping window as illustrated in Figure 54. FIGURE 54 Element Mapping Form (Fixed Values) 11. Enter the value St. John s, Newfoundland, Canada in the Fixed Value text box. 12. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 13. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 14. Right-click on element name Publisher and select the New Mapping... menu item. The Element Mapping window will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-17

Tutorial 15. Select the Fixed toggle field. The Fixed Value text box will be displayed in the Element Mapping window. 16. Enter the value World Hydrographic Office in the Fixed Value text box. 17. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 18. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 19. Use the scroll bars to locate element Geospatial_Data_Presentation_Form. Right-click on element name Geospatial_Data_Presentation_Form and select the New Mapping... menu item. The Element Mapping window will be displayed. 20. Select the Fixed toggle field. The Fixed Value text box will be displayed in the Element Mapping window. 21. Enter the value Map in the Fixed Value text box. 22. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 23. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 24. Right-click on element name Online_Linkage and select the New Mapping... menu item. The Element Mapping window will be displayed. 25. Select the Fixed toggle field. The Fixed Value text box will be displayed in the Element Mapping window. 26. Enter the value http://www.metadatamanager.com in the Fixed Value text box. 27. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 28. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 6.3.1 What Did You Do In this lesson you performed the following tasks: You used the Meta Manager Administration interface to access the master collection for mapping element definitions that will be common to all subsequent collections created. You navigated through the metadata groups to identify metadata elements that will be common to all collections created within the database. You mapped fixed values to data elements: Publication_Place; Publisher; Geospatial_Data_Presentation_Form; and, Online_Linkage. by Compusult Limited 1998-2003 - Document No. 901-003 6-18

Tutorial 6.3.2 What Did You Learn The standard provides a common set of terminology and definitions for the documentation of digital geospatial data. The standard establishes the names of data elements and compound elements (groups of data elements) to be used for these purposes, the definitions of these compound elements and data elements, and information about the values that are to be provided for the data elements. The first task associated with configuring a Meta Manager database is to map values in the master collection that will be common to all collections created subsequently. A new collection is created by copying the master collection with the default values that have been assigned. by Compusult Limited 1998-2003 - Document No. 901-003 6-19

Tutorial 6.4 Lesson 4 - Creating a New Meta Manager Collection A new collection is required to store the GEO Profile definitions that will be associated with the metadata definitions. Procedure 1. Select New... from the Collection menu located at the top of the screen (or click the New... toolbar button on the main window). The Collection - New form will be displayed as shown in Figure 55.. FIGURE 55 Collection - New Form 2. In the Standard Name pull-down menu, select FGDC GEO Profile. 3. In the Collection Name data entry field, enter the name S57 HYDROGRAPHIC DATA. 4. Click the Next... button located at the bottom of the form. The Add Tables form will appear. If you are using an Oracle database, the Add Tables form will appear as shown in Figure 56. FIGURE 56 Add Tables (Oracle) Form If you are using a Microsoft Access database, the Add Tables form will appear as shown in Figure 57. by Compusult Limited 1998-2003 - Document No. 901-003 6-20

Tutorial FIGURE 57 Add Tables (MS Access) Form If you are using an SQL Server database, the Add/Remove Tables form will appear as shown in Figure 58. FIGURE 58 Add/Remove Tables (SQL Server) Form 5. In the Tables list box, select the database table MMDEMO.S57METADATA and click the >> button located between the Tables list box and the Meta Manager Tables list box. The selected table(s) will now appear in the list under Meta Manager Tables. To remove tables from the Meta Manager Tables list, click the << button. If you are using the Microsoft Access tutorial, select an MS Access file (*.mdb file) from the Open... button. The Tables list will be populated with tables from the selected MS Access file. Note: The database table names will be listed without a username prefix so you would pick S57METADATA. If you are using the SQL Server tutorial, select the Tutorial catalog from the Catalog pull-down list. The Tables list will be populated with tables from the selected catalog. Note: The database table names will be listed with the prefix Tutorial.. so you would pick the Tutorial..S57METADATA table. by Compusult Limited 1998-2003 - Document No. 901-003 6-21

Tutorial 6. Repeat Step 5 to add the MMDEMO.S57DATA and MMDEMO.AGENCY tables (S57DATA and AGENCY for MS Access, Tutorial..S57DATA and Tutorial..AGENCY for SQL Server). 7. Select the Next button at the bottom of the form. The Collection - New form will appear with the Collection Name field filled with the name provided in Step 3. The form will also contain fields for the primary Table Name and the Primary Key Field (see Figure 59). FIGURE 59 Collection - New Form 8. Select the value MMDEMO.S57METADATA in the Table Name pull-down menu (S57METADATA for MS Access, Tutorial..S57METADATA for SQL Server). 9. Select the value S57ID in the Primary Key Field pull-down menu. 10. Select the Save button located at the bottom of the Collections - New window. A Confirmation dialog box will be displayed. 11. Select OK. The Confirmation dialog box will be dismissed and the new collection will open. 12. Click the Close button on the Metadata Collection box to return to the Meta Manager main window. 6.4.1 What Did You Do In this lesson you created a Meta Manager collection for containing metadata definitions about the Hydrographic S57 datasets. All of the fields and element mappings contained in the Master Meta Manager collection were copied to the new collection. 6.4.2 What Did You Learn This lesson demonstrated the process required to create a new Meta Manager collection. This is the first step required to bring a new dataset collection on-line. by Compusult Limited 1998-2003 - Document No. 901-003 6-22

Tutorial 6.5 Lesson 5 - Configuring a Meta Manager Collection for Enhanced Text Searching Meta Manager provides the ability to perform Enhanced Text Searching on a collection, whereby mapped text elements are compared to a search value in a keyword list. This facility is used for the purpose of faster text searching when a Full Text search is selected on the Web Page. Procedure 1. Open the S57 HYDROGRAPHIC DATA collection by selecting Collection, Open... from the Meta Manager main menu (or select the Open... toolbar button). 2. Select Properties.. from the Collection drop-down menu located at the top of the screen (or click the Properties toolbar button). The Collection-Properties form will appear as shown in Figure 60. FIGURE 60 Collection-Properties Form 3. The Standard Name, Collection Name, Table Name and Primary Key fields should be pre-filled with the information supplied when the collection was created. Select the pull-down arrow next to the Modification Date field. A list of columns for the S57METADATA table will be displayed. 4. Select column name ISDT. NOTE: The Modification Date field must be of data type DATE (for Oracle) or DATETIME (for MS Access, SQL Server and Sybase). 5. Select the pull-down arrow next to the Auto Harvest field and select Yes. This will enable the Enhanced Text Search. 6. Click the Save button located at the bottom of the form. The Collection-Properties form will disappear and a Confirmation dialog box will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-23

Tutorial 7. Click the OK button in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the collection will be updated. 6.5.1 What Did You Do In this lesson you selected Enhanced Text Searching for the Collection by turning the Auto Harvest option on and by defining the Modification Date, which is used to determine when the keyword list should be updated. The modification date for the S57METADATA table is column ISDT. When an element is mapped or updated, the Text Search field must also be set to INCLUDE (See Lesson 7 - Configuring a New Meta Manager Collection on page 29.). When this is done, any text in the element mapping will be added to the keyword list when the Auto Harvest program runs again. 6.5.2 What Did You Learn The Meta Manager Z39.50 component uses database mappings applied using the Meta Manager Administrator to extract keywords and place them in a table for quick retrieval when a Full Text Search is selected on the Web Page by Compusult Limited 1998-2003 - Document No. 901-003 6-24

Tutorial 6.6 Lesson 6 - Creating Database Table Relationships Meta Manager provides the ability to establish linkages between database tables. This facility is used when a column in one table (key) is linked with a column in another table (key) for the purpose of extracting one or more columns that are identified by the database table keys. Procedure 1. Open the S57 HYDROGRAPHIC DATA collection by selecting Collection, Open... from the Meta Manager main menu (or select the Open... toolbar button). 2. Select Relationships... from the Collection menu located at the top of the screen. The Table Links form will appear as shown in Figure 61.. FIGURE 61 Table Links Form The fields associated with the Table Links form are defined as follows: Optional Table1 Column1 Table2 Column2 Relationship Indicates whether every row in Table1 has at least one corresponding row in Table2. First linked table. The column in Table1 that will refer to a column in Table2. Second linked table. The column in Table2 that will refer to a column in Table1. Description of the relationship between the first and second linked table. 3. Select the New button located at the bottom of the form. The Table Links - New form will appear (see Figure 62). by Compusult Limited 1998-2003 - Document No. 901-003 6-25

Tutorial FIGURE 62 Table Links - New Form The fields associated with the Table Links - New form are defined as follows: Collection Table1 Table2 Column1 Column2 Relationship Optional The relevant collection. First linked table. Second linked table. The column in Table1 that will refer to a column in Table2. The column in Table2 that will refer to a column in Table1. Description of the relationship between Table1 and Table2. Indicates whether every row in Table1 has at least one corresponding row in Table2. If you are using the Microsoft Access tutorial database, the database table names will be listed without a username prefix. If you are using the SQL Server tutorial database, the database table names will be listed with the prefix Tutorial... 4. In the Table1 pull-down menu, select the table MMDEMO.S57METADATA. 5. Select the pull-down menu arrow next to the Column1 data entry field. A list of available columns for the MMDEMO.S57METADATA table will be provided. 6. Select column name S57ID. 7. In the Table2 pull-down menu, select the table MMDEMO.S57DATA. 8. Select the pull-down menu arrow next to the Column2 data entry field. A list of available columns for the MMDEMO.S57DATA table will be provided. 9. Select column name S57ID. 10. Select the drop-down list arrow next to the Relationship field and select ONE-TO-ONE. 11. Select the drop-down list arrow next to the Optional field and select No. 12. Select the Save button located at the bottom of the Table Links - New window. The Table Links - New window will disappear and a Confirmation window will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-26

Tutorial 13. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the list box in the Table Links window will be updated with the table links created. 14. Select the New button located at the bottom of the Table Links window. The Table Links - New window will be displayed. 15. In the Table1 pull-down menu, select the table MMDEMO.S57METADATA. 16. Select the pull-down menu arrow next to the Column1 data entry field. A list of the available columns for the MMDEMO.S57METADATA table will be provided. 17. Select column name AGENCY_ID. 18. In the Table2 pull-down menu, select the table MMDEMO.AGENCY. 19. Select the pull-down menu arrow next to the Column2 data entry field. A list of the available columns for the MMDEMO.AGENCY table will be provided. 20. Select column name ORGANIZATION_ID. 21. Select the drop-down list arrow next to the Relationship field and select ONE-TO-ONE. 22. Select the drop-down list arrow next to the Optional field and select No. 23. Select the Save button located at the bottom of the Table Links - New window. The Table Links - New window will disappear and a Confirmation dialog box will be displayed. 24. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the list box in the Table Links window will be updated with the table linkages (see Figure 63). FIGURE 63 Table Links Window 25. Select the Close button located at the bottom of the Table Links window. The Table Links window will be dismissed. 6.6.1 What Did You Do In this lesson you defined the tables and table linkages that the S57 Hydrographic Data collection will utilize when accessing the SQL database for looking up metadata definitions. In this case, the by Compusult Limited 1998-2003 - Document No. 901-003 6-27

Tutorial S57METADATA table contains the metadata product definitions for each of the S57 data products. The primary key for the S57METADATA table is column S57ID. A linkage was made to the table S57DATA. This table contains geographic extents and other information that is specific to each S57 dataset. The primary key for table S57DATA is also column SECOND_SEQ. A one-to-one relationship exists between the S57METADATA table and the S57DATA table. Table linkages were also made between tables S57METADATA and AGENCY. The AGENCY table contains information regarding the organization that is responsible for the production of the S57 dataset. The column AGENCY_ID is used as the key in the S57METADATA table and the column ORGANIZATION_ID is used as the key in the AGENCY table. A many-to-one relationship exists between the S57METADATA table and the AGENCY table. 6.6.2 What Did You Learn The Meta Manager Z39.50 component uses database mappings applied using the Meta Manager Administrator to extract metadata from one or more tables that exist in an SQL database. When metadata information about a collection is spread across multiple tables, the linkages between these tables are defined using the Links component of Meta Manager. Figure 36 illustrates the table linkages. by Compusult Limited 1998-2003 - Document No. 901-003 6-28

Tutorial 6.7 Lesson 7 - Configuring a New Meta Manager Collection The following procedure will demonstrate the configuration of a Meta Manager collection. You will apply fixed and database values to the GEO Profile definitions. If you are using the Microsoft Access tutorial database, the database table names will be listed without a username prefix. Procedure 1. Select Open... from the Collections drop-down menu in the main window menu bar (or click the Open... toolbar button). The Select Collection to Open dialog box will appear (see Figure 41). 2. Select the metadata standard FGDC GEO Profile from the Metadata Standard pull-down list. 3. Select the collection S57 HYDROGRAPHIC DATA from the Collection list box. Meta Manager will now load the metadata tree. 4. To expand the metadata tree, select the + next to Metadata. The left side of the screen is a tree representation of the metadata standard. The right side of the screen displays the properties and mappings of the currently selected element. 5. Select the data element Title in the tree, located at the path Metadata/Identification_Information/ Citation/Citation_Information. Select New Mapping... from the Edit menu located at the top of the screen or right-click on the Title element. The Element Mapping screen will appear as shown in Figure 64. 6. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. Notice that the drop-down list is populated with the table names that were assigned when table relationships were defined for the collection. 7. Select the table MMDEMO.S57METADATA. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.S57METADATA. 8. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.S57METADATA will be displayed in a drop-down list. 9. Select column name DSNM. The Display Value and Search Value data entry fields will be populated with the value DSNM. 10. Update the Display Value to have a meaningful name by placing the cursor in the Display Value data entry field and entering S57 Data Set in front of DSNM. (Ensure that there is a space before and after the ) If you are using Microsoft Access, enter S57 Data Set & in front of DSNM. If you are using SQL Server, enter S57 Data Set + in front of DSNM. by Compusult Limited 1998-2003 - Document No. 901-003 6-29

Tutorial FIGURE 64 Element Mapping (Database values) 11. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 12. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 13. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 14. Right-click on Originator and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 15. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 16. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 17. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in the table MMDEMO.AGENCY will be displayed in a drop-down list. 18. Select column name ORGANIZATION_NAME. The Display Value and Search Value data entry fields will be populated with the value ORGANIZATION_NAME. 19. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 20. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation window will be displayed. 21. Select OK in the Confirmation window. The Confirmation window will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 22. Right-click on Publication_Date and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-30

Tutorial 23. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 24. Select the table MMDEMO.S57METADATA. The Table Name box will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.S57METADATA. 25. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.S57METADATA will be displayed in a drop-down list. 26. Select column name ISDT. The Display Value and Search Value data entry fields will be populated with the value ISDT. 27. Update the Display Value field to display the correct format of the date by updating the field to contain TO_CHAR(MMDEMO.S57METADATA.ISDT, YYYYMMDD ). If you are using Microsoft Access, enter the value Format(S57METADATA.ISDT, YYYYMMDD ) If you are using SQL Server, enter the value CONVERT(VARCHAR, Tutorial..S57METADATA.ISDT, 112). The conversion number for converting from datetime to string in YYYYMMDD format is 112. 28. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 29. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 30. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 31. Right-click on Publication_Time and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 32. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 33. Select the table MMDEMO.S57METADATA. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.S57METADATA. 34. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.S57METADATA will be displayed in a drop-down list. 35. Select column name ISDT. The Display Value and Search Value data entry fields will be populated with the value ISDT. 36. Update the Display Value field to display the correct format of the date by updating the field to contain TO_CHAR(MMDEMO.S57METADATA.ISDT, HH24MISS ). If you are using Microsoft Access, enter the value Format(S57METADATA.ISDT, HHMMSS ). If you are using SQL Server, enter the value CONVERT(VARCHAR, Tutorial..S57METADATA, 108). The conversion number for converting from datetime to string in HHMMSS format is 108. 37. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 38. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-31

Tutorial 39. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 40. Right-click on Online_Linkage and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 41. Select the Fixed toggle button. The Fixed Value text box will be displayed in the Element Mapping window. 42. Enter the value http://www.metadatamanager.com in the Fixed Value text box. 43. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 44. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 45. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 46. Select the data element Contact Position in the tree, located at the path Metadata/ Identification_Information/Point_of_Contact/Contact_Information. Select New Mapping... from the Edit menu located at the top of the screen. The Element Mapping screen will appear. 47. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 48. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 49. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 50. Select column name CONTACT_POSITION. The Display Value and Search Value data entry fields will be populated with the value CONTACT_POSITION. 51. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 52. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 53. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 54. Right-click on Contact_Voice_Telephone and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 55. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 56. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 57. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 58. Select column name CONTACT_TELEPHONE. The Display Value and Search Value data entry fields will be populated with the value CONTACT_TELEPHONE. by Compusult Limited 1998-2003 - Document No. 901-003 6-32

Tutorial 59. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 60. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 61. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 62. Right-click on Contact_Facsimile_Telephone and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 63. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 64. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 65. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 66. Select column name CONTACT_FAX. The Display Value and Search Value data entry fields will be populated with the value CONTACT_FAX. 67. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 68. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 69. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 70. Right-click on Contact_Electronic_Mail_Address and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 71. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 72. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 73. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 74. Select column name EMAIL_ADDRESS. The Display Value and Search Value data entry fields will be populated with the value EMAIL_ADDRESS. 75. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 76. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 77. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 78. Right-click on Hours_of_Service and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-33

Tutorial 79. Select the Fixed toggle button. The Fixed Value text box will be displayed in the Element Mapping window. 80. Enter the value 08:30 AM to 05:00 PM EST in the Fixed Value text box. 81. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 82. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 83. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 84. Right-click on Contact_Instructions and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 85. Select the Fixed toggle button. The Fixed Value text box will be displayed in the Element Mapping window. 86. Enter the value Data product information may be obtained Monday to Friday during hours of service. in the Fixed Value text box. 87. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 88. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 89. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 90. Select the data element Contact_Person in the tree, located at path Metadata/ Identification_Information/Point_of_Contact/Contact_Information/*/ Contact_Person_Primary. Expand Group item Contact_Person_Primary. The form will be redisplayed with the elements available under group Contact_Person_Primary. 91. Select New Mapping... from the Edit menu located at the top of the screen. The Element Mapping form will be displayed. 92. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 93. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 94. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 95. Select column name CONTACT_LNAME. The Display Value and Search Value data entry fields will be populated with the value CONTACT_LNAME. 96. Update the Display Value data entry field to contain the first name and last name of the primary contact. Update the Display Value data entry field to contain: RTRIM(MMDEMO.AGENCY.CONTACT_FNAME) RTRIM(MMDEMO.AGENCY.CONTACT_LNAME). 97. If you are using Microsoft Access, enter the value: TRIM(AGENCY.CONTACT_FNAME) & & TRIM(AGENCY.CONTACT_LNAME). by Compusult Limited 1998-2003 - Document No. 901-003 6-34

Tutorial If you are using SQL Server, enter the value: RTRIM(Tutorial..AGENCY.CONTACT_FNAME) + + RTRIM(Tutorial..AGENCY.CONTACT_LNAME). 98. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 99. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 100. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 101. Right-click on Contact_Organization and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 102. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 103. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 104. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 105. Select column name ORGANIZATION_NAME. The Display Value and Search Value data entry fields will be populated with the value ORGANIZATION_NAME. 106. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 107. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 108. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 109. Select the data element Address_Type in the tree, located at the path Metadata/ Identification_Information/Point_of_Contact/Contact_Information/Contact_Address. The form will be re-displayed with the elements available under group Contact_Address. 110. Select New Mapping... from the Edit menu located at the top of the screen. The Element Mapping form will be displayed. 111. Select the Fixed toggle button. The Fixed Value text box will be displayed in the Element Mapping window. 112. Enter the value Mailing Address in the Fixed Value text box. 113. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 114. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 115. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 116. Right-click on Address and select New Mapping... from the pop-up menu. The Element Definition form will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-35

Tutorial 117. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 118. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 119. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 120. Select column name ADDRESS. The Display Value and Search Value data entry fields will be populated with the value ADDRESS. 121. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 122. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 123. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 124. Right-click on City and select New Mapping... The Element Mapping form will be displayed. 125. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 126. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 127. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 128. Select column name CITY. The Display Value and Search Value data entry fields will be populated with the value CITY. 129. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 130. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 131. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 132. Right-click on State_or_Province and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 133. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 134. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 135. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 136. Select column name PROVINCE. The Display Value and Search Value data entry fields will be populated with the value PROVINCE. 137. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. by Compusult Limited 1998-2003 - Document No. 901-003 6-36

Tutorial 138. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 139. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 140. Right-click on Postal_Code and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 141. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 142. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 143. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 144. Select column name POSTAL_CODE. The Display Value and Search Value data entry fields will be populated with the value POSTAL_CODE. 145. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 146. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 147. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 148. Right-click on Country and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 149. Click on the down-arrow button located next to the Table Name data entry field. The Table Name drop-down list will be displayed. 150. Select the table MMDEMO.AGENCY. The Table Name list will be dismissed and the data entry field for Table Name will be populated with the value MMDEMO.AGENCY. 151. Click on the down-arrow button located next to the Display Value data entry field. The columns contained in table MMDEMO.AGENCY will be displayed in a drop-down list. 152. Select column name COUNTRY. The Display Value and Search Value data entry fields will be populated with the value COUNTRY. 153. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 154. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 155. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 156. Select the data element Theme_Keyword_Thesaurus in the tree, located at the path Metadata/ Identification_Information/Keywords/Theme/*. The form will be re-displayed with the elements available under group Keywords. 157. Select New Mapping... from the Edit menu located at the top of the screen. The Element Mapping form will be displayed. by Compusult Limited 1998-2003 - Document No. 901-003 6-37

Tutorial 158. Select the Fixed toggle button. The Fixed Value text box will be displayed in the Element Mapping window. 159. Click the Keywords... button located on the right side of the Element Mapping window. The Global Change Master Directory Keywords form will appear as illustrated in Figure 65. FIGURE 65 Global Change Master Directory Keywords Form 160. Click on the down-arrow button located next to the Theme field and select GCMD. 161. Click on the down-arrow button located next to the Category field and select EARTH SCIENCE. 162. Click on the down-arrow button located next to the Topic field and select HYDROSPHERE. 163. Click on the down-arrow button located next to the Term field and select Ground Water. 164. Click on the down-arrow button located next to the Variable field and select Groundwater Quality. 165. Select the Save button located on the left side of the form. The Global Change Master Directory Keywords form will disappear and the Element Mapping form will be displayed. All values selected on the Global Change Master Directory Keywords form will be displayed in the Fixed Value field on the Element Mapping Form. 166. Select the pull-down arrow next to the Text Search field at the top of the Element Mapping form and select INCLUDE. The element will be included in the Enhanced Text Search. 167. Select the Save button located at the bottom of the Element Mapping form. A message box confirming the database update will be displayed. 168. Click OK to dismiss the message box. The right side of the Meta Manager main window will be updated with the values selected in the Global Change Master Directory Keywords window. 6.7.1 What Did You Do In this lesson you performed the following tasks: by Compusult Limited 1998-2003 - Document No. 901-003 6-38

Tutorial You used Meta Manager to access the new collection for mapping element definitions that are specific to the new collection. You navigated through the metadata groups to identify metadata elements that will be mapped to the new collection. You mapped fixed values to data elements. You mapped keywords using the Global Change Master Directory Keywords. You mapped database fields to data elements. You applied database functions used in formatting the display of database fields mapped to metadata elements. You concatenated database fields to be used in the display of a selected metadata element. You edited mappings so they could be included in Enhanced Text Searching. 6.7.2 What Did You Learn Meta Manager provides an open interface for defining and mapping metadata elements to database and fixed values. You can also concatenate database fields or combine database fields and text to create a more meaningful display value for a metadata element. Meta Manager provides the ability to include standard database functions that can be used in the manipulation or conversion of database fields prior to displaying the values as metadata elements. Meta Manager also provides the ability to include element mappings in the Enhanced Text Search. The mappings that are applied to a new Meta Manager collection are specific to that collection. by Compusult Limited 1998-2003 - Document No. 901-003 6-39

Tutorial 6.8 Lesson 8 - Mapping Compound Elements Using Search Overrides The following procedure will illustrate the process used to apply search overrides to selected metadata group elements. If you are using the Microsoft Access tutorial database, the database table names will be listed without a username prefix. Procedure 1. Launch the Meta Manager application, connect to the Meta Manager database housing the Data Collection to be mapped and open the S57 HYDROGRAPHIC Data collection. 2. Navigate to the compound element Bounding_Coordinates located at the path Metadata/ Indentification_Information/Spatial_Domain. Right-click on the element and select Search Override... from the menu. The Search Overrides - Bounding Coordinates form will be displayed as shown in Figure 66. FIGURE 66 Search Overrides - Bounding Coordinates Form At the top of the form will be the Table and Search Type selection boxes to provide selection of the table name and search type. The rows in the grid below will be updated according to the selection of Search Type. The fields associated with the Search Override - Bounding Coordinates form are explained as follows: Type: Search Value: Override Element Type: The type of search value, either fixed or database. The appropriate column from the search table for the corresponding Override Element Type. This value will come from either a field in the table (if Type Database is selected) or will be entered by the user (if Type Fixed is selected). One of the override element types defined within Meta Manager (auto-filled by the selection of Search Type). by Compusult Limited 1998-2003 - Document No. 901-003 6-40

Tutorial Search Mask: Field Type: This is the SQL construct (if any) that must be applied to the value presented in the search request by the client before it can be compared to the Search Value. (e.g., Z39.50 dates are passed as YYYYMMDD, they must be converted to a database DATE format if a native DATE field is being used. This would require a search mask such as to_date( %s, YYYYMMDD ). The %s is replaced with the value passed in the search request.) Note: to_date( %s, YYYYMMDD ) is the default search mask if the Data Type of the element is DATE. The database field type (i.e., NUMBER, CHAR, DECIMAL, etc.). Note: If the search value type is fixed, the Field Type will be VARCHAR2. 3. Select the pull-down arrow next to the Table field and select the table MMDEMO.S57DATA. 4. Select the pull-down arrow next to the Search Type field and select the BOUNDING BOX. The values under the Override Element Id field in the grid will automatically be filled with the override elements for search type BOUNDING BOX. 5. In the row containing the Override Element Type value MIN LAT, click inside the Type field. Select Database from the drop-down menu. 6. For the same row, click inside the Search Value field. A pull-down list will be displayed containing the fields in the table MMDEMO.S57DATA. 7. Click the down-arrow button and select the column name SLAT. The drop-down list will be dismissed and the data entry field for Search Value will be updated with the value SLAT. 8. In the row containing the Override Element Type value MIN LONG, click inside the Type field. Select Database from the drop-down menu. 9. For the same row, click inside the Search Value field. A pull-down list will be displayed containing the fields in the table MMDEMO.S57DATA. 10. Click the down-arrow button and select the column name WLON. The drop-down list will be dismissed and the data entry field for Search Value will be updated with the value WLON. 11. In the row containing the Override Element Type value MAX LAT, click inside the Type field. Select Database from the drop-down menu. 12. For the same row, click inside the Search Value field. A pull-down list will be displayed containing the fields in the table MMDEMO.S57DATA. 13. Click the down-arrow button and select the column name NLAT. The drop-down list will be dismissed and the data entry field for Search Value will be updated with the value NLAT. 14. In the row containing the Override Element Type value MAX LONG, click inside the Type field. Select Database from the drop-down menu. 15. For the same row, click inside the Search Value field. A pull-down list will be displayed containing the fields in the table MMDEMO.S57DATA. 16. Click the down-arrow button and select the column ELON. The drop-down list will be dismissed and the data entry field for Search Value will be updated with the value ELON. The Search Overrides - Bounding Coordinates form will now appear as illustrated in Figure 67. by Compusult Limited 1998-2003 - Document No. 901-003 6-41

Tutorial FIGURE 67 Search Overrides - Bounding_Coordinates Form 17. Select the Save button located at the bottom left of the Search Overrides - Bounding_Coordinates window. The Search Overrides - Bounding_Coordinates box will disappear and a Confirmation dialog box will be displayed. 18. Select the OK button to dismiss the Confirmation dialog box. 19. Expand group Bounding_Coordinates. The form will be re-displayed with the elements available under group Bounding_Coordinates. 20. Right-click on West_Bounding_Coordinate and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 21. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57HYDROGRAPHIC Data collection will be displayed. 22. Select table MMDEMO.S57DATA. The Table Name data entry field will be populated with the value MMDEMO.S57DATA. 23. Select the down-arrow button located next to the Display Value field. A drop-down list will be displayed containing the fields in the table MMDEMO.S57DATA. 24. Select field WLON. The Display Value and Search Value fields will be populated with the value WLON. 25. Select the pull-down arrow next to the Text Search field and select EXCLUDE. The element will be included in the Enhanced Text Search. 26. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 27. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 28. Right-click on East_Bounding_Coordinate and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 29. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57 HYDROGRAPHIC Data collection will be displayed. 30. Select table MMDEMO.S57DATA. The Table Name data entry field will be populated with the value MMDEMO.S57DATA. by Compusult Limited 1998-2003 - Document No. 901-003 6-42

Tutorial 31. Select the down-arrow button located next to the Display Value field. A drop-down list will be displayed containing the fields in table MMDEMO.S57DATA. 32. Select field ELON. The Display Value and Search Value fields will be populated with the value ELON. 33. Select the pull-down arrow next to the Text Search field and select EXCLUDE. The element will be included in the Enhanced Text Search. 34. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 35. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 36. Right-click on North_Bounding_Coordinate and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 37. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57 HYDROGRAPHIC Data collection will be displayed. 38. Select table MMDEMO.S57DATA. The Table Name data entry field will be populated with the value MMDEMO.S57DATA. 39. Select the down-arrow button located next to the Display Value field. A drop-down list will be displayed containing the fields in table MMDEMO.S57DATA. 40. Select field NLAT. The Display Value and Search Value fields will be populated with the value NLAT. 41. Select the pull-down arrow next to the Text Search field and select EXCLUDE. The element will be included in the Enhanced Text Search. 42. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 43. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 44. Right-click on South_Bounding_Coordinate and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 45. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57 HYDROGRAPHIC Data collection will be displayed. 46. Select table MMDEMO.S57DATA. The Table Name data entry field will be populated with the value MMDEMO.S57DATA. 47. Select the down-arrow button located next to the Display Value field. A drop-down list will be displayed containing the fields in table MMDEMO.S57DATA. 48. Select field SLAT. The Display Value and Search Value fields will be populated with the value SLAT. 49. Select the pull-down arrow next to the Text Search field and select EXCLUDE. The element will be included in the Enhanced Text Search. 50. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 51. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. You will now define a search override for the Time_Period_of_Content group. by Compusult Limited 1998-2003 - Document No. 901-003 6-43

Tutorial 52. Right-click on the group Time_Period_of_Content located at the path Metadata/ Identification_Information and select Search Overrides... from the menu. The Search Override Definition form will be displayed. 53. Select the pull-down arrow next to the Table field and select the table MMDEMO.S57METADATA. 54. Select the pull-down arrow next to the Search Type field. A drop-down list will be displayed containing the valid override search types. 55. Select DATE RANGE. The data entry field Search Type will be populated with the value DATE RANGE and the list box in the form will be updated with the override element for search type DATE RANGE. 56. Click inside the grid under the Type field and select Database from the drop-down menu. 57. Click inside the Search Value field. A pull-down list will be displayed containing the fields in the table MMDEMO.S57METADATA. 58. Click the down-arrow button and select the column name ISDT. The drop-down list will be dismissed and the data entry field for Search Value will be updated with the value ISDT. 59. Select the Save button located at the bottom left of the Search Override - Time_Period_of_Content window. The Search Override - Time_Period_of_Content box will disappear and a Confirmation dialog box will be displayed. 60. To return to the Meta Manager main window, select the OK button in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 61. Navigate to the element Calendar_Date located at the path Metadata/Identification_Information/ Time_Period_of_Content/Time_Period_Information/*/Single_Date_Time. Right-click on the element and select New Mapping... from the pop-up menu. The Element Mapping form will be displayed. 62. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57 HYDROGRAPHIC Data collection will be displayed. 63. Select the table MMDEMO.S57METADATA. The Table Name data entry field will be populated with the value MMDEMO.S57METADATA. 64. Click on the down-arrow button located next to the Display Value selection field and select column ISDT. The Display Value and Search Value data entry fields will be populated with the value ISDT. 65. Update the Display Value by placing the cursor in the Display Value data entry field and entering TO_CHAR(MMDEMO.S57METADATA.ISDT, YYYYMMDD ). If you are using Microsoft Access, enter the value format(s57metadata.isdt, YYYYMMDD ) If you are using SQL Server, enter the value CONVERT(VARCHAR, Tutorial..S57METADATA.ISDT, 112). 66. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 67. Select the Save button located in the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 68. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. by Compusult Limited 1998-2003 - Document No. 901-003 6-44

Tutorial 69. Right-click on Time_of_Day and select New Mapping... from the pop-up menu. The Element Mapping window will be displayed. 70. Select the down-arrow button located next to the Table Name field. A drop-down list containing the tables for the S57 HYDROGRAPHIC Data collection will be displayed. 71. Select the table MMDEMO.S57METADATA. The Table Name data entry field will be populated with the value MMDEMO.S57METADATA. 72. Click on the down-arrow button located next to the Display Value selection field and select column ISDT. The Display Value and Search Value data entry fields will be populated with the value ISDT. 73. Update the Display Value by placing the cursor in the Display Value data entry field and entering TO_CHAR(MMDEMO.S57METADATA.ISDT, HH24MISS ). If you are using Microsoft Access, enter the value Format(S57METADATA.ISDT, HHMMSS ) If you are using SQL Server, enter the value CONVERT(VARCHAR, Tutorial..S57METADATA.ISDT, 108). 74. Select the pull-down arrow next to the Text Search field and select INCLUDE. The element will be included in the Enhanced Text Search. 75. Select the Save button located in the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 76. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed. 6.8.1 What Did You Do In this lesson you performed advanced Meta Manager mapping techniques using Search Overrides. You applied the search overrides to metadata group elements. 6.8.2 What Did You Learn The Meta Manager Search Override facility is used to map an advanced searching technique that can be applied within Z39.50 Clients. The Search Override types that may be applied include: Geographic-POINT; BOUNDING BOX; Geographic-CORNER; DATE RANGE; SDE BOUNDING BOX; and, TEXT. The Meta Manager server software will use the Search Override definitions when compiling the SQL constructs that will be used for performing a search against metadata collections contained in the database. by Compusult Limited 1998-2003 - Document No. 901-003 6-45

Tutorial 6.9 Lesson 9 - Globally Changing Data Element Mappings The following procedure will illustrate the process used to change a metadata element in the master collection and have that change propagated throughout all Meta Manager collections. Procedure 1. Select Open... from the Collections drop-down menu in the main window menu bar. The Select Collection to Open dialog box will appear. 2. Select the metadata standard FGDC GEO Profile from the Metadata Standard list. 3. Select the collection MASTER from the Collection list. Meta Manager will now load the metadata tree. 4. To expand the metadata tree, select the + next to Metadata. The left side of the screen is a tree representation of the metadata standard. The right side of the screen displays the properties and mappings of the currently selected element. 5. Select the data element Online Linkage in the tree, located at the path Metadata/ Identification_Information/Citation/Citation_Information. Select Edit Mapping... from the Edit menu located at the top of the screen. The Element Mapping screen will appear. The Fixed Value text box will be displayed in the Element Mapping window. 6. Enter the value http://www.metadatamanager.com in the Fixed Value text box. 7. Select the Save button located at the bottom of the Element Mapping window. The Element Mapping window will be dismissed and a Confirmation dialog box will be displayed. 8. Select OK in the Confirmation dialog box. The Confirmation dialog box will be dismissed and the right side of the window will be updated with the values entered in the Element Mapping window. 6.9.1 What Did You Do In this lesson you defined a new fixed value for a data element in the Meta Manager master collection. This data element was then propagated to the new S57 Hydrographic Data collection. 6.9.2 What Did You Learn The Meta Manager software provides the ability to define standard fixed values for data elements in the Master collection when you are first configuring your Meta Manager database. These fixed values will be the default when new collections are created. These values may be changed in any one collection without having an effect on any other collection. If you update the standard fixed values for data elements in the master collection after creating new collections, these updated values in the master collection will be propagated to all subsequent collections in the database. by Compusult Limited 1998-2003 - Document No. 901-003 6-46

Tutorial 6.10 Lesson 10 - Executing the Meta Manager Report The following procedure will illustrate the process used to execute the Meta Manager Report. Procedure 1. Launch the Meta Manager application and connect to the Meta Manager database housing the Data Collection to be mapped. 2. Select Report... from the Collection menu located at the top of the screen. The Open Report dialog box will appear as illustrated in Figure 68. FIGURE 68 Open Report Form 3. Using the down-arrow button next to the Standard Name field, select the standard name. 4. Click on the down-arrow button next to the Collection Name field and select the collection to be loaded from the database. 5. Using the down-arrow button next to the Report field, select the type of report required. 6. Click on the Generate button located at the bottom left of the form. The Open Report dialog box will be dismissed and the Meta Manager report will be displayed for the chosen collection. 7. To print the report, select Print... from the File pull-down menu. 8. When finished viewing the report, select Exit from the File menu located at the top of the screen. by Compusult Limited 1998-2003 - Document No. 901-003 6-47

Tutorial 6.11 Lesson 11 - Configuring the Windows NT/2000 Meta Manager Server Registry The Meta Manager installation configures the Windows NT/2000 Meta Manager Server for operation with the tutorial database if the tutorial is installed. This final lesson will illustrate the steps required to configure the Windows NT/2000 Meta Manager Server for operation against the production Meta Manager database. Note: The Server Parameters function is only available if a Meta Manager Server is installed. Procedure 1. Select Server Parameters... from the Tools menu in the Meta Manager main menu. The Server List form will be displayed as shown in Figure 69. FIGURE 69 Server List Form 2. Select the name of the server under the Server Name heading on the Server List form and click the Edit button. The Edit Server Parameters form will appear with the Server Name field filled with the name of the server to edit or delete (see Figure 70). by Compusult Limited 1998-2003 - Document No. 901-003 6-48

Tutorial FIGURE 70 Edit Server Parameters Form 3. Change the User Name field value to the login specified for the Metaman database during the installation process. 4. Change the Password field value to the password specified for the Metaman database login during the installation process. 5. Change the ODBC DSN to the DSN to be searched for the Metaman database. 6. Stop and re-start the Meta Manager Server in the Services section in the Control Panel. (See Chapter 4 - Meta Manager Server) 6.11.1 What Did You Do In this lesson you changed the registry entry for the username and password for the Oracle account that the Meta Manager server uses when connecting to the database. 6.11.2 What Did You Learn In this lesson you discovered how to configure the Meta Manager server to work against different database user accounts. by Compusult Limited 1998-2003 - Document No. 901-003 6-49