Metadata import options
- Last UpdatedSep 03, 2025
- 2 minute read
Import Metadata configuration file
The metadata importer converts a source metadata file into a standardized JSON file. If the name of the generated JSON file matches the name of a MWX Soup node, the JSON will be loaded along with the node content and made available to the user.
The importer currently supports import from RVM metadata .txt files and AVEVA Gateways metadata .xml files, but has been designed to be able to expand to support other formats.
Settings
These are the settings for a metadata import configuration file.
|
Parameter |
Type |
Default |
Description |
|---|---|---|---|
|
destinationpath |
sstring |
Not set |
The source destination path. Include filename with extension to overload file name. |
|
fileName |
sstring |
Not set |
If left empty, the name of the input file will be used. Any file name can be specified. The file extension will be overwritten according to the conversion output. Note that the output path is user’s Model folder. |
The converted metadata file
RVM Metadata
When converting the original file, data is moved into a structured JSON file. In particular, header information of the input metadata will be stored inside $[‘Header Information’] and syntax definitions will be stored into $[‘meta’], with each definition of key-value pairs as children.
AVEVA Gateways metadata(EIWM)
When converting the original file, data is moved into a structured JSON file. It follows the same structure as in source file. Each object is stored as a separate elements with associations, characteristics, properties and so on.
FindElement
One important thing to acknowledge is that sometimes the model metadata structure does not reflect the model geometry hierarchy 1-1. Therefore, finding a specific object metadata will require using the findElement functionality of the SJSON field data type—the hierarchy of the geometry will not be a valid path inside the JSON metadata.
Metadata field
MWX Soup nodes feature a metadata field. The metadata field is populated at load time with the content of the JSON converted metadata—if the metadata file is in the same folder and has the same name as the imported model.