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">''Figure 41. Sample report - Article 7 form A''</div>}

==iReport Basics==Table 6__NOEDITSECTION__iReport uses standard reporting terms to refer to the basic building blocks of report templates.===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;"|+Available Data Sources

| File name Accident Device || Article 7 Form A.jrxmlMRE

| Data sourceAccident || Hazard reductionMRE Detail

| Variables Assistance Classification || Sum of hazard reduction area sizeSum of total hazard area sizeSum of victim countsNeeds Assessment Classification

| Derived fields Cause Classification || HazreducLinkedHazardAreaSize (Total Hazard Area Size)HazreducLinkedVictimCount (Victim Count)Ordnance

| Sub-reportsField Report || 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"Organisation

| File nameGazetteer || Article 7 Form C.jrxmlPlace

| Data sourceGeopoint || HazardQM

| VariablesGeospatialinfo || REPORT_COUNT (built-in iReport variable)Question

| Derived fieldsHazard || NoneReceived MRE

| Sub-reportsHazard Device || 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"Task

| File nameHazard Reduction || Bar Chart Sample.jrxmlVictim

| Data sourceHazard Reduction Device || HazardVictim Assistance

| VariableImpact Survey || Sum of area sizeCount of metal contamination levelVictim Assistance Assistance

| Derived fieldsInterviewee || NoneVictim Cause

| Sub-reportsLink || 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"|-| File Name|| Clearance by Year and District Sample.jrxml|-| Data source|| Hazard reduction|-| Variables|| Count variables for all the derived fieldsVictim Needs Assessment

| Derived fieldsLocation || 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.Work Item

==MRE Audience Totals by Age==The MRE Audience Totals by Age report lists the different age categories of MRE audiences iReport datasource management and selection window can be found just below the total number of male, female, and unknown gender menu bar 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 leveliReport Designer.  [[Image:Pie ChartIReport Datasources Window.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 modelDatasource selection window'']]

''Figure 56. Conceptual database modeliReport Datasource Selection Window''

Within each country structure ===Fields===__NOEDITSECTION__ Fields in iReport refer to individual IMSMA data elements that are zero or more locations. For example, available from a particular province may have multiple locations within it while another province has no locationsdata source. 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 Fields are added to denoted in iReport using the IMSMA database via field reportsfollowing syntax '''''$F{fieldname}''''' (e.g. '''''$F{guid}'''''). Each data source contains a list of available fields. ===Variables===__NOEDITSECTION__ IMSMA items may have either a direct or a linked relationship to other items. Direct relationships occur when one item requires Variables in iReport are created within the other item iReport template to exist. For example, an accident, hazard, hazard reduction, MRE, QC, manipulate or victim has a direct relationship to the location to which it is associatedcalculate data. The accidentUsing variables, hazardusers can create calculations such as sums, hazard reductioncounts, MRE, QCaverages, or victim cannot exist unless it is associated with a locationother totals. This direct relationship is enforced Variables are denoted in IMSMA via iReport using the reconciliation processfollowing syntax '''''$V{variablename}''''' (e. Direct relationships also exist when subsets of g. '''''$V{SumAreaSize}'''''). Variables can use field and/or parameter data .===Parameters===__NOEDITSECTION__ Parameters in iReport are contained within an item. For exampleused to accept and transfer external information, an MRE may have MRE details such as the MRE type, total audience, and percentage of women and meninformation from another report. The MRE details data requires Parameters are denoted in iReport using the MRE to existfollowing syntax '''''$P{parametername}''''' (e. Table 15g. Direct relationships between items lists '''''$P{ParentGuid}''''')===Bands===__NOEDITSECTION__ Bands are used in iReport to specify areas on the items and the data subsets that depend on themresulting report. Each band acts differently in a report.  <center>The most used bands in iReport are:{| class="wikitable" widthstyle="500margin: 1em auto 1em auto;"

| width="100pt" Title | '''Parent item'''| align="center" width="400pt" | '''Child item(s) which require Displayed once at the beginning of the parent item'''report

| Hazard reduction Column or Group Header || Impact surveyIntervieweeOrganisationQuestionSampleSectorVegetation removalDisplayed at the top of each page or section

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

| MRE Summary || MRE details|-| Victim || Received MREDisplayed once at the end of the report. Useful for charts, crosstabs, and totals.

Linked relationships ===Groups===__NOEDITSECTION__ Groups in iReport are optional relationships which may exist between itemsused to display records with one or more common values together on a report. AccidentsFor example, hazards, hazard reductions, MREs, QCs, and victims may Land with the same value for "Province" could be grouped together in a report. Groups can be related added in the iReport Wizard or after a report has been created.===Subreports===__NOEDITSECTION__ Subreports are used in iReport to include more than one another via linksdata source in a report. For example, to include information about Activities performed on a victim may be associated to particular Land, you would include an accident Activity subreport in a particular hazardthe Land report. If these relationships ===Crosstabs, Charts, and Formatting Elements===__NOEDITSECTION__ In addition to the iReport elements addressed above, additional specialized iReport elements are knownavailable to include in iReport templates including Crosstabs, Charts, and additional formatting elements such as lines, rectangles, IMSMA users may define these links etc. Crosstabs and chart elements typically belong only in the Summary band of a report while reconciling formatting elements including images can be included anywhere within the field reporttemplate.

===Guids==={{Note | 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. Howeverfield, the guid is necessary in determining which item records have a direct relationshipvariable, and parameter references in determining what links exists between item records. {{IMSMANG}} are case-sensitive}}

All accidents, hazards, hazard reductions, MREs, QCs, {{NavBox HowTo Standardizing Data Analysis 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''</div> 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 hazard that are associated to the location. Notice that the location_guid value (1234-1234) in the accident and hazard 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''</div> When you create a report on a location and its associated items, you will need to use location.guid = "$P{'''LocationParamName'''Information Reporting}" 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''</div> IMSMA allows users to define relationships between item records of differing types. For example, an accident may be related to a particular hazard. 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 hazard. 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''</div> 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]]). [[ImageCategory:fig61iR_Appndx.png|center|500px|''Figure 61. Sub-report query for linked items''NAA]]<div align="center">''Figure 61. Sub-report query for linked items''</div> ==Appendix B. Data Source Fields==The following sections list the various data sources that are available in iReport and the fields within them.  Need to add derived fields to this list ===Accident===A field for each country structure level will also be available. Because the country structure levels may vary for each site, these fields are not listed below.  <center>{| class="wikitable" width="500"|-| align="center" colspan="2" | '''Accident fields'''|-| width="250pt" | '''Field name'''| align="center" width="250pt" | '''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> ===Hazard===A field for each country structure level will also be available. Because the country structure levels may vary for each site, these fields 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 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|}</center>