Differences
This shows you the differences between two versions of the page.
metamod:faq [2010-09-27 08:18:38] steingod |
metamod:faq [2022-05-31 09:29:32] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Frequently Asked Questions ====== | ||
- | ===== Features ===== | ||
- | |||
- | ==== What is the purpose of METAMOD? ==== | ||
- | |||
- | METAMOD was initially developed to support scientific projects with data management. Development has focused on a cost effective system where several projects or operational services can share the same backend while maintaining a custom built user interface specific for each project. One METAMOD implementation may support many METAMOD instances. The first instance always own the database and some maintenance and configuration aspects are only available through this instance. | ||
- | |||
- | ==== What are the main features of METAMOD? ==== | ||
- | |||
- | METAMOD was developed to support data management focusing on: | ||
- | - Metadata handling | ||
- | - Human and machine interfaces | ||
- | - Import/ | ||
- | - Support for dataset uploading | ||
- | - Interactive and automated | ||
- | - Through web interface, FTP, scp etc | ||
- | - Ad hoc and regular data streams | ||
- | - Automatic extraction of metadata from datasets uploaded | ||
- | - When uploaded as NetCDF/CF following the convention of METAMOD | ||
- | - Connection to online datasets | ||
- | - METAMOD is usually linked to a THREDDS Data Server actually serving the data sets | ||
- | |||
- | ===== Configuration ===== | ||
- | |||
- | ==== How do I change the runtime environment? | ||
- | |||
- | The runtime environment is generated during installation of the software (see the README file coming with the software for details). Basically the following procedure is used to set up a METAMOD instance: | ||
- | - Edit '' | ||
- | - Run '' | ||
- | - This creates a runtime source code tree located as defined within '' | ||
- | - If a first time set up, run '' | ||
- | - Run '' | ||
- | - Start the system by running '' | ||
- | |||
- | If changes are made to '' | ||
- | |||
- | ==== How do I change the appearance of the web interface? ==== | ||
- | |||
- | The visual appearance of METAMOD is determined by style sheets and contents of the '' | ||
- | - '' | ||
- | - '' | ||
- | - '' | ||
- | - '' | ||
- | |||
- | ==== How do I change the menus of the METAMOD web interface? ==== | ||
- | |||
- | METAMOD has two main menu containers. One top left (available within all modules) and one left (mainly in the search module and the upload). The top left menu is set up using the '' | ||
- | |||
- | The search module menu is configured using the '' | ||
- | - Activity type | ||
- | - Area | ||
- | - Variables (hidden) | ||
- | - Topics and variables | ||
- | - TBW | ||
- | - TBW | ||
- | - Institutions | ||
- | - Datacollection period | ||
- | - Map search | ||
- | - Operational status | ||
- | |||
- | In addition the keyword '' | ||
- | |||
- | In order to add new search categories the following sequence is required: | ||
- | - Edit the file '' | ||
- | - 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. | ||
- | |||
- | ===== Metadata exchange ===== | ||
- | |||
- | ==== Which metadata exchange protocols do METAMOD support? ==== | ||
- | |||
- | [[http:// | ||
- | |||
- | ==== Which metadata standards do METAMOD support? ==== | ||
- | |||
- | METAMOD use an internal metadata standard that is mapped to [[http:// | ||
- | |||
- | ==== What is the structure of the metamod metadata xml files? ==== | ||
- | |||
- | Information and schemata of the metadata-files used since Metamod 2.1 can be found under [[xml-format]]. | ||
- | |||
- | ==== Where do I get the metadata as dif/ | ||
- | |||
- | http:// | ||
- | |||
- | ==== How should metadata in the database be mapped to a DIF XML? ==== | ||
- | The metadata structure is configurable, | ||
- | |||
- | The METAMODPMH module contain a translation from the database to DIF XML. For the time being, this translation is implemented in a PHP script oaidp-config.php. This script contains an array which defines the translation: | ||
- | |||
- | < | ||
- | $key_conversion = array( | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | ' | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | '', | ||
- | ' | ||
- | ' | ||
- | '', | ||
- | '', | ||
- | ' | ||
- | '', | ||
- | ); | ||
- | </ | ||
- | |||
- | In this array, triples of three consecutive elements (starting with elements 0, 1 and 2 on the first line) constitute the translation of one metadata item in the database to one XML element in the DIF. | ||
- | |||
- | Each triple comprise the following components: | ||
- | |||
- | - Name of metadata type in the database (or an empty string) | ||
- | - Sequence of element names used in the DIF | ||
- | - Constant value | ||
- | |||
- | If these three components has, for example, the following contenet: | ||
- | |||
- | ' | ||
- | |||
- | and "METNO Norwegian Meteorological Institute" | ||
- | |||
- | < | ||
- | <DIF ...> | ||
- | ... | ||
- | < | ||
- | ... | ||
- | < | ||
- | ... | ||
- | </ | ||
- | ... | ||
- | </ | ||
- | </ | ||
- | |||
- | The sequence of triples in the array define the sequence of the elements in the DIF XML. If possible, one triple will use the same higher level XML elements as the previous triple. | ||
- | |||
- | These points constitute the general rule, but some special rules apply: | ||
- | |||
- | - If an ' | ||
- | - If the third component in the triple (the constant value) is non-empty, it is used as the value in the DIF XML. The first component will then usually be empty. | ||
- | - A number may follow the metadata type name. This indicate a spacial conversion of the metadata value in the database. This conversion is implemented in the get_exception.php routine. | ||
- | - If several consecutive triples have the same metadata type name, they will appear as consecutive elements in the DIF XML. When this is the case, different conversions of the metatdata value will take place (indicated by a number as explained above). | ||
- | - 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). |