1 / 8

GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries

GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries. Doug Nebert U.S. Geological Survey ddnebert@usgs.gov February 5, 2008. Integration Issues. Catalogues registered with GEOSS have a wide variety of standardization. Protocols include:

starr
Download Presentation

GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GEOSS ADC Architecture WorkshopBreak-out summary:Clearinghouse, Catalogs, and Registries Doug Nebert U.S. Geological Survey ddnebert@usgs.gov February 5, 2008

  2. Integration Issues • Catalogues registered with GEOSS have a wide variety of standardization. Protocols include: • ISO23950 (Z39.50) “GEO” Profile Version 2.2 • FGDC (CSDGM Metadata) • ANZLIC Metadata • ISO 19115 Metadata • OGC Catalogue Service for the Web (Version 2.0.1 and 2.0.2) • ebRIM Profile (incl ISO and EO Extension Packages) • FGDC Profile • ISO 19115 Profile • SRU/SRW OpenSearch • OAI-Protocol for Metadata Harvesting (OAI-PMH) • Dublin/Darwin Core Metadata • Web-accessible folder/ftp?

  3. Who are the primary user types? • Needs to be addressed/documented in CFP for: • Registries • Clearinghouse • Catalogues

  4. What resource types should be registered? • Consider service, data set, data collection (series), items as alternatives and the ability to transition from one to the other. • Current results are too heterogeneous

  5. What protocols can be expected? • Let responses to CFP identify existing and additional possible choices • Support test harness capability to self-test registered catalog service types • Clearinghouse instances must expose identical service interfaces for Web Portal and application clients

  6. What metadata formats are found? • ISO 19139 and Profiles (INSPIRE, ANZLIC, NAP) • FGDC CSDGM • Dublin Core • Darwin Core

  7. What metadata? How should it be presented? • Need to refine the “core” metadata results that are handled and presented by the Clearinghouse as an intersection of data elements or “Summary” type record synthesized from the remote response • Develop/share style sheets for the presentation of the records • Link through to original full record for optional presentation

  8. Specific recommendations (agreements for Clearinghouse testing and implementation) • Performance issues and scalability need to be addressed, usage expectations, type & volume of use • Typical use cases of query and presentation and load handling need to be included to gracefully handle numerous users and query loads • Focus on limited set of “well-known” combinations of protocols and content standards and their versions

More Related