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.
carlw@xxxxxxxxxxxxxxxx wrote:
Late in the day, probably didn't make myself very clear. We felt that online users who accessed the catalog might find themselves navigating within these html pages. And as a convenience, if they were on the parent dataset page (for a particular dataset) where the complete metadata is presented, we wanted to make it easy to directly go to the CatalogRef listing for that dataset without going back to the main thredds catalog page at http://dodsdev.gso.uri.edu/thredds/ and linking through there.
so a catalog like http://motherlode.ucar.edu:8080/thredds/catalogServices?catalog=http://motherlode.ucar.edu:8080/thredds/idd/model/DGEX/Alaska_12km/catalog.xml should link to its parent catalog: http://motherlode.ucar.edu:8080/thredds/catalogServices?catalog=http://motherlode.ucar.edu:8080/thredds/idd/dgex_model.xml ??
And the other potential link I referred to would be down at the granule level. On our present catalog, if you go down to metadata at the granule level, which is accessed by the links in the CatalogRef element for eachdataset, we were suggesting alink down at this granule level back up to the parent dataset (metadata) page that I mentioned in the previous paragraph.
so a dataset "node" like http://motherlode.ucar.edu:8080/thredds/catalog.html?cmd=subset&catalog=http://motherlode.ucar.edu:8080/thredds/idd/model/DGEX/Alaska_12km/catalog.xml&dataset=NCEP/DGEX/Alaska_12km/DGEX_Alaska_12km_20051221_0000.grib2 should link to its containing catalog, like: http://motherlode.ucar.edu:8080/thredds/catalogServices?catalog=http://motherlode.ucar.edu:8080/thredds/idd/model/DGEX/Alaska_12km/catalog.xml ?? If thats what you mean, that seems reasonable, the second one is easy to implement, but Im not sure if the first one is; catalogs dont know who their parents are, if they exist, and the parent doesnt have to be unique.
thredds archives: