Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
metamod:minutes2009_12_03 [2009-12-08 15:12:59] egils |
metamod:minutes2009_12_03 [2022-05-31 09:29:32] (current) |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| Calling this url will extract the metadata from the files named by '' | Calling this url will extract the metadata from the files named by '' | ||
| - | Comments by --- // | + | ===== Discussion ===== |
| + | |||
| + | **Comments by --- // | ||
| This solution (with no restrictions on file names belonging to a given dataset) gives us some problems regarding THREDDS catalogs. Up to now, we have used the datasetScan element in the THREDDS catalog to create a dataset entry within THREDDS corresponding to all files in a directory. We can continue to use this method if all files in a dataset belongs to the same directory. Then the consequences will not be wery difficult to cope with: We can contunue to use the same method to create THREDDS catalogs, and few changes need to be done in the web interface for creating new datasets. | This solution (with no restrictions on file names belonging to a given dataset) gives us some problems regarding THREDDS catalogs. Up to now, we have used the datasetScan element in the THREDDS catalog to create a dataset entry within THREDDS corresponding to all files in a directory. We can continue to use this method if all files in a dataset belongs to the same directory. Then the consequences will not be wery difficult to cope with: We can contunue to use the same method to create THREDDS catalogs, and few changes need to be done in the web interface for creating new datasets. | ||
| Line 23: | Line 25: | ||
| If we can not assume this correspondence, | If we can not assume this correspondence, | ||
| + | |||
| + | |||
| + | **Comment by --- // | ||
| + | That are in fact two questions: | ||
| + | - Can we assume that all files belonging to one dataset reside in one directory? | ||
| + | - Can we assume that all files in a directory belong to one dataset? | ||
| + | |||
| + | I think question 1) should be made a requirement. If we allow to scan subdirectories for additional use by the data-provider, | ||
| + | |||
| + | Question 2) will not be true. The southern-hemisphere and northern-hemisphere files of the ice-products will (most likely) reside in one directory, but Metamod needs to have two different datasets to allow for efficient geographical search and display. I think it is not a big problem, that a users sees a directory with both northern and southern hemisphere data after he is redirected from Metamod to thredds. | ||
| + | |||
| + | We can think about a solution, which creates virtual directories in thredds by writing a explicit mapping between a dataset and a file, without using a dataset-scan. This solution is implemented in our thredds server for the MyOcean data, which puts all data-files into one directory and maps the files to two virtual directories, | ||
| ===== Timeline ===== | ===== Timeline ===== | ||