Date: Thu, 28 Mar 2024 12:14:23 +0000 (UTC) Message-ID: <1930241053.3866.1711628063823@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3865_563760543.1711628063823" ------=_Part_3865_563760543.1711628063823 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Schemas represent the data you wish to extract from NMIS. They are= broken down by the name of the table they will export to. Schema's s= hould only ever be changed on the MySQL server and then pushed out to the N= MIS servers. If a schema is changed it's version number in the schema= _set.json file should be incremented, if it is not the results will be = ;indeterminate.
The schema_set.json file lists the schemas that are available in an arry= a, the version of each schema it holds and some more information about each= individual schema. An example of a schema that it holds is:
"system" : { "schema" : "system", "schema_type" : "Inventory", "file_name" : "export-system.json", "version" : 1 }
Each schema file holds an array of the data points that it will export, = an example that is found in every file is this:
{ "data_source" : "node-node.nmis", "data_location" : "system", "data_location_type" : "Flat", "data_name" : "name", "data_type" : "varchar", "data_length" : 255=20 },