[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #MIN-918666]: Inherited metadata within <aggregation>

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #MIN-918666]: Inherited metadata within <aggregation>
  • Date: Fri, 14 Apr 2006 15:22:50 -0600
Hi Jerome,

I'm not sure what you are trying to accomplish by including metadata in your 
aggregation elements. Do you want the metadata to be part of the resulting 
aggregated dataset in the catalog the server makes available? Or are you trying 
to modify each dataset that is being included in the aggregation before it gets 
aggregated?

If the former, probably your best bet is to add the metadata at the dataset 
level. If the latter, you could use NCML to wrap each dataset that is being 
aggregated and point to that wrapped dataset in the aggregation. 

The NCML XML Schema does not define the aggregation element in a way that 
allows metadata child elements. I'm guessing that the server ignores the 
metadata as we try to be pretty lenient when we read catalogs.

Ethan

Ticket Details
===================
Ticket ID: MIN-918666
Department: Support THREDDS
Priority: Normal
Status: Open