Two-day training course:
How should we present the information
Outline for the course
How should we organize and present the information? Here are some ideas:
- As a collection of PowerPoint presentations
- As a web course (maybe built using a/this twiki)
- A binder/notebook
Here's an outline. Originally from Dan, I hacked it up some...
Server-Side:
- Determining the (pre-existing) server to use.
- testing the server against the data.
- Installing the server into an existing web server
- explain the cgi dispatch
- explain the servlet
- discuss the security issues regarding our implementations.
- Explain the suite of server services and how they work
- usage, usage_jg
- asciival
- www_int
- explain the installation issues with asciival/www_int
- Letting others know about your server
- GCMD
- Our data set list
- Sending people URLs and seeting up your own pages
- Advanced Topic: Discuss DAP response / data model issues for various data representations (in-situ, gridded, etc.)
- Explain the issues of mapping DAP responses into various client applications and why that's important.
- This topic could be a lead into custom server development, steps required, et cetera.
Client-side:
- Data Discovery
- Using the GCMD
- Using our data set list
- URLs from your buddies
- Why sometimes the URL has
.dodsand sometimes it doesn't.
- Why sometimes the URL has
- Classes of clients available
- Relinking netCDF-based applications with our libraries.
- Using URLs in those applications.
- List existing SCOTS packages (matlab, IDL) and what's required to access data in those packages (loaddods, idl_dods.so)
- Using URLs in those applications.
- Scripting
- using Matlab, IDL scripts
- using script applications like Python
- OPeNDAP Data Connector
- demonstrate data location
- demonstrate visualization
- demonstrate interaction with external apps (Excel, Matlab, IDL, etc.)
- Relinking netCDF-based applications with our libraries.