Shore Side Data System (600031 and 900823) : ProjectRequirements
This page last changed on Oct 28, 2009 by kgomes.
Requirements documents for SSDS development:
Consolidated Requirements
| Number | Requirement | Description |
|---|---|---|
| 1.0 | User can merge data from different sources | This should be able to be done by the user selecting variables from various sources and a time frame and then SSDS will return a merged data set in various formats. See John's pseudo-code and Perl script for merging script. |
| 2.0 | Data conversions can be done by SSDS | SSDS should support user defined data transformations. CTD values to salinity is the golden example of this |
| 3.0 | SSDS should connect up/work with AOSN | ? |
| 4.0 | I want to be able to edit the metadata in the SSDS system. | |
| 5.0 | I want a snapshot view of all the currently deployed instruments and what their data stream are doing (this should have links to the raw data, instruments configuration and device information). | |
| 6.0 | I want data/plot of variable X (i.e. salinity) from platform Y and time frame. | |
| 7.0 | I want data/plot of variable X (i.e. salinity) from geospatial location and time frame. | |
| 8.0 | I want a 'shallow' operational view of current platforms and instruments | |
| 9.0 | I want to get access to 'all' data from a device | |
| 10.0 | I want to find all data of mime type X from a device or platform | |
| 11.0 | I want to see all currently deployed devices in a geospatial location (box) |
Mooring_QC-QL_plots.doc (application/msword)
merge_pseudocode (application/octet-stream)
merge.pl (text/plain)
