277
edits
Changes
no edit summary
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 1. Conventions'''
|-
| width="100pt" | '''Convention'''
=== Article 7: Form A===__NOEDITSECTION__
The ''Article 7: Form A'' report returns the total area size of all reductions that are being reported on, the total area size of all Lands Land that have been linked to the reported reductions, and a count of all victims that have been linked to the reported reductions. If a search definition is associated with the report, the search definition name will be displayed in the report title.
[[Image:fig41SampleReport.png|center|500px|''Figure 41. Sample report - Article 7 form A'']]
===Article 7: Form C===__NOEDITSECTION__
The ''Article 7: Form C'' report returns a crosstab by district and Land with the number of Lands Land by Land type.
[[Image:Article 7FormC.png|center|500px|''Figure 42. Sample report- Article 7-form C'']]
==Bar Chart Sample==__NOEDITSECTION__
The ''Bar Chart'' sample report returns the metal contamination level of Lands Land and area size. The report includes a bar chart which summarizes the total area size of Lands Land by their metal contamination level.
[[Image:BarChartSample.png|center|500px|''Figure 43.'' ''Sample report- Bar chart'' '']]
|}
==Lands Land by Ordnance Type==__NOEDITSECTION__The Lands Land by Ordnance Type report shows summary data based on the full set of Ordnance Types present. This report groups Lands Land based on the full list of Ordnance SubCategories that are found on the Land. The report displays the name of the search in the report title.
[[Image:MRE audience.png|center|500px|''Figure 45.'' ''Sample report- Land by ordnance type'']]
{| class="wikitable"
|-
| File name || Lands Land by Ordnance Type.jrxml
|-
| Data source|| Land
|-
| Variables
|| Count of Lands Land for each ordnance sub-category
Sum of area size,
Average of area size
The Education Audience Totals by Age report lists the different age categories of Education audiences and the total number of male, female, and unknown gender in each age category.
[[Image:MRE audience.png|center|500px|''Figure 46.'' ''Sample report- Education audience totals by age'']]
====Table 11====__NOEDITSECTION__
==Pie Chart Sample==__NOEDITSECTION__
The Pie Chart sample report returns the metal contamination level of Lands Land and area size. The report includes a pie chart which summarizes the total area size of Lands Land by their metal contamination level.
[[Image:Pie Chart.png|center|500px|''Figure 47.'' ''Sample report- Pie chart'']]
====Table 12====__NOEDITSECTION__
Set the SUB-REPORT_DIR parameter to .\Sub-reports\.
[[Image:Accident Victim.png|center|500px|''Figure 48.'' ''Sample report- Accident victim summary'']]
====Table 13====__NOEDITSECTION__
Data source: Land
[[Image:Hazard Summary.png|center|500px|''Figure 49.'' ''Sample report- Land summary'']]
===Activity Summary Report===__NOEDITSECTION__
File: Summary_Hazreduc.jrxml
Data source: Activity
[[Image:Hazard Reduction.png|center|500px|''Figure 50.'' ''Sample report- Activity summary'']]
===Location Summary Report===__NOEDITSECTION__
File: Summary_Location.jrxml
Data source: Location
[[Image:Location Summary.png|center|500px|''Figure 51.'' ''Sample report- Location summary'']]
==Education Summary Report==__NOEDITSECTION__
Set the SUB-REPORT_DIR parameter to .\Sub-reports\.
[[Image:MRE Summary.png|center|500px|''Figure 52.'' ''Sample report- Education summary'']]
====Table 15====__NOEDITSECTION__
Data source: Organisation
[[Image:Organisation List Report.png|center|500px|''Figure 53.'' ''Sample report- Organisation list'']]
===Place List Report===__NOEDITSECTION__
File: Summary_Place.jrxml
Data source: Place
[[Image:Place List Report.png|center|500px|''Figure 54.'' ''Sample report- Place list'']]
===Quality Control Summary Report===__NOEDITSECTION__
File: Summary_QA.jrxml
Data source: Qa
[[Image:Quality Control Summary Report.png|center|500px|''Figure 55.'' ''Sample report- Quality control summary'']]
==Appendix A: IMSMA Database==__NOEDITSECTION__
===Overview===__NOEDITSECTION__
The IMSMA database contains tables for IMSMA’s base data (country structures, explosive, ordnance, organisations, and places), locations, and the locations’ associated accidents, LandsLand, Activities, Educations, QMs, and victims.
[[Image:fig56iR_Appndx.png|center|500px|''Figure 56. Conceptual database model'']]
<div align="center">
''Figure 56. Conceptual database model''
</div>
Within each country structure are zero or more locations. For example, a particular province may have multiple locations within it while another province has no locations. Each location may have zero or more items such as accidents, LandsLand, Activities, Educations, QMs, or victims associated with them. These accidents, LandsLand, Activities, Educations, QMs, or victims are added to the IMSMA database via data entry forms.
IMSMA items may have either a direct or a linked relationship to other items. Direct relationships occur when one item requires the other item to exist. For example, an accident, Land, Activity, Education, QM, or victim has a direct relationship to the location to which it is associated. The accident, Land, Activity, Education, QM, or victim cannot exist unless it is associated with a location. This direct relationship is enforced in IMSMA via the reconciliation process. Direct relationships also exist when subsets of data are contained within an item. For example, an Education may have Education details such as the Education type, total audience, and percentage of women and men. The Education details data requires the Education to exist. Table 15. Direct relationships between items lists the items and the data subsets that depend on them.
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 15. Direct relationships between items'''
|-
| width="100pt" | '''Parent item'''
</center>
Linked relationships are optional relationships which may exist between items. Accidents, LandsLand, Activities, Educations, QMs, and victims may be related to one another via links. For example, a victim may be associated to an accident in a particular Land. If these relationships are known, IMSMA users may define these links while reconciling the data entry form.
===Guids===__NOEDITSECTION__
All records in IMSMA have a guid. A guid is a unique value that identifies the record in the IMSMA database. Because the guid is lengthy and comprised of alphanumeric characters, it is typically not a useful value to display in a report. However, the guid is necessary in determining which item records have a direct relationship, and in determining what links exists between item records.
All accidents, LandsLand, Activities, Educations, QMs, and victims are associated with a single location. The information about the location to which an item record is associated is stored in the location_guid field of the item table and corresponds to the location_guid of the location to which it is associated ([[:Image:fig57iR_Appndx.png|Figure 57]]).
[[Image:fig57iR_Appndx.png|center|500px|''Figure 57. location_guid'']]
<div align="center">
''Figure 57. location_guid''
The location_guid field in the item table contains the guid of the location to which the item record is associated. [[:Image:fig58iR_Appndx.png|Figure 58]] shows an example of a location and the accident and Land that are associated to the location. Notice that the location_guid value (1234-1234) in the accident and Land are identical to the location_guid of the location.
[[Image:fig58iR_Appndx.png|center|500px|''Figure 58. location_guid example'']]
<div align="center">
''Figure 58. location_guid example''
When you create a report on a location and its associated items, you will need to use location.guid = "$P{'''LocationParamName'''}" in the query of the sub-report where '''LocationParamName''' is the name of the parameter that you created for the location ([[:Image:fig59iR_Appndx.png|Figure 59]]).
[[Image:fig59iR_Appndx.png|center|500px|''Figure 59. Sub-report query for location and associated items'']]
<div align="center">
''Figure 59. Sub-report query for location and associated items''
IMSMA allows users to define relationships between item records of differing types. For example, an accident may be related to a particular Land. These relationships are referred to as links. The link table contains the links that have been defined between item records. The link table contains the guid of the item from which the link was established (from_guid) and the guid to which the link is being established (to_guid). [[:Image:fig60iR_Appndx.png|Figure 60]] shows an example of a link that was created from an accident to a Land. These links are stored in the link table.
[[Image:fig60iR_Appndx.png|center|500px|''Figure 60. Link table example'']]
<div align="center">
''Figure 60. Link table example''
When you create a report that includes linked items, you will need to use links.toGuid = "$P{'''PrimaryParamName'''} in the query of the sub-report where '''PrimaryParamName''' is the name of the parameter that you created for the primary report item ([[:Image:fig61iR_Appndx.png|Figure 61]]).
[[Image:fig61iR_Appndx.png|center|500px|''Figure 61. Sub-report query for linked items'']]
<div align="center">
''Figure 61. Sub-report query for linked items''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 16. Land fields'''
|-
| width="250pt" | '''Field name'''
| Time to Travel to Level 4 ||
|-
| Total Land Area Size || A derived field that returns the total area size of all Lands Land that are linked to the Activity.
|-
| Travel Time to Medivac ||
| Lat/Long ||
|-
| Linked Land IDs || A derived field that returns a comma separated list of the local IDs of all Lands Land that are part of the location.
|-
| Location Description ||
| Nearest Medical Facility ||
|-
| Total Land Area Size || A derived field that returns the total area size of all Lands Land that are part of the location.
|}
</center>
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 21. Education fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 21. Education fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 23. Organisation fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 24. Place fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 25.QA fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 26.Question fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 27.Received Education fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 29.Vegetation fields'''
|-
| width="250pt" | '''Field name'''
{| class="wikitable" width="500"
|-
| align="center" colspan="2" | '''Table 30. Location fields'''
|-
| width="250pt" | '''Field name'''