| Priority |
Element (Rank) |
Type |
Source |
| 1 |
Third Party (Tertiary) Metadata
|
Core |
All workshops: The need for uniform standardized use and search metadata. Enables qualification and certification of datasets. |
| 2 |
GIS:
Client
|
Clients |
All workshops. NOPP Mandate. Gateway from Scientific Data to non-science communities via ESRI existing off-the-shelf analysis and display tools. |
| 3 |
.html Page
(Add a top-level directory page to the server.) |
Servers |
NOPP BAA: " ... to easily access certain data types ... regardless of data source, ..." |
| 4 |
File-out tools.
DataDDS --> {NetCDF,HDF,MAT,SAV}
|
Clients |
NOPP BAA: " ... to easily access certain data types
... regardless of data source, ... such that the data would easily transfer into the user applications ..." |
| 5 |
Generic Display
(Immediate display for any DODS-served Dataset)
|
Clients |
National and Regional Workshops. "All VODHub datasets should be immediately previewable on line ...". Enables immediate testing at installation and immediate preview by a user. |
| 6 |
Adopt A Controlled Vocabulary
(For variable names.)
|
Metadata Tools |
National and Regional Workshops. Enables compliance with federal standards, while enabling machine level interoperability. Enables cross-discipline interoperability on machine and human levels. |
| 7 |
Client Toolbox
(including GUIettes)
Matlab
IDL. |
Clients |
Regional Workshops: Looking for user configurable applications for their specific needs. Toolboxes will make life easier for someone building specific search or analysis software. They will have modules for building DODS URLS on the fly, and applying calibrations based on the available metadata. |
| 8 |
Build Metrics gathering into our servers. |
Core |
Previous ExperienceLittle mention was made of how to track progress, with the exception of knowing which datasets are available (data discovery). Collecting specific demographics on dataset, server, and client usage is critical to enhancing and advertising the capabilities in directions that will further the aims of the NVODS. |
| 9 |
Data Registration Tool;
(URL + Metadata, use and search)
|
Core |
National and Regional Workshops: The ability to discover a useful dataset was a major concern. By giving a data provider a simple form to supply registration (discovery) metadata, information about the contents and location of their data will be easily and automatically put into regional and or national search locations (GCMD, e.g.) with standard (FGDC) content suggested (or specified as "required" for NVODS certification). |
| 10 |
A GUI geospatial/temporal selection capability.
|
Clients |
National and Regional Workshops (implicit), Core (explicit):Converting from standard geospatial units (latitude, longitude, e.g.) to internal dataset values (array indices, e.g.) when making a data request should be performed by a graphical user interface so that the user does not have to make that translation consciously. Having a web-based interface or interfaces to do those conversions for an arbitrary NVODS geospatial dataset is manditory for active and widespread use of NVODS. |
| 11 |
Web Crawler
|
Metadata Tools |
National Workshop and Regional by implication:
Several regions articulated a need for a central regional "data catalog" of available datasets of interest to the region. A web crawler could be used to keep such catalog current. The National Data Discovery Breakout Group viewed web crawlers as one mechanism to locate datasets of particular interest. Web crawlers could be used to acquire metadata from datasets themselves without the provider giving the metadata directly. Updating metadata for continuously increasing datasets is a prime example. |
| 12 |
Secure Software for DODS Datasets
(Done. needs Documentation)
|
Core |
National and Regional mandates:Installation of DODS software must not compromise the computer systems on which it is intalled. A high level of security that minimizes or eliminates any "holes" into the computer systems must be maintained. System security was a concern of all the workshops, and continues to be a primary consideration in the softweare development. |
| 13 |
XML version of the DAP |
Core |
National,Regional, Technical workshops, Core:XML with its self-defining content descriptions provides an ideal means of coding and transporting arbittrary data types, including metadata. The ESRI TIM noted "XML is a fundamental part of data communication for ESRI web applications ..." "The coming use of XML" was noted during the National Workshop. Neville Smith noted: "The XML standard (or an equivalent) ensures all data are properly described / characterized." Putting the DAP into XML has been a target for some time. |
| 14 |
Enable serving CODAR Data.
(End to end Demo. Project)
|
Core |
National and Regional Workshop: CODAR surface current data are available from several of the regions, and will fill in real-time and near-real-time information along most of the U.S. coastline. The National and Regional workshops identified the need for several pilot projects. Serving CODAR data to allow the collection, analysis, display, and
provision to end users of digital and graphical information which they could
view on a local or regional or national scale at will, would provide a powerful demonstration of the NVODS system, and was identified as a prime "cross-cutting pilot project" for further consideration. |
| 15 |
Geospatial-Temporal Display of NVODS Datasets
a) Overplotting
b) Fusion
|
Clients |
National and Regional Workshops:From the National Browser Breakout Group: "...all VODHub datasets should be previewable on-line in a geophysically consistent form: i.e., with the ability to label the axes of the plots." From the regional summary: "Functionality should include location/sub-setting, manipulation, display, and data download." LAS is being evaluated to determine if it can be modified to include these functionalities for all NVODS datasets. |
| 16 |
FGDC-reader->.das |
Metadata Tools |
National and Regional Workshops:The need for standards of search and use metadata is paramount to the success of the NVODS effort. FGDC was cited many times throughout the discussions as providing a Federally mandataed standard. One mechanism for attaching semantic metadata to a dataset is through the Data Attribute Structure. If the metadata required to make a dataset compliant with NVODS standards is put into an FGDC Clearinghouse, then having a software package that could querry the clearinghouse and populate a DAS would be one direct way of automatically attaching required metadata to a dataset. |
| 17 |
PI Servers
(Robust Server for ASCII/binary data) |
Servers |
Regional Workshops (specifically), National workshop (general):Providing for the serving of older datasets, and datasets held by individual PIs, which often exist as ASCII or binary files, must be servable with general and easily installed servers. The two servers which accomodate ASCII data are the JGOFS and FreeForm servers. Each has limitations and problems which should be overcome with a more general and easier to use server, specifically designed for the purpose. Several of the regional participants have such datasets. |
| 18 |
GIS:
Toolbox
|
Clients |
| 19 |
DODS-dir
|
Server-side Services |
| 20 |
Multi-URL Protocol Issue
(was DAP consolidation) |
Core |
| 21DONE |
Provide DODS-dir URL with Dataset List
|
Metadata Tools |
| 22DONE |
Grid() server side function. |
Server-side Services |
| 23DONE |
Control Access to DODS-served Datasets.
|
Core |
| 24 |
Design NVODS to handle:
maps
graphs
images
animations
(via Related URLs, e.g.)
(This is an NVODS issue possibly to be handled by
judicous use of placement of metadata images/maps/graphs/animations.
|
NVODS |
| 25 |
Concatination of Modulo requests.
(was "Auto-subsampling of very large datasets")
|
Core |
| 26 |
GIS:
Server (GIS data to DODS)
|
Clients |
| 27 |
Provide Unique Dataset Tags
|
Server-side Services |
| 28 |
Provide for User Feedback on Dataset Quality
|
User Support |
| 29 |
Allow for more projection types on the Earth's Surface
|
Core |
| 30DONE |
Fileserver Interface |
Server-side Services |
| 31 |
Point Aggregation Server for non-gridded data.
|
Servers |
| 32 |
Interface for standardized representations
of independent variables
|
Core |
| 33 |
Support a swath datatype (NGrid?). |
Core |
| 34 |
Display a Disclaimer on access to certain datasets.
|
Core |
| 35 |
Enable Push serving data into NVODS.
|
Core |
| 36 |
BUFR external |
Servers |
| 37 |
Develop an ESML-based server.
|
Servers |
| 38 |
Develop an NVODS Variable-Name Controlled Vocabulary.
|
Servers |
| 39 |
Mirror Servers
|
Servers |
| 40 |
IDL GUI. |
Clients |
| 41 |
Matlab GUI. |
Clients |
| 42 |
HDF API -- Client Library
|
Clients |
| 43 |
Develop Depth interfaces Similar to Time |
Server-side Services |
| 44 |
Macintosh OS-10 |
Platforms |
| 45 |
CORBA Gateway
|
Core |
| 46 |
Data Quality Specification |
Metadata Tools |
