Bjørge Solli wrote:
It really depends on what THREDDS client you are using. It sounds like you are viewing the catalogs in a browser in which case the TDS XML to HTML code can be thought of as the THREDDS client. In the TDS HTML catalogs, the documentation is only seen on datasets that have IDs (and are not catalogRefs, as those are links to the next level of catalog.I'm using thredds 3.4 on tomcat 5.0.30.
My content/thredds/catalog.xml contains: <catalogRef xlink:title="North Atlantic Class 1 - Best estimate and bulletins" xlink:href="dodsC/mersea-ip-class1-nat.xml"> <documentation type="summary"> DODS Data Prepared for the MERSEA IP EU Project. </documentation> <documentation type="simple" xlink:href="http://www.mersea.eu.org" xlink:title="MERSEA Project Web page"> </documentation> </catalogRef>
Where is the documentation shown?
Wouldn't it be better to have a <metadata inherited="true">...</metadata> inside <catalogRef> and let all the datasets in dodsC/mersea-ip-class1-nat.xml inherit them? Another way that would work for me was to have it like this:Unless the catalogRef and the referenced catalog are generated from datasetScan elements, the metadata in your top catalog will not be visible across the catalogRef link in the referenced catalog even if the metadata is declared inherited. Since each catalog can be referenced seperately, a catalog needs to stand alone. It can reference other catalogs and URLs but it can not depend on an upstream link that the user/client may not have followed. Here's how the spec puts it, "[t]he referenced catalog is not textually substituted into the containing catalog, but remains a self-contained object".
<dataset "container"> <!-- no ID on this -->
<catalogRef ... />
And then all the datasets in the catalogRef also inherit the metadata.
I use catalogRef to avoid having to process all my large datasets unless specifically asked for, but they mainly have pretty much the same <authority>, <dataType>, <dataFormat>, <documentation>, <creator> and <publisher>.Are you using datasetScan elements for automatic catalog generation in your content/thredds/catalog.xml? Or only at lower levels of you catalog tree. Using datasetScan elements would do a lot of this for you and the catalogs don't get generated until requested.
Hope this helps. Let me know if you have further questions.
-- Ethan R. Davis Telephone: (303) 497-8155 Software Engineer Fax: (303) 497-8690 UCAR Unidata Program Center E-mail: address@hidden P.O. Box 3000 Boulder, CO 80307-3000 http://www.unidata.ucar.edu/ ---------------------------------------------------------------------------
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.