On Tue, Dec 18, 2012 at 7:47 AM, boehnert
<address@hidden> wrote:
Hi Lansing,
I do not know if I completely understand your email, but if I want my page to look like this one http://motherlode.ucar.edu/thredds/catalog/fmrc/NCEP/GFS/CONUS_80km/runs/catalog.html?dataset=fmrc/NCEP/GFS/CONUS_80km/runs/NCEP-GFS-CONUS_80km_RUN_2012-12-17T18:00:00Z is there anything I can do?
Thank you Jennifer
On 2012-12-17 15:41, Unidata THREDDS Support wrote:
Here are those files you requested.
Thank you Jennifer
On 12/17/2012 1:46 PM, Unidata THREDDS Support wrote:
>> Hello,
>> We have a TDS running which is holding our AR4 CCSM data. We have lots
>> of metadata in the nc files but you cannot see the metadata in the
>> dataset catalog page through the TDS catalog. ( see
>> http://tds.gisclimatechange.ucar.edu/thredds/catalog/products/catalog.html?dataset=anomalies/tas_SRESB1_near_seasonal_down_anomaly.nc)
>>
>> I want to see what variables are available, the time ranges, all that
>> info. I am looking in the TDS documentation and I see a havest
>> attribute for the dataset element.
>>
>> <xsd:attribute name="harvest" type="xsd:boolean"/>
>>
>> Do we just need to add this attribute and set it to true in order to
>> harvest the metadata into the catalog.
>>
>> Thanks in advance
>> Jennifer
>>
>>
>>
> Jennifer,
>
> Can you send me your catalog.xml and threddsConfig.xml files?
>
> -Lansing
>
> Ticket Details
> ===================
> Ticket ID: QWW-389996
> Department: Support THREDDS
> Priority: Normal
> Status: Open
Jennifer,
The metadata information you're describing won't show up on the
catalag page for a given dataset, but it is given through the
interfaces for opendap and ncss. The harvest attribute has to do with
how discoverable your data inventory is by other services.
-Lansing
Ticket Details
===================
Ticket ID: QWW-389996
Department: Support THREDDS
Priority: Normal
Status: Open