geoss adc architecture workshop break-out summary : clearinghouse, catalogs, and registries
DESCRIPTION
GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries. Doug Nebert U.S. Geological Survey [email protected] February 5, 2008. Integration Issues. Catalogues registered with GEOSS have a wide variety of standardization. Protocols include: - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/1.jpg)
GEOSS ADC Architecture WorkshopBreak-out summary:Clearinghouse, Catalogs, and Registries
Doug Nebert
U.S. Geological Survey
February 5, 2008
![Page 2: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/2.jpg)
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?
![Page 3: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/3.jpg)
Who are the primary user types?
• Needs to be addressed/documented in CFP for:– Registries– Clearinghouse– Catalogues
![Page 4: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/4.jpg)
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
![Page 5: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/5.jpg)
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
![Page 6: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/6.jpg)
What metadata formats are found?
• ISO 19139 and Profiles (INSPIRE, ANZLIC, NAP)• FGDC CSDGM• Dublin Core• Darwin Core
![Page 7: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/7.jpg)
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
![Page 8: GEOSS ADC Architecture Workshop Break-out summary : Clearinghouse, Catalogs, and Registries](https://reader036.vdocuments.us/reader036/viewer/2022083006/56813af4550346895da37417/html5/thumbnails/8.jpg)
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