RDH Catalog Organization
From OPeNDAP Documentation
RDH Catalog
The RDH needs to be able to provide a catalog of its data holdings. Since the RDH relies on a list of ODBC Data Sources in its configuration file (See the RDH Configuration Use Case and the RDH Catalog Use Case ) it's catalog is flat. There are no collections, aka containers, aka child catalogs. The RDH holdings can and should be represented as a simple list of DAP data sets. Each of these data sets has a DDS/DDX/DAS representation that can be accessed in the typical DAP manner.
Integration with existing BES catalog services
The RDH will need to have it's own catalog representation in the BES.
http://localhost:8080/opendap/ http://localhost:8080/opendap/catalog/
http://localhost:8080/opendap/rdh/ http://localhost:8080/opendap/cedar/ http://localhost:8080/opendap/jgofs/
