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

Re: metadata question

Hi Ethan - I hope your prepared for this!

Specifically, the metadata element that does not work with the TDS HTML is <metadata xlink:href="http://sands01.ssec.wisc.edu:8080/thredds/Shelves/7a75/4fd8/7a754fd85b39c6b6795936bbcd26955d/"; xlink:title="Parent Dataset" />.

It fails with the error output found at http://www.ssec.wisc.edu/~brucef when navigating to the dataset containing the above metadata. The above XML works if you change the tag to documentation and place it in a metadata element. ???

What I am trying to accomplish is kinda hard to explain, but I'll give it a shot...

I have 2 parallel TDS representations for the same data. There is a "Shelves" tree generated using datasetScan that is an exact recreation of our datastore back-end on our XSAN. The data-store is in a format that is not user navigable, so for users to get to their data we provide soft-links to something more "friendly," which we call the "user links." The XSAN back-end will never change, but the user links might. I have python scripts that generate TDS catalogs from the user links that replicate the soft-linked user navigable access to the XSAN back-end.

So... If a link to a particular dataset(ie. netcdf file) is distributed from one user to another, that user may also be interested in the related files in the parent dataset. Therefore, there was a requirement to have a link to the parent dataset containing related files. Since the user links may change it made sense to provide that link to the shelves tree, which is static.

For example, the user links URL for the above metadata tag is http://localhost:8080/thredds/dodsC/User_Links/Users/johnm/catalog.html, which actually represents the same data.

So, it seems unnatural to classify the link to a parent dataset as documentation.


To unsubscribe thredds, visit:

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.