Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
metamod:faq [2010-09-27 09:08:43] steingod |
metamod:faq [2012-09-03 12:13:05] steingod [File formats] |
||
---|---|---|---|
Line 71: | Line 71: | ||
FIXME | FIXME | ||
+ | |||
+ | ===== Operation and maintenance ===== | ||
+ | |||
+ | ==== How do I remove datasets? ==== | ||
+ | |||
+ | The best solution is to use the administration interface (require login and appropriate user rights) and the " | ||
+ | |||
+ | ==== How do I change metadata? ==== | ||
+ | |||
+ | The preferred solution is to use the metadata editor included in the software. This is launched using the "File upload" | ||
+ | |||
+ | Sometimes, the solution above is insufficient. Under such conditions, direct modification of metadata and import of these from the webrun directory using '' | ||
+ | |||
+ | ==== How do I reinitialise the database? ==== | ||
+ | |||
+ | Use the following recipe (information in <> to be substituted as appropriate): | ||
+ | |||
+ | - sudo / | ||
+ | - sudo / | ||
+ | - sudo -u <web server owner> < | ||
+ | - sudo / | ||
+ | - sudo / | ||
+ | |||
===== Metadata exchange ===== | ===== Metadata exchange ===== | ||
Line 183: | Line 206: | ||
===== File formats ===== | ===== File formats ===== | ||
+ | |||
+ | ==== File formats relevance for METAMOD ==== | ||
+ | |||
+ | METAMOD is essentially agnostic concerning file formats. However, [[# | ||
+ | |||
+ | Basically METAMOD can relate to any file as long as the metadata are created manually and uploaded, but metadata can be extracted automatically from NetCDF/CF files. | ||
==== NetCDF/CF ==== | ==== NetCDF/CF ==== | ||
Line 205: | Line 234: | ||
|title|A short description of the data set|Active| | | |title|A short description of the data set|Active| | | ||
|abstract|A short summary of the data collection activity and data set. This element may alternatively be provided as the global attribute " | |abstract|A short summary of the data collection activity and data set. This element may alternatively be provided as the global attribute " | ||
- | |topiccategory|A blank separated list of topic keywords describing the dataset. | + | |topiccategory|A blank separated list of topic keywords describing the dataset. |
+ | climatologyMeteorologyAtmosphere | ||
+ | environment | ||
+ | geoscientificinformation | ||
+ | imageryBaseMapsEarthCover | ||
+ | inlandWaters | ||
+ | oceans | ||
+ | society</ | ||
|keywords|A blank separated list of keywords describing the dataset. FIXME|Active, | |keywords|A blank separated list of keywords describing the dataset. FIXME|Active, | ||
|gcmd_keywords|Newline separated list of GCMD scientific keywords describing the various variables. This will be used to categorize the datasets according to the " | |gcmd_keywords|Newline separated list of GCMD scientific keywords describing the various variables. This will be used to categorize the datasets according to the " | ||
- | |activity_type|Comma separated list of activity types. | + | |activity_type|Comma separated list of activity types. |
+ | Cruise | ||
+ | Aircraft | ||
+ | Model run | ||
+ | Land station | ||
+ | Ice station | ||
+ | Submersible | ||
+ | Float | ||
+ | Space borne instrument | ||
+ | Other</ | ||
|operational_status|Status of the dataset, being one of < | |operational_status|Status of the dataset, being one of < | ||
Pre operational | Pre operational | ||
Operational | Operational | ||
Scientific</ | Scientific</ | ||
- | |Conventions|The metadata convention used, should be '' | + | |Conventions|The metadata convention used, should be '' |
|product_name|A product name of the dataset.|Active|Controlled vocabulary| | |product_name|A product name of the dataset.|Active|Controlled vocabulary| | ||
|history|Modification history of the dataset. Should be of the form: < | |history|Modification history of the dataset. Should be of the form: < | ||
2007-06-10 revision</ | 2007-06-10 revision</ | ||
- | |area|Area name describing the geographical area being studied.If several area names are used, separate them using comma. | + | |area|Area name describing the geographical area being studied.If several area names are used, separate them using comma. |
+ | Barents Sea | ||
+ | Beufort Sea | ||
+ | Chukchi Sea | ||
+ | Denmark Strait Sea | ||
+ | East Siberian Sea | ||
+ | Fram Strait | ||
+ | Greenland Sea | ||
+ | Iceland Sea | ||
+ | Kara Sea | ||
+ | Laptev Sea | ||
+ | Nordic Seas | ||
+ | Northern Hemisphere | ||
+ | White Sea</ | ||
|southernmost_latitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees).|Active| | | |southernmost_latitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees).|Active| | | ||
|northernmost_latitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees).|Active| | | |northernmost_latitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees).|Active| | | ||
Line 226: | Line 284: | ||
|institution|Name of the institution responsible for the dataset. FIXME|Active|Controlled vocabulary| | |institution|Name of the institution responsible for the dataset. FIXME|Active|Controlled vocabulary| | ||
|PI_name|Name of the person responsible for the data set.|Active| | | |PI_name|Name of the person responsible for the data set.|Active| | | ||
+ | |PI_address|Address to the person responsible for the dataset.|Proposed|FIXME| | ||
|contact|email address to responsible user support or principal investigator. If the email address of the principal investigator is used, the variable '' | |contact|email address to responsible user support or principal investigator. If the email address of the principal investigator is used, the variable '' | ||
- | |distribution_statement|A distribution statement describing the conditions for distributing and access to the dataset. | + | |citation|Information on how to cite the information properly.|Proposed|FIXME| |
- | |use_statement|A use statement describing conditions for using the dataset.|Proposed|Controlled vocabulary| | + | |distribution_statement|A distribution statement describing the conditions for distributing and access to the dataset. |
+ | Restricted to < | ||
+ | No access until < | ||
+ | |use_statement|A use statement describing conditions for using the dataset.< | ||
+ | Cite properly | ||
+ | No commercial use, cite properly | ||
+ | PIC/CC0 | ||
+ | PIC/ | ||
|project_name|Name of the project within which the data were collected. Several project dependencies can be indicated using comma separated project names.|Active|Controlled vocabulary| | |project_name|Name of the project within which the data were collected. Several project dependencies can be indicated using comma separated project names.|Active|Controlled vocabulary| | ||
+ | ===== Common pitfalls ===== | ||
+ | |||
+ | ==== Why is METAMOD not including the XML-information located in the webrun directory? ==== | ||
+ | |||
+ | One possible cause can be that there is a conflict between users. Please remember that all scripts and processes has to be run under the user that owns the web server (e.g. www-user or www-data). If this is not the case, try removing the '' | ||
+ | |||
+ | Another possible cause is that the XML-information is inconsistent/ | ||
+ | |||
+ | ==== Why is METAMOD not showing the data I uploaded? ==== | ||
+ | |||
+ | One possible cause can be that the dataset tag is not correct. Check the contents of the '' | ||
+ | |||
+ | See [[#Why is METAMOD not including the XML-information located in the webrun directory? |