Changes

{| class="wikitable" width="500"

|-

|-

| width="100pt" | '''Convention'''

=== Article 7: Form A===__NOEDITSECTION__

[[Image:fig41SampleReport.png|center|500px|''Figure 41. Sample report - Article 7 form A'']]

===Article 7: Form C===__NOEDITSECTION__

[[Image:Article 7FormC.png|center|500px|''Figure 42. Sample report- Article 7-form C'']]

==Bar Chart Sample==__NOEDITSECTION__

[[Image:BarChartSample.png|center|500px|''Figure 43.'' ''Sample report- Bar chart'' '']]

|}

[[Image:MRE audience.png|center|500px|''Figure 45.'' ''Sample report- Land by ordnance type'']]

{| class="wikitable"

|-

|-

| Data source|| Land

|-

| Variables

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.

====Table 11====__NOEDITSECTION__

==Pie Chart Sample==__NOEDITSECTION__

====Table 12====__NOEDITSECTION__

Set the SUB-REPORT_DIR parameter to .\Sub-reports\.

====Table 13====__NOEDITSECTION__

Data source: Land

===Activity Summary Report===__NOEDITSECTION__

File: Summary_Hazreduc.jrxml

Data source: Activity

===Location Summary Report===__NOEDITSECTION__

File: Summary_Location.jrxml

Data source: Location

==Education Summary Report==__NOEDITSECTION__

Set the SUB-REPORT_DIR parameter to .\Sub-reports\.

====Table 15====__NOEDITSECTION__

Data source: Organisation

===Place List Report===__NOEDITSECTION__

File: Summary_Place.jrxml

Data source: Place

===Quality Control Summary Report===__NOEDITSECTION__

File: Summary_QA.jrxml

Data source: Qa

==Appendix A: IMSMA Database==__NOEDITSECTION__

===Overview===__NOEDITSECTION__

<div align="center">

''Figure 56. Conceptual database model''

</div>

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"

|-

|-

| width="100pt" | '''Parent item'''

</center>

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

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

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

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

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

<div align="center">

''Figure 61. Sub-report query for linked items''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

| Time to Travel to Level 4 ||

|-

|-

| Travel Time to Medivac ||

| Lat/Long ||

|-

|-

| Location Description ||

| Nearest Medical Facility ||

|-

|}

</center>

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''

{| class="wikitable" width="500"

|-

|-

| width="250pt" | '''Field name'''