Shore Side Data System (600031 and 900823) : SSDS Strategy Meeting on January 22, 2007 This page last changed on Jan 22, 2007 by kgomes. ## Agenda Current SSDS Status MSE M1/M2 CIMT Funded another year (June 2008) AUVCTD Post processing of all of the above Documentation (WIKI migration) To dos in JIRA Projects involving SSDS, their status, and how SSDS contributes MOOS/MSE Post processing of profiler data Metadata and other user interfaces HOOVES and metadata editing Camera integration (data stream) Watch circle alarm Processes and procedures development (metadata is inconsistent) on MSE - operations Andrew's ACE stuff (Tom) User interface and business logic. OASIS M! Turn M2 Turn NDBC Cleanup (CIMT mooring) Ops procedures and people/tools/training (XML and turns) CIMT 2 turns AUVCTD ssdsLoads is broken HOOVES SENSORS Connect the instrument interface prototype up to SSDS on MARS (adapter or alternate ingest mechanism) Others? ROVCTD LOBO BOG do we put more in SSDS? CO2 Initiative? CN Initiative? Data Aggregation Meetings UW to Microsoft Proposal (RCO) "We (TBD) will bring SSDS up to UW and operate". SSDS collects and then Triton (WorldWind++) visualizes it. It will tie into the .NET 3.0 Workflow Framework. UCSD Response to CI IO FIREWALLED MBARI Response to CI IO FIREWALLED CSO IO Possibly a temporary system to serve as a CI proxy. LOOKING (20 days) Jim wants to merge AOSN Data System and SSDS and then connect COOP and MoQUA to that. Federated observatory prototype include components of SSDS as repository (catalog, processing and preserving data) AOSN If Jim uses looking for merge, AOSN will use that. Dependent on LOOKING. SNMP is an activity ESB at NCSA ESB at MBARI Sending packets back and forth. To get diagram SENSORS build instrument interface and connect to ESB. SSDS is on ESB to collect and catalog data. NCSA Proposal to NSF to extend SNMP work (keeps it going) Product are offered to community (OpenSource) Nekton Research/NOAA MBARI share SSDS code Nekton will package SSDS with 2 AUVs delivered. Get Nekton engineers to be self reliant with SSDS. Would they be interested in AUV science data processing? Would need something like AUVCTD portal code to convert Nekton AUV data to XML/SSDS Data model. Conference call with them. NOAA Proposal (Francisco) CenCOOS Related to NOAA Proposal and Data Aggregation? Dalhousie Waiting on us to deliver exportable code (they can compile and run). Preconfigured properties for building for them Tracking metadata and data for their moorings. They might provide some user interfaces for SSDS. Haven't talked to them in a while. What are our goals for SSDS? Internally Externally Short Term Long Term How do we transition to support and what still needs to be done? Metadata editing/management (and other UIs) Plan for the transition (written) and resources needed Move core to support or vice versa. Documentation Move to Subversion (get rid of branches) Plan and agreement for future work/development Operational interfaces (component health/statistics/log crawlers) Improve data stream monitoring system (NAGIOS a possibility) Controlled vocabularies (instrument types) overlap with MMI? Load all OASIS data. Workflow for instrument data streams. How do we best open source SSDS? Current licensing website Did not formalize license yet Not utilized What is still to be done to open source? Pick a license Decide on distribution mechanism (talk to Brian and Luis) Clean up code/copyright.

Document generated by Confluence on Feb 04, 2026 08:56