Re: [thredds] threddsConfig.xml - <catalogRoot>

• To: <thredds@xxxxxxxxxxxxxxxx>
• Subject: Re: [thredds] threddsConfig.xml - <catalogRoot>
• From: "Comiskey, Glenn" <g.comiskey@xxxxxxxx>
• Date: Thu, 7 Jul 2011 16:48:19 +0100

John,

Thanks for the info.

Have no immediate use for <catalogRoot> elements in catalog.xml, though
that my change shortly, and was just checking functionality of the
element. While I appreciate that <catalogRoot> may be intended to serve
private catalogs, i.e. /thredds/catalog.xml for public use, and
<catalogRoot>.xml</catalogRoot> for private use, it just seems a bit odd
that the URL links the private catalog to the root of the public
catalog.

That is to say:
Public: http://<server>:<port>/thredds/catalog.xml ->
<catalogRef>catalog_2.xml -> <catalogRef>catlog_3.xml -> web page URL
back to http://<server>:<port>/thredds/catalog.xml

Private: http://<server>:<port>/thredds/private.xml ->
<catalogRef>private_2.xml -> <catlogRef>private_3.xml -> web page URL
back to http://<server>:<port>/thredds/catalog.xml

I am assuming the URL is hardcoded somewhere, and hence why every link
is back to the public catalog.

Can envisage this being a bit of an annoyance shortly as due to start
generating large data volumes which will sit on our production server
and I will need to generate the catalog entries privately via
<catalogRoot> first to check all OK before copying to the public
catalog. Given that I will probably be drilling down through a number of
catalogs, I usually use the URL link to the catalog root as a quick way
to get back to the start again. Won't be able to do this as it will take
me from the private catalog tree to the public catalog root.

Regards,

Glenn

------------------------------

Message: 2
Date: Wed, 06 Jul 2011 15:33:13 -0600
From: John Caron <caron@xxxxxxxxxxxxxxxx>
To: thredds@xxxxxxxxxxxxxxxx
Subject: Re: [thredds] threddsConfig.xml - <catalogRoot>
Message-ID: <4E14D499.9050400@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Hi Glenn:

The idea with catalogRoot is to serve non-public catalogs. If you want
catalogs to be public, then link to them from the main catalog.xml.

So the answer is no, we dont have the ability to customize the
catalogRoots. Can you explain what your use case is?

John