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 08:18:38] steingod |
metamod:faq [2012-09-03 12:13:05] steingod [File formats] |
||
---|---|---|---|
Line 17: | Line 17: | ||
- Through web interface, FTP, scp etc | - Through web interface, FTP, scp etc | ||
- Ad hoc and regular data streams | - Ad hoc and regular data streams | ||
+ | - Configurable conformance check of NetCDF/CF files uploaded | ||
- Automatic extraction of metadata from datasets uploaded | - Automatic extraction of metadata from datasets uploaded | ||
- When uploaded as NetCDF/CF following the convention of METAMOD | - When uploaded as NetCDF/CF following the convention of METAMOD | ||
Line 66: | Line 67: | ||
- Reinitialise the static part of the database by running the script '' | - Reinitialise the static part of the database by running the script '' | ||
If several METAMOD instances are using the same database, this has to be done in the METAMOD instance that actually own the database. If the database has been running for a while, reinitialisation may take some time during which the METAMOD instances using the database will be unavailable. | If several METAMOD instances are using the same database, this has to be done in the METAMOD instance that actually own the database. If the database has been running for a while, reinitialisation may take some time during which the METAMOD instances using the database will be unavailable. | ||
+ | |||
+ | ==== How do I configure the conformance check for NetCDF/CF files? ==== | ||
+ | |||
+ | 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 176: | Line 204: | ||
- Several metadata values for the same metadata type and dataset, produce several DIF XML elements. | - Several metadata values for the same metadata type and dataset, produce several DIF XML elements. | ||
- An asterix (*) prepending an element name in the sequence of element names will force the start of a new DIF XML element at this level. (Othervise, new elements will, if possible, add to an already started higher level element). | - An asterix (*) prepending an element name in the sequence of element names will force the start of a new DIF XML element at this level. (Othervise, new elements will, if possible, add to an already started higher level element). | ||
+ | |||
+ | ===== 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 ==== | ||
+ | |||
+ | METAMOD has extended support for NetCDF/CF files where conformance checks and automatic extraction of metadata are supported. Some relevant information concerning NetCDF/CF can be found here: | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | |||
+ | ==== CDL ==== | ||
+ | |||
+ | Common Data Language provides an ASCII representation of NetCDF files. METAMOD do support direct upload of CDL files and will perform the same conformance checks in CDL as on NetCDF/CF files, as well as conversion to NetCDF/CF. | ||
+ | |||
+ | ==== NetCDF/CF global attributes ==== | ||
+ | |||
+ | The following global attributes are required in NetCDF/CF files uploaded through METAMOD for proper stewardship. Please note that this is a minimum requirement and is subject to change (some proposed changes are indicated below). | ||
+ | |||
+ | ^Name^Purpose^Status^Comment^ | ||
+ | |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 " | ||
+ | |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, | ||
+ | |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. Current vocabulary includes < | ||
+ | Cruise | ||
+ | Aircraft | ||
+ | Model run | ||
+ | Land station | ||
+ | Ice station | ||
+ | Submersible | ||
+ | Float | ||
+ | Space borne instrument | ||
+ | Other</ | ||
+ | |operational_status|Status of the dataset, being one of < | ||
+ | Pre operational | ||
+ | Operational | ||
+ | Scientific</ | ||
+ | |Conventions|The metadata convention used, should be '' | ||
+ | |product_name|A product name of the dataset.|Active|Controlled vocabulary| | ||
+ | |history|Modification history of the dataset. Should be of the form: < | ||
+ | 2007-06-10 revision</ | ||
+ | |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| | | ||
+ | |northernmost_latitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees).|Active| | | ||
+ | |westernmost_longitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees) with positive values towards the East.|Active| | | ||
+ | |easternmost_longitude|Elements to describe a geographicalbounding box for the data. Should be a floating point value (decimal degrees) with positive values towards the East.|Active| | | ||
+ | |start_date|Start date and time of the dataset in the form '' | ||
+ | |stop_date|Stop date and time of the dataset in the form '' | ||
+ | |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_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 '' | ||
+ | |citation|Information on how to cite the information properly.|Proposed|FIXME| | ||
+ | |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| | ||
+ | |||
+ | ===== 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? |