Changes

|[[HowTo:Start and Configure i-Report|Start and Configure i-ReportiReport]]|[[HowTo:Create a Basic i-Report iReport Template]]|Create a Basic i-Report [[Modify an iReport Template]]|[[HowTo:Create i-Report Templates with SubreportsFormat an iReport Template]]|[[Create i-Report iReport Templates with Subreports]]|[[HowTo:Summarize i-Report Template Data|Summarize i-Report iReport Template Data]]

==Introductionto iReport==__NOEDITSECTION__===i-Report===iReport Designer (also known as iReport) is a third-party application that allows you to generate custom-defined reports on IMSMA data. Using iReport, you may define the attributes that are returned by a report and also customise the appearance of the report.===How To Use This Manual===This guide provides information for using Report templates designed in iReport with IMSMAcan be imported into {{IMSMANG}} and run by {{IMSMANG}} users to extract data based on search criteria. It provides the steps for configuring Reports can be exported to PDF, RTF, XLS, and using other formats. iReport to report on IMSMA dataDesigner version 5.0. It 1 is not intended to serve as a complete guide for using included with the {{IMSMANG}} distribution. Using iReportDesigner, users create . For detailed information on using jrxml iReporttemplates, a kind of xml report definition, refer that can be used by {{IMSMANG}} to the iReport help or documentation[[Producing Reports Using IMSMANG|produce a formatted report]].

===Conventions===<u>Table 1</u> lists the conventions used in the manual.<center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 1. Conventions'''|-| width="100pt" | '''Convention'''| align="center" width="400pt" | '''Meaning'''|-| ''Bold'' || Indicates menu, button, icon, or list names.|-| ''[Bold in brackets]'' || Indicates a keyboard key.|-| ''Italics'' || Indicates text that should be typed exactly as it is shown in the user manual into a field. Italicized text is also used to {note options that may be selected from a list.|-| [[Image:NoteiReport does not support Java 8.jpg|40px]] || Indicates a tip for using IMSMA.|-| [[Image:Warning.jpg|40px]] || Indicates steps for completing a task.|-| [[Image:MobilePen.png|40px]] || Indicates an error that you might encounter.|}</center> ==Sample Reports==IMSMA includes several iReport sample reports. These reports may be used as is or used as a reference to create your reports. The sample reports are installed in the \iReports\IMSMA reports directory of your IMSMA installation directory. === Article 7: Form A===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 hazards 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'']]<div align="center">=iReport Basics==__NOEDITSECTION__''Figure 41iReport uses standard reporting terms to refer to the basic building blocks of report templates. Sample report - Article 7 form A''</div> ====Table 6=Data Sources===__NOEDITSECTION__Data sources in iReport refer to the connection between the report template and the {{IMSMANG}} database. Each iReport template will have one data source. Data sources in iReport generally refer to items in {{IMSMANG}} such as Land, Activity, Education, Accident, Victim, etc. Available data sources include:{| class="wikitable" style="margin: 1em auto 1em auto;"|-| File name || Article 7 Form A.jrxml+Available Data Sources

| Data sourceAccident Device || Hazard reductionMRE

| Variables Accident || Sum of hazard reduction area sizeSum of total hazard area sizeSum of victim countsMRE Detail

| Derived fields Assistance Classification || HazreducLinkedHazardAreaSize (Total Hazard Area Size)HazreducLinkedVictimCount (Victim Count)Needs Assessment Classification

| Sub-reportsCause Classification || None |} ===Article 7: Form C===The ''Article 7: Form C'' report returns a crosstab by district and hazard with the number of hazards by hazard type. [[Image:Article 7FormC.png|center|500px|''Figure 42. Sample report- Article 7-form C'']]<div align="center">''Figure 42. Sample report – Article 7 form C''</div> ====Table 7===={| class="wikitable"Ordnance

| File nameField Report || Article 7 Form C.jrxmlOrganisation

| Data sourceGazetteer || HazardPlace

| VariablesGeopoint || REPORT_COUNT (built-in iReport variable)QM

| Derived fieldsGeospatialinfo || NoneQuestion

| Sub-reportsHazard || None|} ==Bar Chart Sample==The ''Bar Chart'' sample report returns the metal contamination level of hazards and area size. The report includes a bar chart which summarizes the total area size of hazards by their metal contamination level.  [[Image:BarChartSample.png|center|500px|''Figure 43.'' ''Sample report- Bar chart'' '']] ====Table 8===={| class="wikitable"Received MRE

| File nameHazard Device || Bar Chart Sample.jrxmlTask

| Data sourceHazard Reduction || HazardVictim

| VariableHazard Reduction Device || Sum of area sizeCount of metal contamination levelVictim Assistance

| Derived fieldsImpact Survey || NoneVictim Assistance Assistance

| Sub-reportsInterviewee || None|} ==Clearance by Year and District==The Clearance by Year and District report returns the total area cleared, hours spent, devices, and number of positive samples grouped by year and district.  [[Image:Clearance Operaitons by Year and District.png|center|500px|''Figure 44. Sample report-Clearance by year and district'']] ====Table 9===={| class="wikitable"Victim Cause

| File NameLink || Clearance by Year and District Sample.jrxmlVictim Needs Assessment

| Data sourceLocation || Hazard reduction|-| Variables|| Count variables for all the derived fields|-| Derived fields|| One derived field for each device sub-category (i.e., Anti-Tank, Anti-Vehicle, etc.,) created by using parameterized derived field com.fgm.imsma.ext.report.OrdnanceWithSubCategoryExists, passing in the device subcategory imsma enum.|-| Sub-reports|| None|} ==Hazards by Ordnance Type==The Hazards by Ordnance Type report shows summary data based on the full set of Ordnance Types present. This report groups Hazards based on the full list of Ordnance SubCategories that are found on the Hazard. The report displays the name of the search in the report title. [[Image:MRE audience.png|center|500px|''Figure 45.'' ''Sample report- Hazard by ordnance type'']]Work Item

==MRE Audience Totals by Age==The MRE Audience Totals by Age report lists the different age categories of MRE 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- MRE audience totals by age'']] ====Table 11===={| class="wikitable"|-| File name || MRE Audience by Age.jrxml|-| Data source|| MRE Details|-| Variables|| Sums of each gender (derived fields) by group and reportSum of total audience by group and reportCount of number of events (MRE Details) by group and report|-| Derived Fields|| MREDetailMaleAudience (Total Male Audience)MREDetailFemaleAudience (Total Female Audience)MREDetailUnknownAudience (Total Unknown Audience)|-| Sub-reports|| None|} ==Pie Chart Sample==The Pie Chart sample report returns the metal contamination level of hazards and area size. The report includes a pie chart which summarizes the total area size of hazards by their metal contamination level.  [[Image:Pie Chart.png|center|500px|''Figure 47.'' ''Sample report- Pie chart'']] ====Table 12===={| class="wikitable"|-| File name || Pie Chart Sample.jrxml|-| Data source || Hazard|-| Variables || Sum of area sizeCount of metal contamination level |-| Derived fields || None|-| Sub-reports|| None|} ==Accident Victim Summary Report==The Accident Victim Summary report lists accidents and the victims that are linked to them. In this example, the victim data is linked to the accident and returned via a sub-report. For this type of report, compile the sub-report (Sub-reports\Summary_AccidentVictim_sub-report0.jrxml) before attempting to run the main report. Set the SUB-REPORT_DIR parameter to .\Sub-reports\. [[Image:Accident Victim.png|center|500px|''Figure 48.'' ''Sample report- Accident victim summary'']] ====Table 13===={| class="wikitable"|-| File name|| Summary_AccidentVictim.jrxml|-| Data source|| AccidentQuery executor (used by victim sub-report)|-| Variables|| Sum of area sizeCount of metal contamination level|-| Derived fields|| None|-| Sub-reports|| Sub-reports\Summary_AccidentVictim_sub-report0.jrxml|} ==Hazard Summary Report==File: Summary_Hazard.jrxmlData source: Hazard [[Image:Hazard Summary.png|center|500px|''Figure 49.'' ''Sample report- Hazard summary'']] ===Hazard Reduction Summary Report===File: Summary_Hazreduc.jrxmlData source: Hazard Reduction[[Image:Hazard Reduction.png|center|500px|''Figure 50.'' ''Sample report- Hazard reduction summary'']] ===Location Summary Report===File: Summary_Location.jrxmlData source: Location[[Image:Location Summary.png|center|500px|''Figure 51.'' ''Sample report- Location summary'']] ==MRE Summary Report==For this type of report, compile the sub-report (Sub-reports\Summary_Mre_sub-report1.jrxml) before attempting to run the main report. Set the SUB-REPORT_DIR parameter to .\Sub-reports\.[[Image:MRE Summary.png|center|500px|''Figure 52.'' ''Sample report- MRE summary'']] ====Table 15===={| class="wikitable"|-| File name|| Summary_MRE.jrxml|-| Data source|| MREQuery executor (used by the sub-report)|-| Derived fields|| None|-| Sub-reports|| Sub-reports\Summary_Mre_sub-report1.jrxml|} ===Organisation List Report===File: Summary_Organisation.jrxmlData source: Organisation [[Image:Organisation List Report.png|center|500px|''Figure 53.'' ''Sample report- Organisation list'']] ===Place List Report===File: Summary_Place.jrxmlData source: Place[[Image:Place List Report.png|center|500px|''Figure 54.'' ''Sample report- Place list'']] ===Quality Control Summary Report===File: Summary_QA.jrxmlData source: Qa[[Image:Quality Control Summary Report.png|center|500px|''Figure 55.'' ''Sample report- Quality control summary'']] ==Appendix A: IMSMA Database=====Overview===The IMSMA database contains tables for IMSMA’s base data (country structures, explosive, ordnance, organisations, and places), locations, and the locations’ associated accidents, hazards, hazard reductions, MREs, QCs, 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, hazards, hazard reductions, MREs, QCs, or victims associated with them. These accidents, hazards, hazard reductions, MREs, QCs, or victims are added to the IMSMA database via field reports.  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, hazard, hazard reduction, MRE, QC, or victim has a direct relationship to the location to which it is associated. The accident, hazard, hazard reduction, MRE, QC, 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 MRE may have MRE details such as the MRE type, total audience, and percentage of women and men. The MRE details data requires the MRE to exist. Table 15. Direct relationships between items lists the items and the data subsets that depend on them.  <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 15. Direct relationships between items'''|-| width="100pt" | '''Parent item'''| align="center" width="400pt" | '''Child item(s) which require the parent item'''|-| Hazard reduction || Impact surveyIntervieweeOrganisationQuestionSampleSectorVegetation removal|-| Location || AccidentHazardHazard reductionMREQAVictim |-| MRE || MRE details|-| Victim || Received MRE|}</center> Linked relationships are optional relationships which may exist between items. Accidents, hazards, hazard reductions, MREs, QCs, iReport datasource management and victims may selection window can be related to one another via links. For example, a victim may be associated to an accident in a particular hazard. If these relationships are known, IMSMA users may define these links while reconciling found just below the field report.  ===Guids===All records menu bar 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 recordsiReport Designer.  All accidents, hazards, hazard reductions, MREs, QCs, 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_AppndxIReport Datasources Window.png|center|500px|''Figure 57. location_guidDatasource selection window'']]

''Figure 57. location_guidiReport Datasource Selection Window''

The location_guid field ===Fields===__NOEDITSECTION__ Fields in the item table contains the guid of the location iReport refer to which the item record is associated. [[:Image:fig58iR_Appndx.png|Figure 58]] shows an example of a location and the accident and hazard individual IMSMA data elements that are associated to the locationavailable from a data source. Notice that the location_guid value (1234-1234) Fields are denoted in iReport using the accident and hazard are identical to the location_guid of the location.  [[Image:fig58iR_Appndx.png|center|500px|''Figure 58. location_guid example'following syntax ']]<div align="center">''Figure 58. location_guid example''</div> When you create a report on a location and its associated items, you will need to use location.guid = "$PF{'''LocationParamName'''fieldname}" in the query of the sub-report where '''LocationParamName''' is the name of the parameter that you created for the location ([[:Image:fig59iR_Appndxe.png|Figure 59]])g. [[Image:fig59iR_Appndx.png|center|500px|''Figure 59. Sub-report query for location and associated items'']]<div align="center">'$F{guid}'''Figure 59. Sub-report query for location and associated items''</div> IMSMA allows users to define relationships between item records of differing types). For example, an accident may be related to Each data source contains a particular hazardlist of available fields. These relationships ===Variables===__NOEDITSECTION__ Variables in iReport are referred to as links. The link table contains created within 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 iReport template to which the link is being established (to_guid)manipulate or calculate data. [[:Image:fig60iR_Appndx.png|Figure 60]] shows an example of a link that was created from an accident to a hazardUsing variables, users can create calculations such as sums, counts, averages, or other totals. These links Variables are stored denoted in iReport using the link table. [[Image:fig60iR_Appndx.png|center|500px|''Figure 60. Link table example'following syntax ']]<div align="center">''Figure 60. Link table example''</div> When you create a report that includes linked items, you will need to use links.toGuid = "$PV{'''PrimaryParamName'''variablename} 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_Appndxe.png|Figure 61]])g. [[Image:fig61iR_Appndx.png|center|500px|''Figure 61. Sub-report query for linked items'']]<div align="center">'$V{SumAreaSize}'''Figure 61. Sub-report query for linked items''<). Variables can use field and/div> ==Appendix B. Data Source Fields==The following sections list the various or parameter data sources that are available in iReport and the fields within them.  Need to add derived fields to this list ===AccidentParameters===__NOEDITSECTION__ A field for each country structure level will also be availableParameters in iReport are used to accept and transfer external information, such as information from another report. Because Parameters are denoted in iReport using the country structure levels may vary for each site, these fields are not listed below.  <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | following syntax '''Accident fields''$P{parametername}'|-| width="250pt" | '''Field name' (e.g. ''''| align="center" width="250pt" | '$P{ParentGuid}''Data type'''|-| Accident Description || Text|-| Accident ID || Varchar(50)|-| Area Marked || Varchar(38)|-| Area Officer || Varchar(50)|-| Clearance In Progress? || Varchar(38)|-| Confirmed || Varchar(38)|-| Data Gathered By || Varchar(25)|-| Date of Accident || Datetime|-| Description of ref area |||-| Distance From Nearest Town || Text|-| Distance From City || |-| Equipment Damage || Float|-| Guid || Varchar(38)|-| Inquiry Report Reference || Text|-| Lat/Long || |-| Linked Victim Name(s) || A derived field that returns A comma separated list of the names (first and last) of all victims that are linked to the accident.|-| Location ID || Varchar(38)|-| Mine Action Activity Type || Varchar(38)|-| Municipality || Varchar(125)|-| Number of Linked Victims || A derived field that returns the number of victims that are linked to the accident. |-| Number of Persons Involved || Int(10)|-| Property Damage || Float|-| Reliability of Information || Varchar(38)|-| Reliability of Source || Varchar(38)|-| Source || Varchar(50)|-| Type of Accident || Varchar(38)|-| Type of Area || Varchar(38)|-| Type of Hazardous Area || Varchar(38)|-| Unknown Device || Varchar(38)|-| Was Mine/UXO Marked? || Varchar(38)|}</center> ===HazardBands===__NOEDITSECTION__ A field for each country structure level will also be available. Because the country structure levels may vary for each site, these fields Bands are not listed below.  <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 16. Hazard fields'''|-| width="250pt" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Agricultural Fields Blocked || Varchar(38)|-| Anti-lift Fitted || Varchar(38)|-| Area Size || Float|-| Azimuth || Float |-| Best Route To Hazard || Text|-| Blocked Roads || Varchar(38)|-| Blocked Water Access || Varchar(38)|-| Booby Trapped || Varchar(38)|-| Calculated Size || |-| Clearance Difficulty || Varchar(38)|- | Comments || Text |- | Condition of Mines/UXO || Varchar(38) |-| Confirmed || Varchar(38)|-| Contamination Type |||-| Coordinates Visually Verified |||-| Dev Proj Contact TC |||-| Dev Proj Funded TC |||-| Development Project Planned used in Area || Varchar(38)|-| Device Classification || Varchar(38)|-| Direction from City || |-| Distance From Nearest Town || Float |-| Drainage Features || |-| Estimated Clearance Completion || Varchar(50)|-| Estimated Length || Float|-| Estimated Width || Float |-| Fighting In Area || Varchar(38)|-| Fixed TC |||-| Ground Profile |||- | Guid || Varchar(38)|-| Hazard Description || Text |-| Hazard ID || Varchar(50)|-| Hazard Name || Varchar(125)|-| Identifier || |-| Identifying Person Contact |||-| Identifying Person Name |||-| Information Source || Varchar(38)|-| Infrastructure Blocked || Varchar(38)|-| Intended Land Use || Varchar(38)|-| Intended Land Use Date || Date|-| Lat/Long |||-| Linked Hazard Reduction IDs || A derived field that returns a comma separated list of the local IDs of all hazard reductions that are linked iReport to specify areas on the hazardresulting report.|-| Location ID || Varchar(38)|-| Major Impacts || Text|-| Map Coordinate System TC |||-| Marking Type |||-| Measured From View Point |||-| Medical Facility Level 1 || Text |-| Medical Facility Level 2 || Text |-| Medical Facility Level 3 || Varchar(38)|-| Medical Facility Level 4 || Varchar(38)|-| Medivac || Varchar(38)|-| Metal Contamination Level || Varchar(38)|-| Metal Content Level || Varchar(38) |-| Mine Action Area Type |||-| Municipality |||-| Number Of Affected Communities || Int(10) |-| Ordnance SubCategory List || A derived field that returns "-" separated list of all sub-categories of ordnance that are present Each band acts differently in the hazard.|-| Other Vital Point Text |||-| Planned Clearance Total Area || A derived field that returns the total area size of all clearances that are linked to the hazard. "Clearance" is defined as a Hazard Reduction where the type is set to "Clearance", "Road Clearance" or "Battle Area Clearance"|-| Priority || Varchar(38)|-| Reason for Depth || Text |-| Recommended Clearance Depth || Float|-| Recommended Number Of Demining Teams || Int(10) |-| Reliability of Information || Varchar(38)|-| Reliability of Source || Varchar(38)|-| Road Alternative Text |||-| Road To Other Text |||- | Road Usable For || Varchar(38)|-| Seasonal Consideration || Text|-| Slope || Varchar(38) |-| Soil Type |||-| Status || Varchar(38)|-| Suitable for |||-| Terrain Category || Varchar(38)|-| Terrain/Locale Information || Text |-| Time to Travel to Level 1 || Time|-| Time to Travel to Level 2 || Time |-| Time to Travel to Level 3 || Time |-| Time to Travel to Level 4 || Time |-| Travel Time to Medivac || Time |-| Type of Area || Varchar(38)|-| Type of Blocked Agriculture |||-| Type of Hazardous Area || Varchar(38)|-| Type of Infrastructure Blocked |||-| Type Of Mechanical Device |||-| Type of Non-Agricultural Areas Blocked |||-| Type of Roads Blocked |||-| Type of Water Blocked |||-| Unknown Device |||-| Vegetation |||-| Vegetation Density || Varchar(38)|-| Vegetation Removed By || Varchar(38)|- | Walk Time |||}</center> ===Hazard Reduction===A field for each country structure level will also be availablereport. Because the country structure levels may vary for each site, these fields The most used bands in iReport are not listed below.  <center>:{| class="wikitable" widthstyle="500"|-| align="center" colspan="2" | '''Table 17. Hazard fields'''|-| width="250ptmargin: 1em auto 1em auto;" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Anti Lift |||-| Anti-Lift Fitted |||-| Area Description |||-| Area Officer |||-| Area Officer ||

| Best Route to Site Title ||Displayed once at the beginning of the report

| Booby Trap Column or Group Header ||Displayed at the top of each page or section

| Bobby Trapped Detail ||Displayed once for each data row returned by the report. Most often data elements will exist in this band.

| Comment Summary |||-| Community Leader |||-| Confirmed |||-| Contamination Type |||-| Cost Per Meter |||-| Dangerous Area Type |||-| Depth |||-| Destruction Method |||-| Distance from Nearest Town |||-| Drainage Features |||-| End Date |||-| End Period |||-| Estimated Workday |||-| Fighting in Area |||-| Ground Profile |||-| Guid |||-| Hazard Reduction ID |||-| Hazard Reduction Name |||-| Hours Spent |||-| Intended Land Use |||-| Interviewer |||-| Lat/Long |||-| Length |||-| Location ID |||-| Marking |||-| Marking Method |||-| Medical Facility Level 1 |||-| Medical Facility Level 2 |||-| Medical Facility Level 3 |||-| Medical Facility Level 4 |||-| Medivac |||-| Metal Contamination level |||-| Mines/UXO Condition |||-| Monitor |||-|Municipality |||-| Number Displayed once at the end of Teams |||-| Number of Vehicles |||-| Operational Notes |||-| Ordnance SubCategory Exists || A derived field that returns “true” if the hazard reduction contains ordnance data where the sub-category matches the |-Subcategory propertyreport. Please note that you must specify a sub-category with this field. |-| Organisation || |-| Planned End Date |||-| Planned Start Date || A derived field that returns the number of positive samples Useful for the hazard reduction.|-| Priority Correction |||-| QC Comments |||-| Quality Assurance |||-| Recommendations |||-| Reduction Method |||-| Reliability of Information |||-| Reliability of Source |||-| Reported Progress Area Size || A derived field that returns the total area size of all "Progress Report" field reports that were reconciled to the hazard reduction.|-| Road Usable For |||-| Size of Area |||-| Soil Metal Content Level |||-| Soil Type |||-| SOP Dog |||-| SOP Manual |||-| SOP Mechanical |||-| SOP Metal Detector |||-| Start Date |||-| Start Period |||-| Status |||-| Survey MA Guid |||-| Task Dossier |||-| Tasked By |||-| Team ID |||-| Team Leader |||-| Team Location |||-| Terrain Category |||-| Time to Travel to Level 1 |||-| Time to Travel to Level 2 |||-| Time to Travel to Level 3 |||-| Time to Travel to Level 4 |||-| Total Hazard Area Size || A derived field that returns the total area size of all hazards that are linked to the hazard reduction.|-| Travel Time to Medivac |||-| Type of Activity |||-| Uncleared Area Size |||-| Verification Notes |||-| Victim Count || A derived field that returns the number of victims that are linked to the hazard reduction.|-| Visitor |||-| Year of Reduction || A derived field that returns a string representation of a date formatted by the user provided formatcharts, or "yyyy" if no format is |-provided. The date is the first of the following fields of the hazard reduction that contains data: Start Datecrosstabs, End Date, Planned Start Date, Planned End Date. An optional date format may be specifiedand totals.

===Impact SurveyGroups===__NOEDITSECTION__ <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 18Groups in iReport are used to display records with one or more common values together on a report. Impact survey fields'''|-| width=For example, Land with the same value for "250ptProvince" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Accident Cause |||-| Accident could be grouped together in Area |||-| Casualty Type |||-| Economic Base |||-| Enumerator 1 |||-| Enumerator 2 |||-| Expert Type |||-| Fuel Available |||-| Guid |||-| Higher Education |||-| Higher Education Comments |||-| Last Conflict Year |||-| Local Clearance Effects |||-| Local Clearance Effort |||-| Major Mine Impacts |||-| Medical Facility Type |||-| Military Activity Intensity |||-| Mine History Comments |||-| MRE Community Centre |||-| MRE Organization Involved |||-| MRE Other |||-| MRE Performing Group |||-| MRE Posters |||-| MRE Radio |||-| MRE Religious Centre |||-| MRE School Presentation |||-| MRE Victim Assistance |||-| MRE within 24 Months |||-| Number of Households Census |||-| Number of Households Census Pre-War |||-| Number of Households Key Informants |||-| Number of Households Key Informants Pre-War |||-| Number of Primary Schools |||-| Number of Secondary Schools |||-| Number of Victims Injured – Old |||-| Number of Victims Killed – Old |||-| Origin of Impact Survey Report |||-| Piped Water Supply |||-| Population Census |||-| Population Census Pre-War |||-| Primary Interview Language |||-| Priority |||-| Recent Marking Survey |||-| Recent Mine Clearance |||-| Settlement Established |||-| Telephone Connection |||-| Year Mines Last Planted |||-| Year Mines Problem Began |||}</center> ===Interviewee===<center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 19a report. Interviewee fields'''|-| width="250pt" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Age |||-| Family Name |||-| From Date of Service |||-| Gender |||-| Given Name |||-| Guid |||-| Interviewee Type |||-| Length of Service |||-| Location of Service |||-| Mine Victim |||-| Movement Member |||-| Position Rank |||-| Time Groups can be added in Area |||-| To Date of Service |||-| Vocation Type |||}</center>the iReport Wizard or after a report has been created.===LocationSubreports===__NOEDITSECTION__ A field for each country structure level will also be availableSubreports are used in iReport to include more than one data source in a report. Because For example, to include information about Activities performed on a particular Land, you would include an Activity subreport in the country structure levels may vary for each site, these fields are not listed belowLand report. <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 20. Location fields'''|-| widthCrosstabs, Charts, and Formatting Elements="250pt" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Country Structure |||-| Evacuation Route(s) |||-| Guid |||-| Lat/Long ||__NOEDITSECTION__ |-| Linked Hazard IDs || A derived field that returns a comma separated list of In addition to the local IDs of all hazards that iReport elements addressed above, additional specialized iReport elements are part of the locationavailable to include in iReport templates including Crosstabs, Charts, and additional formatting elements such as lines, rectangles, etc.|-| Location Description ||| Location ID ||| Nearest Medical Facility || | Total Hazard Area Size || A derived field that returns Crosstabs and chart elements typically belong only in the total area size of all hazards that are part Summary band of a report while formatting elements including images can be included anywhere within the locationreport template.|}</center>

===MRE===A {{Note | All field for each country structure level will also be available. Because the country structure levels may vary for each site, these fields variable, and parameter references in {{IMSMANG}} are not listed below. <center>{| class="wikitable" width="500"|case-| align="center" colspan="2" | '''Table 21. MRE fields'''|-| width="250pt" | '''Field name'''| align="center" width="250pt" | '''Data type'''|-| Campaign Level|-| Comments |||-| Confirmed |||-| Date |||-| End Date |||-| Guid |||-| Lat/Long |||-| Location ID |||-| Mine Action Type |||-| MRE ID |||-| Municipality |||-| Organisation |||-| Period |||-| Planned End Date |||-| Planned Start Date |||-| Project |||-| Qty |||-| Reason |||-| Reliability of Information |||-| Reliability of Source |||-| Start Date |||-| Status |||-| Supported Activity Type |||sensitive}}</center>

===MRE Details===<center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Table 21. MRE fields'''|-| width="250pt" | '''Field name'''| align="center" width="250pt" | '''{NavBox HowTo Standardizing Data type'''|-| Campaign Level |||-| Comments |||-| Confirmed |||-| Date |||-| District |||-| End Date |||-| Guid |||-| Lat/Long |||-| Mine Action Type |||-| MRE ID |||-| Municipality |||-| Organisation |||-| Period |||-| Planned End Date |||-| Planned Start Date |||-| Project |||-| Qty |||-| Reason |||-| Reliability of Analysis and Information |||-| Reliability of Source |||-| Start Date |||-| Status |||-| Supported Activity Type |||Reporting}}</center>[[Category:VIE]]