... | ... | @@ -45,7 +45,7 @@ What we do is having a way for the parser to tell us what he can extract, and on |
|
|
# Metadata
|
|
|
|
|
|
To define what is extracted, and model it from the conceptual point of view we use metadata.
|
|
|
Our metadata model is pretty flexible, can accommodate extensions amd is described in [NomadMetaInfo]().
|
|
|
Our metadata model is pretty flexible, can accommodate extensions amd is described in [NomadMetaInfo](NomadMetaInfo).
|
|
|
|
|
|
This is a central thing to make the whole system interoperable.
|
|
|
|
... | ... | @@ -112,7 +112,7 @@ The parser then should reply with a json list containing dictionaries that give |
|
|
- collectiveSha: sha of all the files connected to the calculation
|
|
|
|
|
|
The parser can be implemented with any language as long it conforms with this interface.
|
|
|
All the parsers currently used are implemented in python and there is already an infrastructure to simplify the implementation of such parsers using python as detailed in the [NomadParsing wiki](http://nomad-dev.rz-berlin.mpg.de/wiki/NomadParsing}).
|
|
|
All the parsers currently used are implemented in python and there is already an infrastructure to simplify the implementation of such parsers using python as detailed in the [NomadParsing wiki](http://nomad-dev.rz-berlin.mpg.de/wiki/NomadParsing).
|
|
|
|
|
|
output:
|
|
|
|
... | ... | |