Closed jh-RLI closed 2 years ago
@henhuy looked into omi´s conversion functionality and found out is outdated quite a lot. To me it seems like I would need too much time to fix it ATM. It wasn't touched since oem-v1.3.0. The conversion method uses one of the available parser classes (see the upaded one for oem-v1.5.0) . Since we have made some changes to the metadata structure, the conversion tool needs to know the structures of all metadata versions. But at the moment we only work with one structure, which should always be up to date with the latest metadata version. (see comment above)
okay, thanks for checking. Conversion looks rather complicated and I am not familiar with it. So I will not add this to our meta_creator right now.
Since we have developed the metadata standard OEM further and have not adapted omi immediately, the metadata conversion from a low version to the latest version is currently not supported.
With version v1.5.0 the structure of the metadata was changed, essentially under the key "temporal" the subkey timeseries (already introduced in v1.4.1) was changed to the type list of objects :[{..},{..}]. Since omi works with the current version of the oem structure and does not use one structure definition per version, it is necessary to define in the parser classes or directly in the conversion how the current structure can be translated to the desired metadata version. Also the other new keys have to be included in the conversion method.
If you install omi and try to convert a metadata file v1.4.1 to v.1.5.0 (using the metadata from the oemetadata repository) there is some output but the output is very limited and not correct.
omi translate -f oep-v1.4 -t oep-v1.5 ..\oemetadata\metadata\v141\example.json
Output: