Yep - thanks John - in addition to what I mentioned below the harvester does
check this attribute on datasets but at the moment the catalogs I've looked at
(even those that have datasets with metadata elements) don't use it for some
reason.
Cheers,
Simon
________________________________________
From: John Caron [caron@xxxxxxxxxxxxxxxx]
Sent: Thursday, 16 April 2009 2:21 AM
To: Pigot, Simon (CMAR, Hobart)
Cc: Ted.Habermann@xxxxxxxx; Pauline.Mak@xxxxxxxxxxx; ngdc.geospatial@xxxxxxxx;
thredds@xxxxxxxxxxxxxxxx; Peter.Blain@xxxxxxxxxxx; rsignell@xxxxxxxxx
Subject: Re: [thredds] Collection Metadata from Granules
Simon.Pigot@xxxxxxxx wrote:
> Re: granularity
>
> I don't have an answer on what level of granularity is appropriate - only to
> mention that the harvester will have simple check boxes that allow you to
> harvest services, collections and atomic dataset metadata - its a device to
> which other options could be added. The whole concept of
> searching/identifying and displaying hierarchical relations between dataset
> metadata records as well as relationships between services records and the
> datasets they deliver is still at a very early stage of development (at least
> in GeoNetwork :-)).
We use the harvest="true" attribute to identify those THREDDS dataset
elements for which we want to create these kind of metadata records.
This is a mechanism to make sure you dont have to open 1000's of
identical files.
