When using the CMR catalog, the dataset link works correctly until/unless the default catalog is accessed. When the default catalog is accessed, then the dataset displayed because the dataset displayed for any of the CMR datasets. The dataset displayed is the most recent dataset access from the default catalog.
Now I am experiencing the error like this:
Start server. Poke around normal test data. Look at DDS output:
Go to a CMR dataset and look at its DDS (Takes some time for it to download the file into the CMR cache).
CMR dataset DDS looks ok.
Go back to normal test data.
All DDS responses are now the same as the CMR dataset DDS.
I can trigger the error using besstandalone
Here are some test files:
This file gets the DDS of our friend data/nc/fnoc1.nc in the default catalog (catalog)
This file gets the DDS of a dataset in the CMR catalog.
Two or more of these commands may be combined in a single BES command file:
This file gets the DDS for data/nc/fnoc1.nc followed by the DDS of the CMR dataset. (WORKS.)
This file gets the DDS for the CMR dataset followed by the DDS of data/nc/fnoc1.nc. (BROKEN - returns the CMR dataset DDS for the second request.)
This file gets the DDS for data/nc/fnoc1.nc followed by the DDS of the CMR dataset followed by the DDS of data/nc/fnoc1.nc. (BROKEN - returns the CMR dataset DDS for the final request.)
I just added *
This file gets the DDS of the CMR dataset, deletes the container from the CMR request. and then gets the DDS for data/nc/fnoc1.nc (WORKS.)