Clearinghouse WG Telecon Agenda and Presentations September 25, 2002

Agenda Introductions (5 min) Clearinghouse Node Status (5 min) Gateway Status and Support Activities (15 min) Isite Software Status (15 min) Intergraph SMMS/GeoConnect Status (15 min) ESRI Metadata Server Status (15 min) Enraemed Software for ISO Metadata (5 min) SDI Technical Workshop Review (10 min) Wrap-up (5 min)

Clearinghouse Nodes Status

Clearinghouse Node Status 366 Clearinghouse Servers Identified 274 – Active Status in FGDC/GSDI registry 92 – with GeoConnections Canada 34 – Not Active Status 11 – Pending Status Need to work with Canada to get more content registered with FGDC

Domestic Nodes by State

Clearinghouse Nodes Around the World Argentina: 1 Australia: 19 Barbados:2 Bolivia:1 Brazil: 3 Canada: 109* Chile 1 China: 1 Colombia: 2 Costa Rica: 3 Dominica: 1 Dominican Republic: 1 El Salvador: 2 Ethiopia1 Guatemala: 2 Honduras: 2 Updated: Sept 2002 Italy: 2 India1 Japan: 2 Jamaica: 1 Kenya:3 Mexico: 2 Nicaragua: 2 Norway:1 Peru:1 South Africa: 2 Switzerland:1 Trinidad & Tobago: 1 United Kingdom: 9 United States: 183 Uruguay: 2 Venezuela: 2 * Canada has 92 un-registered nodes

Clearinghouse Support Activities Registry Wizard Completed Gateways Upgraded Registry-UDDI Integration Multiviewer Development UNGIWG Demonstration Support WSSD / GISD Support

Multiviewer/Gateway Support for javascript in all browsers must be verified Proper processing of OGC Map requests needs to be assured Disseminate guidance to Clearinghouse participants on how to set up their map services and proper metadata link contents

26 September 2002 Archibald Warnock FGDC Support Activities Archie Warnock, A/WWW Isite Updates CIP/GEO Interoperability Testing ISO CD2 Metadata Support Activities

Isite Updates ftp://ftp.awcubed.com/pub/Software/Isite2 GEO Compatibility Fixed date range syntax (CCYYMMDD/CCYYMMDD) Uses structure attribute 210 for specifying date ranges Added ISO19115CD2 doctype Z39.50 Improvements Isite Z39.50 clients handle ReferenceID parameters and have configurable timeouts Improved handling of user authentication information in Isite Z39.50 clients

Isite General Enhancements Isite/Isearch2 ported to Solaris and Cygwin zserver writes its process ID to a file, ala Apache Can search multiple fields in single query term (title+abstract/water) Can search multiple fields from one use attribute Improved Isearch-cgi, with support for numeric, spatial and temporal searches, and configuration file Virtual naming for indexes Improved documentation using SGMLdoc Updated class documentation

INFEO Client to Isite Server INFEO is a European Space Agency operated imagery catalog service using the CIP Profile of Z39.50 Testing in collaboration with Maurice Klein Gebbinck at ESA Spatial searching works but… Isite supports only BoundingCoordinates use attributes (2060 and 3111) GEO term ordering is different than that used by INFEO Semantics of spatial relations are not consistent

CIP Client to Isite/GEO Server Isite supports full-text queries using the Any use attribute (1016), not implemented in some CIP clients Some presentation issues in clients

Isite/GEO Clients to CIP Server User Authentication Issues Isite does not require authentication information unless it is required for access. Indeed, interoperability testing with other servers generated significant problems in such cases ReferenceID Issues This is an optional parameter in the Z39.50 standard By default, Isite clients omit it Specifying a value crashes the Blue Angel MetaStar server – reported to Blue Angel Omitting a value fails to connect to INFEO’s CIP server

FGDC and ISO FGDC is prototyping support for ISO metadata The intention is to use the abstraction layer provided by Z39.50 to make ISO metadata queryable as if it were FGDC metadata In this way, ISO metadata does not have to be transformed into the standard FGDC XML format Configuration files in Isite define the mapping between the GEO 2.2 profile use attributes and one or more specific fields in the ISO metadata

Presenting ISO Results Valid XML means we can build results of various sorts using stylesheet transformation tools like Xalan or Apache Cocoon From one XML document, it is possible to create results on demand – FGDC Brief and Summary element sets in any/all of SUTRS, XML, HTML, USmarc XSLT may be difficult and tedious for XML that is as complex as ISO 19115

GeoConnect v1.0.2 – An Update for the Clearinghouse WG Bruce Westcott SMMS Metadata Consultant

GeoConnect Metadata Server What does GeoConnect do? What are the pre-requisites and components of GeoConnect? How do you obtain GeoConnect and support/updates? What are key features?

What does GeoConnect Do? Stores FGDC-standard metadata in a relational database (Access, MS-SQL or Oracle); Supports FGDC, Bio.Profile, and unlimited User- Defined fields; Provides a sophisticated GUI for content management and external metadata import; Provides an “out of the box” web page for searching “live” metadata in the database, and Administrator GUI for managing the web page ( ”live” examples at ); Provides a Z39.50 Clearinghouse server application.

What are GeoConnect Components? Database Scripts – Create structures in Oracle or MS-SQL & an ODBC connection MetaWeb – Use GeoConnect ASP code (as is or modified for your web page) to provide Intranet or Web access Z39.50 Server – Create a server process to access the database and respond to Clearinghouse queries GeoConnect Administrative Tool – (MetaWeb only) Manage your Web GUI

What are GeoConnect Pre- requisites? Client machine (data loading and Web site management): Win98, Win2K, WinNT GeoConnect server: Win-NT Server (or equivalent) Microsoft IIS 4 with ASP (required for MetaWeb application only) Oracle 8.0+ or MS-SQL Server v7 or v2000 GeoMedia products are not required

How do you obtain GeoConnect and support? Applications and Documentation (PDF) distributed on SMMS CD -- order online at Updates, knowledge base, and technical documents available at Intergraph Premium Maintenance: Web-based and phone-based support Automatic software “hot-fixes” and upgrades

What are Enhancements in this Version? Fully compatible with Geo2.2 Profile for Z39.50 Certified on newer versions of Win-OS and RDBMS products Increased server process stability More user-customization features

The GeoConnect Architecture Z39.50 Queries

Goals for the ArcIMS Metadata Server Provide the capability to manage and search a central metadata repository over the Internet. Allow data producers to easily publish their metadata to the repository. Allow data consumers to easily search the metadata in the repository.

Adding support for metadata to ArcIMS Provides a single set of enhanced metadata functionality for use by: The Geography Network ArcInfo 8.x ArcSearch ArcExplorer 3.x Other custom client applications

New in ArcIMS Z39.50 Support Metadata Harvesting Increased performance for Metadata Server Improved ISO support

Internet ArcSDE Z39.50 Z39.50 Connector ArcCatalog Metadata Explorer Clearinghouse ArcXML ArcIMS Z39.50 ArcXML

Why the Metadata Server? Provides a central metadata repository that keeps track of all your data, wherever it may be, and whatever format it is. Allows users on any platform to quickly search for data by extent, keyword, or other criteria using a lightweight web app. Integrated with ArcGIS clients, allowing you to publish, manage, and search metadata using familiar tools and interfaces. Distributed and scalable, allowing networks of servers to be searched with a single request. Essential backend product that allows organizations to build their own geography network.

Enraemed Metadata Software

Develop by Dutch Donor Agency for the Ethiopian Government Being used within Ethiopia by all governmental institutions Willingness to hand over software to UNEP and GSDI/FGDC for maintenance

Enraemed Metadata Software Features ISO, FGDC, GILS, and DC compliant Stand Alone or Client–Server Backend Database MSDE, MS SQL Server, Access2000 Globally unique IDs Element Navigator Elements of selected standard Mandatory-optional-mandatory Jump function

Enraemed Navigator

Enraemed plans Continue evaluation of software as replacement for MetaLite reference implementation software Attend in-depth training in November on- site to learn programming details Develop/modify basic package for use in US and elsewhere as metadata collector

Metadata Status Contract to Intergraph to build XSLT transformation rules to translate FGDC V2 as XML into ISO as XML – awaiting newer version and confirmation of transform assumptions ISO Metadata Standard will have a companion Technical Specification on how it will be encoded in XML Both to be approved, hopefully, by mid 2003

Denver Workshop Summary zAbout 150 people attended a three day SDI workshop hosted by US and Canada zParade of relevant standards and specifications and policies and technical solutions providers zRaised some issues and concerns about how NSDI could be improved

Clearinghouse Suggestions Show benefits of migration to ISO metadata, minimize pain of transition/ participation Provide an alternative solution to the Z39.50 approach to Clearinghouse search using search engine approach Make Clearinghouse searches easier and more reliable Adopt the Canadian approach of web components to allow anyone to build a Gateway