IMSMA and maXML

	The selection of fields used for Data Entry Forms differs between countries. Mine Action Programs also have the possibility to add its own fields or modify the existing standard ones. This means that IMSMA^NG data can be very different between countries. It is therefore necessary to understand a country’s specific set of data collection forms in order to be able to exchange information with that country’s IMSMA^NG.

Artifacts

The Artifact pages reflect the structure and sequence of elements as defined and exported by IMSMA^NG. The form of maXML exported and imported by IMSMA^NG differs slightly from the maXML defined by the generic maXML schema and therefore some exports will not validate to the original schema. Anyone who would like to exchange information with IMSMA^NG should follow IMSMA^NG maXML dictionary to construct or read a maXML file correctly formatted for IMSMA^NG.

IMSMA^NG imports its main objects in the form of field reports. The different types of field reports are all collected under the parents MineActionFieldReport, FieldReport in maXML. In order to correctly form a field report for import by IMSMA^NG one would need to construct a maXML document containing the elements DocumenHeader (not required see below), FieldReportInfo and the desired type of field report, there is also the option to include the element attachment if relevant. The different types of field report are Accident, Hazard, HazardReduction, Location, MREActivity, QAActivity, Victim, and VictimAssistance. Multiple field reports of various types can be included in one file and imported by IMSMA^NG each separate field report should then be contained within its own FieldReport tags.

Some elements are used by several Artifacts such as DocumentHeader, GeospatialInfo etc. and they are specified in the Common pages. The common elements are listed in the artifacts they appear to reflect their location in maXML but with a reference to find their specification in common elements.

For radiobuttons and checkboxes IMSMA^NG uses enumeration values retrieved from an enumeration table to restrict the choices available. IMSMA Enum Category refers to the category of enumeration values for the IMSMA^NG field in question. The enumeration value is often translated to a different value when displayed in the application IMSMA^NG, either in a different language or in the same language but with another value (e.g. the Land status enumeration list/category contains Active (a.k.a. Base Term) but the value displayed in IMSMA^NG is Open.

An enumeration list may be obtained by contacting your GICHD IM advisor. Choices in IMSMA^NG can be customised to fit the needs of specific Mine Action programmes. Customised values are added to the IMSMA enumeration list when created. It is therefore recommended to request specific lists of enumeration values from each country.

In addition to the field reports there are eight elements for Auxiliary data. IMSMA^NG does not currently import Auxiliary data but it does export it. It will be of interest to read Auxiliary data from IMSMA^NG for any system that intends to exchange information with IMSMA^NG as there are often many references to Auxiliary data in a field report. Information about organisations, places, country structure and more are referred to in a field report through GUIDs which can only be obtained from an IMSMA^NGinstallation.

Required/recommended elements and attributes

There are very few elements in maXML that are absolutely required in order for IMSMA^NG to import the data. Non required elements can be excluded from an import but obviously any information they may contain will not be imported. The attribute originalValue is used and exported by IMSMA^NG for all multiple and single select fields in IMSMA^NG. They are always the same as the value of the element and can be excluded without any loss of information. The element UnitOfMeasure and all children of the same are exported by IMSMA^NG but are automatically set to default values during import and can therefore be excluded without any loss of information.

The only value within DocumentHeader that will be stored by IMSMA^NG if included is the FileCreationDateTime, all others will have values automatically assigned by IMSMA^NG whether they contain anything or not. If left out the FileCreationDateTime will be assigned to the moment of import by IMSMA^NG. The DocumentHeader element can be left out entirely from a xml file and IMSMA^NG will still import it without errors or information lost.