RDH Catalog Organization: Difference between revisions
| 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. | 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. | ||
In BES speak that means that RDH catalog response will contain only items that | |||
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. When responding to a bes:showCatalog request the RDH should return a catalog composed of a top level dataset that contains a list of dataset elements each of which has a ''node'' attribute whose value is false and (at minimum) a child bes:serviceRef element with a value of "dap" : | |||
<dataset catalog="catalog" lastModified="-1" name="dataSourceOne" node="false" size="-1"> | |||
<serviceRef>dap</serviceRef> | |||
</dataset> | |||
Since the bes:dataset ''size'' and ''lastModified'' attributes may not have much meaning in this context they should be set to the appropriate value for missing value or mottied if that's the right thing to do... | |||
== Integration with existing BES catalog services == | == Integration with existing BES catalog services == | ||
Revision as of 00:06, 7 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.
In BES speak that means that RDH catalog response will contain only items that 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. When responding to a bes:showCatalog request the RDH should return a catalog composed of a top level dataset that contains a list of dataset elements each of which has a node attribute whose value is false and (at minimum) a child bes:serviceRef element with a value of "dap" :
<dataset catalog="catalog" lastModified="-1" name="dataSourceOne" node="false" size="-1">
<serviceRef>dap</serviceRef>
</dataset>
Since the bes:dataset size and lastModified attributes may not have much meaning in this context they should be set to the appropriate value for missing value or mottied if that's the right thing to do...
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/
