IMSMA and maXML - Revision history

Alnaucler at 13:39, 24 July 2019

2019-07-24T13:39:31Z

← Older revision		Revision as of 15:39, 24 July 2019
Line 10:		Line 10:
	For radiobuttons and checkboxes {{IMSMANG}} 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 {{IMSMANG}} field in question. The enumeration value is often translated to a different value when displayed in the application {{IMSMANG}}, 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 {{IMSMANG}} is ''Open''.		For radiobuttons and checkboxes {{IMSMANG}} 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 {{IMSMANG}} field in question. The enumeration value is often translated to a different value when displayed in the application {{IMSMANG}}, 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 {{IMSMANG}} is ''Open''.

	An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.		An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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. {{IMSMANG}} does not currently import Auxiliary data but it does export it. It will be of interest to read Auxiliary data from {{IMSMANG}} for any system that intends to exchange information with {{IMSMANG}} 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 {{IMSMANG}}installation.		In addition to the field reports there are eight elements for Auxiliary data. {{IMSMANG}} does not currently import Auxiliary data but it does export it. It will be of interest to read Auxiliary data from {{IMSMANG}} for any system that intends to exchange information with {{IMSMANG}} 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 {{IMSMANG}}installation.

Alnaucler at 19:05, 12 June 2017

2017-06-12T19:05:42Z

← Older revision		Revision as of 21:05, 12 June 2017
Line 2:		Line 2:

	==Artifacts ==__NOEDITSECTION__		==Artifacts ==__NOEDITSECTION__
	The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by {{IMSMANG}} 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 {{IMSMANG}} should follow {{IMSMANG}} maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.		The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by {{IMSMANG}} '''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 {{IMSMANG}} should follow {{IMSMANG}} maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.

	{{IMSMANG}} 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 {{IMSMANG}} 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 {{IMSMANG}} each separate field report should then be contained within its own FieldReport tags.		{{IMSMANG}} 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 {{IMSMANG}} 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 {{IMSMANG}} each separate field report should then be contained within its own FieldReport tags.

Alnaucler at 19:05, 12 June 2017

2017-06-12T19:05:12Z

← Older revision		Revision as of 21:05, 12 June 2017
Line 2:		Line 2:

	==Artifacts ==__NOEDITSECTION__		==Artifacts ==__NOEDITSECTION__
	The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by ~~IMSMA~~ 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 {{IMSMANG}} should follow ~~IMSMA~~ maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.		The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by {{IMSMANG}} 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 {{IMSMANG}} should follow {{IMSMANG}} maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.

	~~IMSMA~~ 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 ~~an IMSMA system~~ 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~~ each separate field report should then be contained within its own FieldReport tags.		{{IMSMANG}} 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 {{IMSMANG}} 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 {{IMSMANG}} 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.		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~~ 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~~ field in question. The enumeration value is often translated to a different value when displayed in the application ~~IMSMA~~, 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 {{IMSMANG}} is ''Open''.		For radiobuttons and checkboxes {{IMSMANG}} 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 {{IMSMANG}} field in question. The enumeration value is often translated to a different value when displayed in the application {{IMSMANG}}, 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 {{IMSMANG}} is ''Open''.

	An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.		An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.

Alnaucler at 18:50, 12 June 2017

2017-06-12T18:50:20Z

← Older revision		Revision as of 20:50, 12 June 2017
Line 1:		Line 1:
	{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.}}		{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.}}

			==Artifacts ==__NOEDITSECTION__
			The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by IMSMA 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 {{IMSMANG}} should follow IMSMA maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.

			IMSMA 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 an IMSMA system 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 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.		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.
Line 6:		Line 11:

	An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.		An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.

	~~==Artifacts ==__NOEDITSECTION__~~
	The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by IMSMA 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 {{IMSMANG}} should follow IMSMA maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.

	IMSMA 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 an IMSMA system 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 each separate field report should then be contained within its own FieldReport tags.

	In addition to the field reports there are eight elements for Auxiliary data. {{IMSMANG}} does not currently import Auxiliary data but it does export it. It will be of interest to read Auxiliary data from {{IMSMANG}} for any system that intends to exchange information with {{IMSMANG}} 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 {{IMSMANG}}installation.		In addition to the field reports there are eight elements for Auxiliary data. {{IMSMANG}} does not currently import Auxiliary data but it does export it. It will be of interest to read Auxiliary data from {{IMSMANG}} for any system that intends to exchange information with {{IMSMANG}} 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 {{IMSMANG}}installation.

Alnaucler at 18:48, 12 June 2017

2017-06-12T18:48:58Z

← Older revision		Revision as of 20:48, 12 June 2017
Line 1:		Line 1:
	{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.		{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.}}

	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.		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.

Alnaucler at 18:48, 12 June 2017

2017-06-12T18:48:30Z

← Older revision		Revision as of 20:48, 12 June 2017
Line 1:		Line 1:
	{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.}}		{{Note \| 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 {{IMSMANG}} 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 {{IMSMANG}}.

	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.		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.
Line 7:		Line 7:
	An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.		An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.

	The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}. The form of maXML exported and imported by IMSMA 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 {{IMSMANG}} should follow IMSMA maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.		==Artifacts ==__NOEDITSECTION__
			The Artifact pages reflect the structure and sequence of elements as '''defined and exported''' by {{IMSMANG}}. The form of maXML exported and imported by IMSMA 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 {{IMSMANG}} should follow IMSMA maXML dictionary to construct or read a maXML file correctly formatted for {{IMSMANG}}.

	IMSMA 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 an IMSMA system 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 each separate field report should then be contained within its own FieldReport tags.		IMSMA 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 an IMSMA system 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 each separate field report should then be contained within its own FieldReport tags.

Alnaucler at 18:46, 12 June 2017

2017-06-12T18:46:36Z

@@ Line 1: / Line 1: @@
-{{IMSMANG}} exchanges data by exporting and importing maXML files containing information in the form of Data Entry Forms or Auxiliary Data. Data Entry Forms in {{IMSMANG}} uses a selection of fields from a certain topic depending on needs to collect or enter information ex. Accident can either use fields for civilian accidents in non-surveyed areas or for demining accidents in Land during clearance activities.
+{{Note | 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 {{IMSMANG}} 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 {{IMSMANG}}.}}
 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.
@@ Line 13: / Line 6: @@
 An enumeration list may be obtained by contacting your [[Information Management Team | GICHD IM advisor]]. Choices in {{IMSMANG}} 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.
 {{NavBox XML Documentation}}
 [[Category:NAA]]

Alnaucler at 18:31, 12 June 2017

2017-06-12T18:31:51Z

← Older revision		Revision as of 20:31, 12 June 2017
Line 6:		Line 6:

	==Documentation structure==__NOEDITSECTION__		==Documentation structure==__NOEDITSECTION__
	The elements in each Artifact are explained in detail in the sub pages by specifying all elements within the Artifacts~~. Each element has a short description together with a table listing its type, IMSMA Field Name, IMSMA Type and its IMSMA Enum Category~~.		The elements in each Artifact are explained in detail in the sub pages by specifying all elements within the Artifacts.

	Some elements are used by several Artifacts such as DocumentHeader, GeospatialInfo etc. and they are specified ~~at the end of~~ the ~~chapter under common elements~~. The common elements are ~~still~~ listed in the artifacts they appear to reflect their location in maXML but with a reference to find their specification in common elements.		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.

	~~The IMSMA type is the type of field in {{IMSMANG}} Data Entry Forms that records the information contained by the element. IMSMA Type can be~~
	* Any Value,
	* any Number,
	* Multiple Values,
	* Single Value
	* Date.

	~~Any Value means that the information is collected through a textbox without any restrictions on what can be entered.~~
	~~Any number is a textbox restricted to numbers only.~~
	~~Multiple values means that {{IMSMANG}} collects the information through checkboxes and therefore that the values are predefined but that multiple values can be selected.~~
	~~Single value indicates that {{IMSMANG}} collects the information through radiobuttons where values are predefined and only one value can be selected.~~
	~~Date is a field restricted to the date format~~.

	For radiobuttons and checkboxes IMSMA 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 field in question. The enumeration value is often translated to a different value when displayed in the application IMSMA, 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 {{IMSMANG}} is ''Open''.		For radiobuttons and checkboxes IMSMA 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 field in question. The enumeration value is often translated to a different value when displayed in the application IMSMA, 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 {{IMSMANG}} is ''Open''.

	An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.		An enumeration list may be obtained by contacting your [[Information Management Team \| GICHD IM advisor]]. Choices in {{IMSMANG}} 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.


	{{NavBox XML Documentation}}		{{NavBox XML Documentation}}
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler: Created page with "{{IMSMANG}} exchanges data by exporting and importing maXML files containing information in the form of Data Entry Forms or Auxiliary Data. Data Entry Forms in {{IMSMANG}} use..."

2017-06-12T13:27:49Z

Created page with "{{IMSMANG}} exchanges data by exporting and importing maXML files containing information in the form of Data Entry Forms or Auxiliary Data. Data Entry Forms in {{IMSMANG}} use..."

New page

{{IMSMANG}} exchanges data by exporting and importing maXML files containing information in the form of Data Entry Forms or Auxiliary Data. Data Entry Forms in {{IMSMANG}} uses a selection of fields from a certain topic depending on needs to collect or enter information ex. Accident can either use fields for civilian accidents in non-surveyed areas or for demining accidents in Land during clearance activities.

Currently {{IMSMANG}} can only export auxiliary data, not import it. The latest review of maXML has focused mainly on updating the maXML schema for those parts that can be imported into {{IMSMANG}}. The schemas description of auxiliary data still differs in many cases from how {{IMSMANG}} exports this information and should not be considered representative of {{IMSMANG}}.

The selection of fields used for Data Entry Forms usually differs between countries. Mine Action Programs also have the possibility to add its own fields or modify the existing standard ones. This means that {{IMSMANG}} 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 {{IMSMANG}}.

==Documentation structure==__NOEDITSECTION__
The elements in each Artifact are explained in detail in the sub pages by specifying all elements within the Artifacts. Each element has a short description together with a table listing its type, IMSMA Field Name, IMSMA Type and its IMSMA Enum Category.

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

The IMSMA type is the type of field in {{IMSMANG}} Data Entry Forms that records the information contained by the element. IMSMA Type can be
* Any Value,
* any Number,
* Multiple Values,
* Single Value
* Date.

Any Value means that the information is collected through a textbox without any restrictions on what can be entered.
Any number is a textbox restricted to numbers only.
Multiple values means that {{IMSMANG}} collects the information through checkboxes and therefore that the values are predefined but that multiple values can be selected.
Single value indicates that {{IMSMANG}} collects the information through radiobuttons where values are predefined and only one value can be selected.
Date is a field restricted to the date format.

For radiobuttons and checkboxes IMSMA 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 field in question. The enumeration value is often translated to a different value when displayed in the application IMSMA, 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 {{IMSMANG}} is ''Open''.

An enumeration list may be obtained by contacting your [[Information Management Team | GICHD IM advisor]]. Choices in {{IMSMANG}} 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.

{{NavBox XML Documentation}}
[[Category:NAA]]