1 / 17

The NOAA National Geophysical Data Center

The NOAA National Geophysical Data Center. And Collocated World Data Service for Geophysics. Failure to Connect?. Dan Kowal Data Administrator, Information Services Division NOAA / NESDIS / NGDC dan.kowal@noaa.gov GeoData Workshop 2014 .

merlin
Download Presentation

The NOAA National Geophysical Data Center

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. The NOAA National Geophysical Data Center And Collocated World Data Service for Geophysics Failure to Connect? Dan Kowal Data Administrator, Information Services Division NOAA / NESDIS / NGDC dan.kowal@noaa.gov GeoData Workshop 2014

  2. Technical issues of connecting geodatain and between governmental agencies.

  3. Challenges and Accomplishments • Metadata Publication • Software Development • Data Citation

  4. Metadata Tools http://www.ngdc.noaa.gov/docucomp/

  5. Measurement of Completeness

  6. Count of Broken URLS

  7. Metadata Publication - Local • NGDC Metadata Homepage • Immediately available • NGDC Geoportal • synchronized weekly or upon request

  8. Software Challenges • Wide variety of data types • Diversity of data providers • Decreasing staff and funds • Increasing number of data sets ~ 600 to date • Legacy code bases • Lack of communication

  9. Engineering Objectives • Common framework • standardize on common technologies, shared knowledge, centralization supporting tracking / reporting • Isolate dataset specific components • share things like file handling, messaging across disparate datasets • Modular and extensible • ease maintenance and facilitate testing, phasing in new capabilities (incremental improvements), reduce likelihood of system-wide impacts to errors or malfunctions

  10. Engineering Objectives - cont’d • Industry-standard and best practices and patterns • develop in teams, automated builds, test coverage, leverage industry tools • Resilient • eliminate single points of failure, be able to restart processes following errors without data loss, secure • Minimize custom code • reduce software maintenance

  11. New Access Interfaces at NGDC

  12. DOI Landing Page

  13. DOI Landing Page

  14. DOI Readiness Assessment

  15. Data Citation Summary • Data Linkage to Publications: • Data Citation Indexin Thomson-Reuters’ Web of Knowledge • Elsevier ScienceDirect – Ongoing discussions. • Procedural Directive for Data Citation in the works. • Leverage ESIP Guidance • NCAR’s Data Citation White Paper • DataCite • ~ 50 Datasets minted through EZID.

  16. In Summary… • Need to fix the catalog publishing disconnect. • Enterprise approach to development paying dividends. • Creating opportunities for reuse. • Generic functionality shared across data sets. • Going to take more resources to transition legacy data sets. • Collaboration in Data Citation practices across Data Centers bodes well for future consolidation. • Begin “Interoperability” discussion early when initiating a new Archive Project.

More Related