NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Nathan, Yup, I agree with John. If you want catalog level metadata, the catalog needs to contain a single top-level dataset with the metadata. If a catalog contains multiple top-level datasets, you don't have catalog level metadata. I never write catalogs without a single top-level dataset for just this reason. If we were designing catalogs again, I'd push hard to only allow catalogs to contain a single dataset (and get rid of the catalog name as well). Ethan On 3/7/2012 11:03 AM, John Caron wrote: > On 3/7/2012 9:43 AM, Nathan Potter wrote: >> >> Greetings, >> >> I have a user that wants to add<documentation> tags to the top level >> of a THREDDS catalog. Based on my reading of the THREDDS specification: >> >> >> http://www.unidata.ucar.edu/projects/THREDDS/tech/catalog/v1.0.2/InvCatalogSpec.html >> >> I believe that the catalog may not contain a documentation element at >> the top level. The dataset element may contain a documentation >> element, but there can be multiple datasets at the top level of a >> catalog so there is no obvious (at least to me) way to universally >> identify which dataset metadata would be used to describe the catalog >> collection. >> >> Is that correct? >> >> Any thoughts? >> >> Nathan > > hi nathan: > > I think thats right. You need to add a top level dataset container > element if you want to have top level documentation element. > > john
thredds archives: