Differences

This shows you the differences between two versions of the page.

--- metamod:two_levels [2009-02-17 14:23:45] – egils
+++ metamod:two_levels [2009-02-24 10:01:06] (current) – heikok
@@ Line 37: / Line 37: @@
 These files are created by extracting metadata from netCDF files like name1_xxx.nc, name1_yyy.nc etc. The xml/xmd files on the highest level will remain exactly as they are today. The xml/xmd files on the lowest level will each represent one netCDF file only. The format of these files will be the same as those describing the directory level datasets. (This format is described on [[xml-format]]).
+The dataset ID field (xpath in .xmd file: ''dataset/info@name'') will be now restricted to match one or
+two ''/'' characters, one ''/'' meaning parent (''APPLICATION/DIRECTORY''), two ''/'' meaning file (''APPLICATION/DIRECTORY/FILE'').
+=== Updating from Metamod 2.1 to Metamod 2.2 (adding file-metadata) ===
+The current trunk of Metamod, which will lead to Metamod 2.2, extracts now both levels of metadata
+from fresh uploaded files. The file-metadata from older netcdf-files stored on the same machine in an OpENDAP enabled catalogue can be generated using the program ''createChildDatasets.pl'', which is installed in the script directory and should be used as:
+  createChildDatasets.pl /outputdir
+The outputdir will contain all second level metadata. After manual verification it should be copied over
+to metadata-directory of the project.
 ==== SEARCH module ====
-The main functionality of the search user interface will be kept. Searching will initially be limited to the highest (directory) level. When the search results are displayed, a small button [+] will be shown for each directory dataset that has corresponding files. When pushing this [+] button, the search result will be expanded with one row for each file record **//that match the search criteria//**. (Possibly we should also have a button that let the user see **//all//** the files belonging to that directory). Each row with file information includes a link directly to the THREDDS page for that file. The subtable with file information should have a separate headings row customized to the fields that vary between the file records.
+The main functionality of the search user interface will be kept. Searching will initially be limited to the highest (directory) level. When the search results are displayed, a small button [+] will be shown for each directory dataset that has corresponding files. When pushing this [+] button, the search result will be expanded with one row for each file record **//that match the search criteria//**. (Possibly we should also have a button that let the user see **//all//** the files belonging to that directory). Each row with file information includes a link directly to the THREDDS page for that file. The subtable with file information should have a separate heading row customized to the fields that vary between the file records.