Changes

Jump to: navigation, search

Standardising Data Analysis and Information Reporting

1,257 bytes removed, 21:12, 19 February 2013
no edit summary
| align="left" | Navigating data in IMSMA<sup>NG</sup>
General summaries of pre-provided data
| align="left" | *Lists and summary reports of single items
*Simple cross tabs
*Monthly progress reports for internal consumption
*Any report where the data is more important than the formatting
| align="left" | *Manipulating data using external tools
*Pivot tables and charts based on one item
| align="left" | *Linking or exporting IMSMANG data for use in external tools
*Building customised reporting tools for IMSMANG data
*Linking data to ArcGIS Desktop, Crystal Reports and other tools
|-
| align="left" | '''Benefits'''
| align="left" | *Fast and easy to use
*Requires little or no training
| align="left" | *Can limit data using searches
*Can be preformatted and available on a network
*Backed up and stored
*Users can simply run these reports as opposed to building them
*Supports charts
| align="left" | *Easiest way to get IMSMANG data into Excel
*Can manipulate data in common applications
| align="left" | *Most powerful and customisable way of accessing data for reports
*Can manipulate data in advanced or custom reporting applications
*Can be linked with external databases
|-
| align="left" | '''Challenges'''
| align="left" | *Reports are simplistic
*Limited to printing and reports provided with the software. No customisation.
| align="left" | *Limited customisation of resulting data (formats, conditional display, etc.)
*Not ideal for incorporating multiple reports together within a larger report
| align="left" | *Limited customisation of resulting data (formats, conditional display, etc.)
*Not ideal for incorporating multiple reports together within a larger report
| align="left" | *Requires expert level understanding of SQL
|}
</center>
 
Basic iReport Data export External reporting tools
Description Includes printing field reports, current views and maps Includes building iReport templates for more sophisticated reporting as well as exporting data for use in external tools such as Microsoft Excel
Includes exporting data to CSV format for use in Excel as well as cutting and pasting from tables. The most complicated kind of reporting where users connect to backend databases using SQL, Crystal Reports, ArcGIS Desktop, etc., to perform queries and generate reports
 
Uses
 
 Navigating data in IMSMANG
 General summaries of pre-provided data
 Lists and summary reports of single items
 Simple cross tabs
 Monthly progress reports for internal consumption
 Any report where the data is more important than the formatting
 Manipulating data using external tools
 Pivot tables and charts based on one item
 Linking or exporting IMSMANG data for use in external tools
 Building customised reporting tools for IMSMANG data
 Linking data to ArcGIS Desktop, Crystal Reports and other tools
 
 
Benefits  Fast and easy to use
 Requires little or no training
 
 
 Can limit data using searches
 Can be preformatted and available on a network
 Backed up and stored
 Users can simply run these reports as opposed to building them
 Supports charts
 Easiest way to get IMSMANG data into Excel
 Can manipulate data in common applications  Most powerful and customisable way of accessing data for reports
 Can manipulate data in advanced or custom reporting applications
 Can be linked with external databases
Challenges  Reports are simplistic
 Limited to printing and reports provided with the software. No customisation.
 
 Limited customisation of resulting data (formats, conditional display, etc.)
 Not ideal for incorporating multiple reports together within a larger report
 Only works with one item at a time
 Process is conducted outside of IMSMANG and so not controlled  Requires expert level understanding of SQL
==Basic Reporting==
IMSMANG also includes a Map Layout manager that allows users to define map layouts and print high-quality maps with IMSMANG data. Information managers can define map layout templates that include scale bars, annotations and legends or use more sophisticated tools like ArcGIS Desktop to prepare more complicated map layouts for displaying IMSMANG data.
[[Image:AdminGuide_ExampleMapLayoutTemplate.png|center|500px|''Example of a Map Layout Template'']]Figure 25. <div align="center">''Example of a Map Layout Template''</div>
{{note|
===iReports===
 
With the iReport tool, information managers have access to an entire suite of report generation functions. iReport provides the ability to design report templates from the desired data elements; add page layout and formatting information including images, colours and text; and import the reports into IMSMANG for data entry personnel to run. Information managers can also design complex reports to summarize data using sum, count, average, subreports and other statistical reporting functions similar to packages such as Crystal Reports. Being fully integrated into IMSMANG, iReport can be translated into any language supported by the system. Using this approach, only information managers are presented with the complexity of designing reports while traditional users simply have to select a report (and any preceding search) and run it.
Typical uses for iReport include producing reports commonly required by multiple users within a programme. These reports can include:
*clearance: monthly progress reporting*MRE: number of people trained by type of training*hazard: sum of hazardous area by province or type of hazard*accidents: number of accidents by type or by province*data quality: number and list of hazards with incorrect status
Because iReport templates are initiated with a search, they provide a scalable reporting solution that allows one template to be developed for many reports. For example, a report template that shows number of hazards and size of hazards by province can produce different reports depending on the search parameters.
[[Image:AdminGuide_ReportUsingNoSearchParameters.png|center|500px|''Report Example Using No Search Parameters'']]Figure 26. <div align="center">''Report Example Using No Search Parameters''</div>  
In the first example, no search parameter is applied and all data in IMSMANG is used in the report. But by adding a search parameter, for example, limiting this to hazards whose status is active, a different report is generated.
[[Image:AdminGuide_ReportUsingSearchParameters.png|center|500px|''Report Example Using a Search Parameter'']]Figure 27. <div align="center">''Report Example Using a Search Parameter''</div>  
Moreover, if the hazards are further limited to hazards that are minefields (excluding UXO and battle areas), another report is generated, all using the same template. In this way, information managers can build templates and searches to fulfil multiple reporting needs.
}}
===Data Export===
 
IMSMANG also provides data export functionality designed to allow users to export data to external tools such as Microsoft Excel for additional reporting and analysis. This lets users take advantage of functionality in these tools such as sums, counts, charts, pivot tables and other data manipulation functions to format and present data. Users access this functionality by performing a search in IMSMANG and then exporting the results to .CSV format. Users can choose which columns to export, and the data can be manipulated in any external tool that supports .CSV.
The process for connecting external reporting tools is essentially the same for all tools. External tools connect to the IMSMANG relational database via an ODBC connection. Information managers establish this connection by installing the ODBC driver for MySQL. When this is complete, information managers can connect any ODBC-compliant tool to the IMSMANG database, including reporting tools, other database packages and SQL management tools. Examples include:
Reporting tools Database packages and SQL management tools* Crystal Reports* ArcGIS Desktop* iReport* Microsoft Excel Database packages * Microsoft Access* OpenOffice Base* Microsoft SQL Server* OracleSQL management tools* MySQL Query Browser* Navicat* TOAD SQL* Heidi SQL
When connecting an external reporting tool to IMSMANG, it is recommended that information managers build database views within the database to do any necessary data transformations. While it is possible to directly import or connect IMSMANG database tables in external tools and perform transformations within the external tools, the recommended method is to do transformations within the IMSMANG database using database views and then import the resulting views into the external tools.
Using database views, information managers can perform statistical and other operations on the IMSMANG set for reporting purposes including sum, count and average or more complicated functions available in SQL. These operations can be combined with search criteria to provide a highly precise mechanism for providing data to reports. For example, information managers can create a view that returns the name of each clearance and a sum of the hours worked, AP mines found and area cleared on all progress reports linked to each clearance.
 
 
Clearance ID Area cleared AP mines found Hours worked Number of progress reports
CL-1022 23,400 45 120 4
CL-1239 22,330 42 160 6
CL-2345 1,920 4 20 1
<center>
{| class="wikitable" width="600"
|-
| align="left" | '''Clearance ID'''
| align="left" | '''Area cleared'''
| align="left" | '''AP mines found'''
| align="left" | '''Hours worked'''
| align="left" | '''Number of progress reports'''
|-
| align="left" | CL-1022
| align="left" | 23,400
| align="left" | 45
| align="left" | 120
| align="left" | 4
|-
| align="left" | CL-1239
| align="left" | 22,330
| align="left" | 42
| align="left" | 160
| align="left" | 6
|-
| align="left" | CL-2345
| align="left" | 1,920
| align="left" | 4
| align="left" | 20
| align="left" | 1
|}
</center>
This view could then be pasted into Excel, linked with additional IMSMANG data or external data or linked with a map to provide additional analysis. As such, database views provide a powerful way of formatting and analysing IMSMANG data.
{{note|
* Database views created in IMSMANG are backed up by the IMSMANG backup functionality. However, it is important to correctly set the database permissions on views or it will cause problems when restoring the databases.
* Information managers should maintain separate files containing the view creation scripts so that they can be quickly and easily restored or modified. Using the CREATE OR UPDATE VIEW syntax from SQL is an easy way to build scripts for creating or updating views if they already exist}}   {{HowTo's}}
0
edits

Navigation menu