RDH Catalog Organization: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
| Line 1: | Line 1: | ||
== RDH Catalog == | == 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 [[Adding the RDH to the BES | RDH Configuration Use Case]] and the [[RDH handles bes:showCatalog request | 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 == | == Integration with existing BES catalog services == | ||
Revision as of 23:57, 6 May 2009
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/
