U.S. Department of Commerce National Oceanic & Atmospheric Administration National Geophysical Data Center (NGDC) Marine Geology and Geophysics Division & Co-located World Data Center for GMG

NTHMP Repository Status Scott Thurston Systems Engineer Earth Resources Technology

Loren Pahlke, Technical Writer o Technical writer in several high-technology companies Scott Thurston, Systems Engineer o USAF Information Systems Programmer o Extensive background in high-technology companies Introductions

NTHMP Strategic Plan calls for web-based repository of tsunami-related materials NTHMP funds became available to start the project NOAA/NWS contracted with ERT to hire a systems engineer and a technical writer for the project Background

1.Inventory available materials o Focus on US west coast, AK, HI and PR 2.Develop functional requirements 3.Draft a functional specification 4.Present recommendations to NTHMP Coordinating Committee 5.Draft a design document Project Phases

Site visits o Team visited 14 sites over the summer o Met with approximately 25 individuals in various areas of modeling, warning and emergency management o Reviewed the checklist to probe for potential contributions o Gathered significant information about requirements, functionality, policies, et cetera. Inventory will be posted to NTHMP Website Inventory

Checklist was exhaustive and captured most of the kinds of materials available Most common feedback is that the repository must be easy-to-use and provide great flexibility in searching for materials Most respondents were enthusiastic about the project and saw a direct benefit to their own work Key findings

The project team has identified a large number of functional requirements for the repository o User interface o Contribution and dissemination methods o Metadata management o Administration The team also identified the need for several policies to govern the use of the repository Requirements and Policies

Flexible searches* Ingest data on physical media Localize the user interface Means for users to comment and discuss* Multiple user roles Manage bundled objects* Archive all objects Migrate data in obsolete formats Option to disseminate on physical media Key Requirements

1.Is georeferencing necessary? 2.Are complex objects (bundles) required? 3.Is a means to comment required? 4.Should the repository accept extremely large data objects (i.e. multi-terabyte modeling products)? Key Questions

Mandatory vs. optional contributions Avoiding copyright violations Approval of content and metadata* Eligibility to contribute Metadata-only contributions* Acceptable contributions Restricted access materials* Key Policies

Next Steps Complete 1 st draft of functional specification o Includes sample policies Complete estimations of costs and implementation times for different approaches Deliver specification and recommendations to CC Draft high-level design document

Thank you! Contact information: Questions?