1. WHOI and SIO (II): Next Steps Towards Multi-Institution Archiving of Shipboard and Deep Submergence Vehicle Data (IN51A-0306) The Woods Hole Oceanographic Institution (WHOI), Scripps Institution of Oceanography (SIO), and the San Diego Supercomputer Center (SDSC) are working together on a digital data archiving and preservation project that will establish interoperability between existing data repositories and provide community access to shipboard and deep submergence vehicle data. The prototype system establishes a two-node, federated data network initially populated with WHOI and SIO data from the Galapagos Island area. SIO and SDSC are contributing software and experience developed for their SIOExplorer application including data and metadata harvesting, federated digital libraries, and related web-based and Java-based clients. WHOI is contributing software developed for a number of its GeoBrowser technologies and GIS Server based applications. 1.Source data files are copied from various sources to a local server either at WHOI or SDSC. 2.A single program, metadata_Creator.pl, harvests source- specific metadata from raw data files derived from sensors and samples. 3.These source-specific metadata are then operated on by another program ADOcreator.bash (&.pl) to generate the {ADO, mif} pairs that are then loaded into the digital library. 4.The data files are ingested as arbitrary data objects (ADOs) into the Storage Resource Broker (SRB) and the metadata (*.mif) into the metadata catalogue implemented using a Postgres relational database. 5.Web-browser and Java clients (shown in blue) are used to access the archive. Maffei, Helly, Clark, Detrick, Gaylord, Goldsmith, Lemmond, Lerner, Miller, Norton, Tivey, Walden Woods Hole Oceanographic Institution, Scripps Institution of Oceanography, San Diego Supercomputer Center We thank the DIGARCH Program of the National Science Foundation and the Library of Congress for their support (NSF IIS 0455998). This figure shows how cruise, Alvin, Jason2 and data are fed into WHOI’s GeoBrowser and GIS Server applications. This figure shows how metadata is harvested from SIO cruise data files, ingested into the digital library and then made accessible via the SIOExplorer Graphical User Interfaces (GUIs). OverviewCurrent SIOExplorer Cruise Data Workflow Current WHOI GeoBrowser & GIS Data Workflow Acknowledgements Examples of Current Web Clients Combined SIOExplorer, WHOI GeoBrowser, and WHOI GIS Data Workflow 1.WHOI cruise/vehicle data files collected from shipboard dataloggers and other locations. 2.Geobrowser applications sample some of the cruise/vehicle data (video, shipboard data, etc.) in order to create metadata in form of Electronic Index Cards (EICs). 3.Historical data transcribed from archives. 4.GeoBrower application provides access to Electronic Index Card (EIC) snapshots and summaries of data collected. 5. WHOI Cruises application provides access to cruise/vehicle metadata via web-based GIS map interface. 1.WHOI and SIO Galapagos-related cruise/vehicle data is collected from various sources. 2.WHOI and SIO Galapagos cruise/vehicle data is re- cast into a Common Cruise Canonical Directory Structure (CCCDS) 3.Metadata plugin routines generate intermediate metadata files for collection, cruise, file, sensor (video, ctd, multi-beam, underway-data, etc.), and other data. We call these intermediate entities Oceanographic Metadata Files (OMFs). 4.WHOI GeoBrowser routines employ CCCDS and OMFs to create Electronic Index Card (EIC) collections. 5.WHOI GIS Server routines employ CCCDS and OMFs to create entries in the GIS server. Sample Search for Galapagos Data WHOI’s Jason2 Virtual Control Van WHOI’s Cruises GIS Server WHOI’s Alvin FrameGrabber WHOI’s Shipboard DataGrabber SIO’s Digital Library WebForm SIO’s Digital Library JAVA Front end 6.SIOExplorer routines use the CCCDS and OMFs to create ADOs and MIFs and ingest them into the federated digital archive. 7.During the prototype phase of the project, the web client front-ends will be updated so that they can access the three server types via their existing Application Programming Interfaces (APIs). During the next phase of this work, a common Web services API will be defined and implemented on each of the servers. Dive 4119 Step 1 (above) - use SIOExplorer to find all SIO/WHOI ship tracks in area; locate AT11-27 Step 4 (below) - use PetDB to find chemical composition of sample Step 2 (above) - use WHOICruise GUI to locate Alvin dive 4119 on AT11-27 Step 3 (left) - use Alvin FrameGrabber to locate detailed dive track and video of basalt sample being taken