http://mwiki.gichd.org:8090/mediawiki/api.php?action=feedcontributions&user=Alnaucler&feedformat=atomIMSMA Wiki - User contributions [en]2024-03-29T14:40:58ZUser contributionsMediaWiki 1.28.0http://mwiki.gichd.org:8090/mediawiki/index.php?title=Update_the_Localisation_Files&diff=24498Update the Localisation Files2021-08-18T18:07:23Z<p>Alnaucler: </p>
<hr />
<div>{{Warning | The two original files IMessage.properties and ITerms.properties should '''not''' be edited. If you would like to '''change the English''' terms and messages then you have to create an '''English copy''' of the files. Be very careful with Search and Replace function while editing the files. The KEY names (value on the left of the '''<nowiki>=</nowiki>''' sign) should '''not''' be replaced.}}<br />
<br />
{{Note | To modify the localisation files, you '''should''' use Rosetta-J. Contact your [[Information Management Team | GICHD IM advisor]] who will provide guidance. You may download Rosetta-J from this '''[http://mwiki.gichd.org/mediawiki/images/0/00/Rosetta_J.zip link]'''.}}<br />
<br />
The three files that are used for localisation need to be created for each new language. Each language has a unique language code. IMSMA is using the Window's codes. See which code should be used in the Data Inventory Manager.<br />
<br />
# In the '''Customisation''' menu &rarr; '''Data Inventory Manager'''.<br />
# Click on the Translate button in the Data Category pane of the Data Inventory Manager window.<br />
# Find the desired language in the Language list and note the code e.g. km for Khmer.<br />
<br />
{{Note| If you are running {{IMSMANG}} in a client/server installation and modify the properties files, you will need to copy of IMessage and ITerms files to the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder of each client computer. }}<br />
<br />
==IMessages.properties==__NOEDITSECTION__<br />
The IMessage.properties file contains the error messages and warning messages used by {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder. <br />
# Copy the existing IMessage.properties to e.g. IMessage_km.properties or IMessage_en.properties for English.<br />
# Edit the IMessage.properties copy with Rosetta-J.<br />
<br />
==ITerms.properties==__NOEDITSECTION__<br />
The ITerms.Properties file contains terms used in menus, tooltips and field names in {{IMSMANG}}. The file is located in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder.<br />
# Copy the existing ITerms.properties to e.g. ITerms_km.properties or ITerms_en.properties for English.<br />
# Edit the ITerms.properties copy with Rosetta-J.<br />
<br />
{{Warning | There are two terms that should '''not''' be translated and affects how dates are written in {{IMSMANG}}, see [[Two Terms Not to be Translated | '''more details here''']].}}<br />
<br />
==trans.properties==__NOEDITSECTION__<br />
The third files contains Data Inventory categories, enumeration values, Custom Defined Fields' labels, etc. <br />
# '''[[Export the Translations|export]]''' the English translations<br />
# rename the file (e.g. trans_km)<br />
# '''update''' the first row in the file to the new language code<br />
# create translations with Rosetta-J<br />
# '''[[Import the Translations|import]]''' the file into the database. <br />
<br />
{{NavBox HowTo Languages and Translations}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Language_and_Translations&diff=24497Language and Translations2021-08-18T18:04:54Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
{{Note | The Data Entry Templates and the Summary Templates will not automatically be translated. }}<br />
<br />
The language used by {{IMSMANG}} is of two types:<br />
# the language that the data is entered in (blue arrow)<br />
# the language that the application use (red arrows).<br />
<br />
{| class="wikitable"<br />
|-<br />
| width="300pt" | [[Image:Language.png|300px]]<br />
| width="300pt" | [[Image:VGA card.png|175px]] [[Image:VGA card2.png|175px]]<br />
|-<br />
| width="500pt" | When the users see ''squares'' instead of expected characters even if the font is installed on the computer e.g. in the Country structure then you need to <br />
# create a new folder called ''fallback'' in ''C:\IMSMAng\java\lib\fonts'' and <br />
# copy the fonts for the data language there.<br />
<br />
<br />
<br />
<br />
| width="500pt" | Other font issues may be caused by high resolution VGA card. If this is the case then you need to:<br />
# go to C:\IMSMAng\trayLauncher folder<br />
# right-click on IMSMA.exe and choose Properties<br />
# on the Compatibility tab check ''Disable display scaling on high DPI settings''<br />
# choose ''System'' in the drop-down list.<br />
|}<br />
<br />
==Application language a.k.a. localisation or translation==__NOEDITSECTION____FORCETOC__<br />
{{HowTo's<br />
|[[Change the Language|How does IMSMA know which language to use?]]<br />
|[[Update the Localisation Files|Update the Localisation Files]]<br />
|[[Export the Translations]]<br />
|[[Import the Translations]]<br />
}}<br />
{{Note| To modify the localisation files, you '''should''' use Rosetta-J. For information on using Rosetta-J, contact your [[Information Management Team | GICHD IM advisor]].}}<br />
<br />
If you would like to run {{IMSMANG}} in a language other than English or '''make changes to the English''' terms and messages, you will need to create three properties files for that language:<br />
* IMessagesXX.properties;<br />
* ITermsXX.properties;<br />
* trans_XX.properties. <br />
<br />
IMessages and ITerms are not imported into the database nor included in the database backup. '''[[Backup and Restore]]''' explains on how to backup the language files which are in the ''C:\IMSMAng\client\resources\com\fgm\imsma\lexicon'' folder. The third file is imported into the database and therefore included in the database backup.<br />
<br />
When the users see ''squares'' instead of expected characters e.g. in menus and labels then something is wrong with the translation files IMessages and ITerms for the language specified in the Regional settings on the user's computer. <br />
{{NavBox IMSMA NG Administration}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Portal:Technical_Notes/FAQ&diff=24496Portal:Technical Notes/FAQ2021-08-18T17:53:19Z<p>Alnaucler: </p>
<hr />
<div>{| style="width:100%"<br />
|- <br />
| width="320"| [[ArcEngine/Java issue]]<br />
| [[Manually create PGSQL service]]<br />
| '''Known issue''' - [[Duplicate Enumvalue]]<br />
|-<br />
| [[Combine several zip files]]<br />
| [[Manually delete IMSMA Remote Entry service]]<br />
| '''Known issue''' - [[Negative Coordinates]]<br />
|-<br />
| [[Create ODBC source]]<br />
| [[Manually delete PGSQL service]]<br />
|<br />
|-<br />
| [[Data Dictionary]]<br />
| [[Ports|Ports]] used by IMSMA <br />
|<br />
|-<br />
<br />
| Difference between MySQL and [[Difference MySQL PostGreSQL| PostgreSQL]]<br />
| Pre-defined [[Saved Searches 6.0 | Saved Searches]]<br />
| <br />
|-<br />
| Delete non-fuctional [[Delete Non-functional Saved Search | Saved Searches]]<br />
| [[Renamed fields]]<br />
| '''Workaround''' - [[Export from ArcGIS to Excel]] (UTF-16)<br />
|-<br />
| [[Empty Reconciliation Tab]]<br />
| [[Shutdown IMSMA Server]]<br />
| '''Workaround''' - [[How to Install ArcEngine 10.1 with Lower or Higher Version of ArcGIS Desktop | How to install ArcEngine with other than ArcGIS 10.1]]<br />
|-<br />
| [[Environment Variables]] used by {{IMSMANG}}<br />
| [[Start-up IMSMA Server]]<br />
| '''Workaround''' - [[Open CSV in Excel]]<br />
|-<br />
| [[Error opening Data Entry Form Template]] <br />
| [[Switch Templates| Switch]] templates<br />
| '''Workaround''' - [[Using non-translated languages]]<br />
|-<br />
| [[Exporting Part of Tree Structure from IMSMANG | Exporting Part of Tree Structure from {{IMSMANG}} ]]<br />
| [[Technical Specification Equipment| Technical specifications]] for PCs and tablets <br />
|<br />
|-<br />
| [[Language and Translations | Font and language ]]problems<br />
| [[Templates do not work in IMSMA Remote Entry | Templates do not work]] in IMSMA Remote Entry<br />
| <br />
|-<br />
| [[Installation ODBC driver | Install ODBC driver]]<br />
| [[Two Terms Not to be Translated]] - Date issues<br />
|<br />
|-<br />
| [[Installation package for IMSMA NG is not working | Installation package '''NG''' ]] is not working<br />
| [[Not Possible to Unapprove | Unapprove does not work]]<br />
|<br />
|-<br />
| [[Installation package for SAG is not working | Installation package '''SAG''' ]] is not working<br />
| [[How to Unblock IMSMA server | Unblock IMSMA server]] <br />
|<br />
|-<br />
| [[IReport does not start | iReport]] does not start<br />
| [[Understanding Configuration Options]]<br />
|<br />
|-<br />
| [[Java automatic update]]<br />
| Which [[Check Version of IMSMA| version]] of {{IMSMANG}} is installed?<br />
|<br />
|-<br />
| [[Java error during installation]]<br />
| [[Windows 8 and Windows 10]]<br />
|<br />
|-<br />
| [[Language Issues | Language issues]]<br />
| [[XML Documentation]]<br />
|<br />
|-<br />
| <br/><br />
|<br />
|<br />
|-<br />
| '''[[Downloads]]''' <br />
| '''[[TeamViewer]]'''<br />
| <br />
|}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Organisations_Uncategorised&diff=24495Organisations Uncategorised2021-07-14T15:56:44Z<p>Alnaucler: </p>
<hr />
<div>{{Note | The Country structure table is called ''organisation'', the entity is called ''Organisation'', the target is called ''Organisation'' and the maXML artifact is [[Organisations Artifact|Organisation]].<br />
The Organisation Competence table is called ''orgaccreditationinfo'' (there is no target) and it is not possible to make CDFs for Organisation Competence.}}<br />
<br />
{|<br />
|- valign="top"<br />
|<br />
[[Image:Uncategorised.png|100px]]<br />
|<br />
{| class="wikitable sortable"<br />
! colspan="5" | organisation<br />
|-<br />
! DIM Label !! Data type !! Database column name !! Enumcategory !! Pojo name<br />
|-<br />
| Contact Name || String || contactname|| || ContactName<br />
|-<br />
| Last Updated Date || Date || dataentrydate|| || DataEntryDate<br />
|-<br />
| Email || String || email || || Email<br />
|-<br />
| Fax Number || String || fax || || Fax<br />
|-<br />
| Country Structure || Country Structure || gazetteer_guid|| || Gazetteer<br />
|-<br />
| Active || Boolean || isactive || || Active<br />
|-<br />
| Mobile Phone Number || String || mobile || || Mobile<br />
|-<br />
| - || String || org_guid|| || Guid<br />
|-<br />
| Organisation ID || String || org_localid|| || LocalId<br />
|-<br />
| Address || String || orgaddress|| || Address<br />
|-<br />
| Category || Single-select || orgcategoryenum_guid || Organisation Category || Category<br />
|-<br />
| Name || String || orgname|| || Name<br />
|-<br />
| ''Inactive''|| String || orgstatus || || Status<br />
|-<br />
| Other || String || other || || Other<br />
|-<br />
| Parent || Parent || parentorg_guid || || ParentOrganisation<br />
|-<br />
| Phone Number || String || phone || || Phone<br />
|-<br />
| Radio || String || radio || || Radio<br />
|-<br />
| Website URL || String || websiteurl|| || WebsiteUrl<br />
|}<br />
|}<br />
<br />
{|<br />
|- valign="top"<br />
|<br />
[[Image:Uncategorised.png|100px]]<br />
|<br />
{| class="wikitable sortable"<br />
! colspan="5" | orgaccreditationinfo<br />
|-<br />
! DIM Label !! Data type !! Database column name !! Enumcategory !! Pojo name<br />
|-<br />
| Accreditation Type || Single-select || accreditationenum_guid|| Accreditation Type || Accreditationtype<br />
|-<br />
| Accreditation Status || Single-select || accreditationstatusenum_guid|| Accreditation Status || Accreditationstatus<br />
|-<br />
| - || Parent || org_guid|| || Organisation<br />
|-<br />
| - || String || orgaccreditationinfo_guid|| || Guid<br />
|}<br />
|}<br />
{{Note | There is an '''inactive''' table called ''contact'' which had a Fkey to ''organisation'' in early versions of {{IMSMANG}}.}} <br />
{{NavBox Data Dictionary}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Country_Structure_Uncategorised&diff=24494Country Structure Uncategorised2021-07-14T15:38:43Z<p>Alnaucler: </p>
<hr />
<div>{{Note | The Country structure table is called ''gazetteer'', the entity is called ''Gazetteer'', the target is called ''Gazetteer'' and the maXML artifact is [[Country Structure Artifact|Gazetteer]].<br />
The Alternative names table is called ''gazetteeralternativenames'' (there is no target for alternative name). The level table is called ''gazetteerlevel'' and the target is called ''Gazetteerlevel''.}}<br />
<br />
{|<br />
|- valign="top"<br />
|<br />
[[Image:Uncategorised.png|100px]]<br />
|<br />
{| class="wikitable sortable"<br />
! colspan="5" | gazetteer<br />
|-<br />
! DIM Label !! Data type !! Database column name !! Enumcategory !! Pojo name<br />
|-<br />
| -||String|| gazetteer_guid||||Guid<br />
|-<br />
| Local ID||String|| gazetteer_localid||||LocalId<br />
|-<br />
| Name||String|| gazetteername||||Name<br />
|-<br />
| Country Structure Level||Level|| gazlevel_guid||||Gazetteerlevel<br />
|-<br />
| -||Numeric|| lowerrightx||||LowerRightX<br />
|-<br />
| -||Numeric|| lowerrighty||||LowerRightY<br />
|-<br />
| Parent||Parent|| parentgazetteer_guid||||ParentGazetteer<br />
|-<br />
| -||Numeric|| upperleftx||||UpperLeftX<br />
|-<br />
| -||Numeric|| upperlefty||||UpperLeftY<br />
|}<br />
|}<br />
{|<br />
|- valign="top"<br />
|<br />
[[Image:Uncategorised.png|100px]]<br />
|<br />
{| class="wikitable sortable"<br />
! colspan="5" | gazetteeralternativenames<br />
|-<br />
! DIM Label !! Data type !! Database column name !! Enumcategory !! Pojo name<br />
|-<br />
| -||String||alternativename||||alternativename<br />
|-<br />
| -||Parent||gazetteer_guid||||gazetteer_guid<br />
|-<br />
| -||String||gazetteeralternativename_guid||||gazetteeralternativename_guid<br />
|-<br />
| -||Integer||sequence_number||||sequence_number<br />
|}<br />
|}<br />
{|<br />
|- valign="top"<br />
|<br />
[[Image:Uncategorised.png|100px]]<br />
|<br />
{| class="wikitable sortable"<br />
! colspan="5" | gazetteerlevel<br />
|-<br />
! DIM Label !! Data type !! Database column name !! Enumcategory !! Pojo name<br />
|-<br />
| -||String||gazlevel_guid||||Guid<br />
|-<br />
| -||String||level||||level<br />
|-<br />
| -||Integer||seqno||||seqNo<br />
|}<br />
|}<br />
<br />
{{Note | There is an '''inactive''' table called ''contact'' which has Fkey to ''gazetteer''. If a Village is referenced from here it cannot delete until table ''contact'' is updated.}} <br />
{{NavBox Data Dictionary}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Change_Element_Display_Properties&diff=24493Change Element Display Properties2021-07-07T18:38:28Z<p>Alnaucler: </p>
<hr />
<div>{{HowTo's<br />
| [[Set a Default Value | Set Default Values]]<br />
| [[Set Required Fields]]<br />
}}<br />
<br />
Fields are added to the form template design pane with default properties such as width and height. You can modify these properties to customise the look of your data entry form template. <br />
<br />
<ol><br />
<li>To open the Component Property Editor either<br />
*Double-click the field that you would like to change.<br />
*Select the field and click the '''Properties''' button. </li><br />
The fields in the Component Property Editor window differ depending on the widget type selected. <br />
<br />
{| class="wikitable" <br />
! Element !! Property Editor !! Read More<br />
|-<br />
| Label / Text Tool<br />
| [[Image:Label property editor.png|300px|]]<br />
|<br />
|-<br />
| Country Structure<br />
| [[Image:CS property editor.png|300px|]]<br />
|<br />
|-<br />
| Date<br />
| [[Image:Date property editor.png|300px|]]<br />
|<br />
|-<br />
| Icon/Image Tool<br />
| [[Image:Icon tool property editor.png|300px|]]<br />
| [[Add an Image to the Data Entry Form Template]]<br />
|-<br />
| ID widget<br />
| [[Image:ID property editor.png|300px|]]<br />
| [[Apply a Local ID Generator]]<br />
|-<br />
| Line Tool<br />
| [[Image:Line tool property editor.png|300px|]]<br />
| [[Add a Line to the Data Entry Form Template]]<br />
|-<br />
| Multiple Select<br />
| [[Image:MS property editor.png|400px|]]<br />
| [[Add values to enumeration list]]<br />
|-<br />
| Number / Text Field <br />
| [[Image:Text property editor.png|400px]]<br />
|<br />
|-<br />
| Organisation<br />
| [[Image:Org property editor.png|300px|]]<br />
|<br />
|-<br />
| Place<br />
| [[Image:Place property editor.png|300px|]]<br />
|<br />
|-<br />
| Single Select<br />
| [[Image:SS property editor.png|400px|]]<br />
| [[Add values to enumeration list]]<br /><br />
[[Change Single Selection Option List]] <br /><br />
[[Change Display Option for Single Select]]<br />
|-<br />
| Text Area<br />
| [[Image:Textarea property editor.png|400px|]]<br />
| {{New_6.0 | In version 6.0 the display choice between Text Field and Text Area for Text field CDFs has been introduced.}}<br />
[[Image:Word wrap.png|321px|left]]<br/><br/><br />
If the scroll bar is still visible after you have changed the CDF to Text Field '''OR'''<br/><br />
you have removed the Word wrap for a system field then drag in the field again.<br/><br />
Minimum field height for text size 12 is 21.<br/><br />
|-<br />
| Table<br />
| [[Image:Table property editor.png|500px|]]<br />
| [[Customise Tables | Change table properties]]<br />
|-<br />
|}<br />
<br />
</ol><br />
<br />
{{NavBox HowTo Data Entry Forms}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Change_Element_Display_Properties&diff=24492Change Element Display Properties2021-07-03T07:23:39Z<p>Alnaucler: </p>
<hr />
<div>{{HowTo's<br />
| [[Set a Default Value | Set Default Values]]<br />
| [[Set Required Fields]]<br />
}}<br />
<br />
Fields are added to the form template design pane with default properties such as width and height. You can modify these properties to customise the look of your data entry form template. <br />
<br />
<ol><br />
<li>To open the Component Property Editor either<br />
*Double-click the field that you would like to change.<br />
*Select the field and click the '''Properties''' button. </li><br />
The fields in the Component Property Editor window differ depending on the widget type selected. <br />
<br />
{| class="wikitable" <br />
! Element !! Property Editor !! Read More<br />
|-<br />
| Label / Text Tool<br />
| [[Image:Label property editor.png|300px|]]<br />
|<br />
|-<br />
| Country Structure<br />
| [[Image:CS property editor.png|300px|]]<br />
|<br />
|-<br />
| Date<br />
| [[Image:Date property editor.png|300px|]]<br />
|<br />
|-<br />
| Icon/Image Tool<br />
| [[Image:Icon tool property editor.png|300px|]]<br />
| [[Add an Image to the Data Entry Form Template]]<br />
|-<br />
| ID widget<br />
| [[Image:ID property editor.png|300px|]]<br />
| [[Apply a Local ID Generator]]<br />
|-<br />
| Line Tool<br />
| [[Image:Line tool property editor.png|300px|]]<br />
| [[Add a Line to the Data Entry Form Template]]<br />
|-<br />
| Multiple Select<br />
| [[Image:MS property editor.png|400px|]]<br />
| [[Add values to enumeration list]]<br />
|-<br />
| Number / Text Field <br />
| [[Image:Text property editor.png|400px]]<br />
|<br />
|-<br />
| Organisation<br />
| [[Image:Org property editor.png|300px|]]<br />
|<br />
|-<br />
| Place<br />
| [[Image:Place property editor.png|300px|]]<br />
|<br />
|-<br />
| Single Select<br />
| [[Image:SS property editor.png|400px|]]<br />
| [[Add values to enumeration list]]<br /><br />
[[Change Single Selection Option List]] <br /><br />
[[Change Display Option for Single Select]]<br />
|-<br />
| Text Area<br />
| [[Image:Textarea property editor.png|400px|]]<br />
| {{New_6.0 | In version 6.0 the display choice between Text Field and Text Area for Text field CDFs has been introduced.}}<br />
[[Image:Word wrap.png|321px|left]]<br/><br/><br />
If the scroll bar is still visible after you have changed the CDF to Text Field '''OR'''<br/><br />
you have removed the Word wrap for a system field then drag in the field again.<br/><br />
|-<br />
| Table<br />
| [[Image:Table property editor.png|500px|]]<br />
| [[Customise Tables | Change table properties]]<br />
|-<br />
|}<br />
<br />
</ol><br />
<br />
{{NavBox HowTo Data Entry Forms}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=File:Word_wrap.png&diff=24491File:Word wrap.png2021-07-03T07:16:54Z<p>Alnaucler: </p>
<hr />
<div></div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Move_Fields_Between_Data_Categories&diff=24490Move Fields Between Data Categories2021-07-02T12:25:03Z<p>Alnaucler: </p>
<hr />
<div>{{Note | The focus have to been on the category you want to move from. If the node/item is selected you cannot select more than one field/CDF.}}<br />
[[Image:DIM enum2.png|600px|center]]<br />
<ol><br />
<li>Display the fields in the right pane by selecting the data category in the left pane.</li> <br />
<li>Select the row(s) associated with the field(s) that you would like to move.</li><br />
<li>Click the [[File:UserManual MoveSelectedItemAttributeIcon.png]] button.</li> <br />
[[Image:Add DIM category2.png|center|390px|''Change Category Window'']]<br />
<div align="center"><br />
''Change Category Window''<br />
</div><br />
<li>To move the field(s) into a new data category, select the ''New Category'' option and enter the name for the new category in the field.</li> <br />
<li>To move the item into an existing data category, select the ''Existing Category'' option and select the category name from the list. </li> <br />
<li>Click the '''OK''' button.</li> <br />
</ol><br />
{{Note | The Source column will be updated and show the new Category for the field that you moved. But you need to refresh the DIM by either:<br />
# select another Category and go back<br />
# reopen the DIM<br />
in order to see the final result. }} <br />
{{NavBox HowTo Data Elements}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Rebuild_sandbox&diff=24489Rebuild sandbox2021-06-13T14:25:14Z<p>Alnaucler: </p>
<hr />
<div>{{Note | Rebuilding the sandbox may take long time. }} <br />
<br />
The layers are rebuild in this order:<br />
# Location<br />
# Accident<br />
# Land<br />
# Activity<br />
# QM<br />
# Victim<br />
# Victim Assistance<br />
# Education<br />
# Country structure<br />
# Place<br />
# Organisation<br />
# Task<br />
<br />
{{NavBox Manage Information}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Template:NavBox_Manage_Information&diff=24488Template:NavBox Manage Information2021-06-13T14:22:55Z<p>Alnaucler: </p>
<hr />
<div>{{Navbox<br />
| name = NavBox Manage Information<br />
| state = {{{state|<includeonly>autocollapse</includeonly><noinclude>uncollapsed</noinclude>}}}<br />
| title = [[Portal:IMSMA NG Administration/Maintenance|Manage Information]]<br />
| liststyle = line-height:1.3em;<br />
| bodyclass = hlist<br />
<br />
| group1 = [[Information Exchange]]<br />
| list1 = [[Information Exchange Models]]&nbsp;· [[Centralised Data Entry]]&nbsp;· [[Setting-up Decentralised Information Exchange|Decentralised Data Entry]]<br />
| group2 = [[Backup and Restore]]<br />
| list2 = [[Backup IMSMA Data]]&nbsp;· [[Scheduling Backup]]&nbsp;· [[Restore IMSMA Backup on Server]]&nbsp;· [[Restore IMSMA Backup on Client]] &nbsp;· [[Rebuild sandbox]]<br />
| group3 = [[Importing and Exporting]]<br />
| list3 = [[Import a Data Entry Form from a xml File]]&nbsp;· [[Search for Exporting Data Entry Form | Export Data Entry Form from Advanced Search]]&nbsp;· [[Export Data Entry Form from Workbench]]&nbsp;· [[Import the Translations]]&nbsp;· [[Export the Translations]]&nbsp;· [[Export Auxiliary Data]]&nbsp;· [[Import XLS data]]<br />
}}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Rebuild_sandbox&diff=24487Rebuild sandbox2021-06-13T14:21:51Z<p>Alnaucler: Created page with "{{Note | Rebuilding the sandbox may take long time. }} The layers are rebuild in this order: # Location # Accident # Land # Activity # QM # Victim # Victim Assistance # EORE..."</p>
<hr />
<div>{{Note | Rebuilding the sandbox may take long time. }} <br />
<br />
The layers are rebuild in this order:<br />
# Location<br />
# Accident<br />
# Land<br />
# Activity<br />
# QM<br />
# Victim<br />
# Victim Assistance<br />
# EORE<br />
# Country structure<br />
# Place<br />
# Organisation<br />
# Task<br />
<br />
{{NavBox Manage Information}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Configuration_Options&diff=24486Understanding Configuration Options2021-06-07T14:37:05Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
__NOEDITSECTION__<br />
To determine the initial configuration of the IMSMA<sup>NG</sup> system, it is important to understand the two ways in which IMSMA<sup>NG</sup> can be set up and the basic architecture of the system. IMSMA<sup>NG</sup> is a client/server software application designed to run in stand-alone or client/server mode. In a stand-alone system, both the IMSMA<sup>NG</sup> client and server are installed on the '''same''' computer. The stand-alone configuration is the simpler type of installation: it requires no additional network equipment or infrastructure and is easy to maintain.<br />
<br />
<br />
{| class="wikitable"<br />
|+ Comparison of Stand-alone and Client/server Configuration Options <br />
! Configuration<br />
! Advantages<br />
! Disadvantages<br />
|-<br />
| <b>Stand-alone</b><br />
|<br />
* Simple to set up and maintain<br />
* Limited IT knowledge required<br />
* Can be upgraded to a client/server configuration later<br />
|<br />
* One-at-a-time data access<br />
|-<br />
| <b>Client/server</b><br />
|<br />
* Multiple concurrent data access<br />
* Redundancy<br />
|<br />
* Complicated to set up and maintain<br />
* Local Area Network infrastructure required<br />
* Multiple computers required<br />
|-<br />
|}<br />
<br />
In a client/server configuration, one computer acts as a server and many other computers can connect to it simultaneously over a network, enabling multiple people to access the same data at the same time. A client/server installation requires at least two computers and a network infrastructure connecting the computers together. Using a client/server installation, a mine action programme can have multiple data entry clerks entering data at the same time.<br />
<br />
<br />
[[Image:Understanding Configuration Options - Networked Config.png|center|300px|''Client/server Config'']]<br />
<div align="center"><br />
''Client/server configuration''<br />
</div><br />
<br />
{{Note| Be aware of the following when running IMSMA in a client/server installation:<br />
* The server and client(s) must be running the exact same version of IMSMA.<br />
* The gisServer.properties file on the server must be configured. <br />
* The client(s) must be configured to connect to the server. <br />
* Maps only need to be installed on the server. <br />
* Data entered into the server or clients will be automatically rendered to all clients (as well as the server). However, geospatial information (points, polygons) will NOT be immediately rendered to all clients. To either post your geospatial updates to the server (thus making them available to other clients) or to receive updates from the server, you must log out of IMSMA and then log back in.<br />
* Fonts will need to be installed on both the server and client(s)<br />
}}<br />
<br />
==Client/server Architecture==__NOEDITSECTION__<br />
<br />
Whether a programme uses a stand-alone installation or a client/server installation, the IMSMA<sup>NG</sup> software has two main components:<br />
<br />
* the IMSMA<sup>NG</sup> server<br />
* the IMSMA<sup>NG</sup> client<br />
<br />
The figure below shows the parts of the software; the following sections then explain the functions that each part performs.<br />
<br />
{| border="1" cellpadding="5"<br />
|- valign="top"<br />
|<br />
[[Image:stand_alone Architecture.png|center|300px|''Stand-alone architecture'']]<br />
<br />
|<br />
[[Image:Understanding Configuration Options- Client Server Architecture.png|center|600px|''Client/server architecture'']]<br />
<br />
|}<br />
<br />
===Server===__NOEDITSECTION__<br />
<br />
The IMSMA<sup>NG</sup> server stores data and manages much of the data processing. The server has two main parts, the datastore and the business layer. The datastore is where data is stored for retrieval by the IMSMA<sup>NG</sup> client. IMSMA<sup>NG</sup> uses a PostgreSQL relational database to store data on the server. Additionally, IMSMA<sup>NG</sup> stores other data including attachments and some configuration files on the server in file format. The PostgreSQL database is accessible via a variety of database access tools designed for browsing relational databases.<br />
<br />
{{warning|While the database contains many relational database constraints designed to preserve data integrity, all updates of data should be handled through the business layer rather than with direct SQL updates in order to maintain integrity. Failure to do so will likely cause data corruption or loss}}<br />
<br />
The business layer is where rules are implemented to ensure data quality and consistency. The business layer takes data from the datastore and transforms it for display in the IMSMA<sup>NG</sup> client. All data interaction between the client and server database is handled through the business layer, which allows for multiple clients to be connected to the database while preserving data integrity in cases of multiple requests. This includes access from the IMSMA<sup>NG</sup> client and from the reporting tool.<br />
<br />
===Client===__NOEDITSECTION__<br />
<br />
The IMSMA<sup>NG</sup> client is the interface through which users can connect to the server and browse the system, enter data and generate outputs. The client includes an integrated GIS component and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS component performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS component also allows each client to load and manage its own maps and geographic data which the client receives from the IMSMA<sup>NG</sup> server. As a result, each client receives and locally stores a complete copy of geographic data from the IMSMA<sup>NG</sup> server when it is connected to the server. This synchronized data is stored in a client ―sandbox‖ separate from the server and can always be updated by connecting to the server.<br />
<br />
JasperSoft’s iReport tool is built into each IMSMA<sup>NG</sup> client and allows users to access data from the database via the business layer. With iReport, users can generate reports containing tabular data, subreports and cross tabs as well as various types of charts and graphs. These reports can easily be localized into any language that IMSMA<sup>NG</sup> supports. Additional reporting options include direct connections to the IMSMA<sup>NG</sup> database via ODBC. This functionality supports tools such as Crystal Reports, Microsoft® Access®, Microsoft Excel® and various open-source reporting tools.<br />
<br />
===Memory settings===__NOEDITSECTION__<br />
<br />
By reserving memory for {{IMSMANG}}, less memory may be used by other applications. It also depends on how much memory the computer has if is possible to reserve more memory for {{IMSMANG}}.<br />
<br />
[[Image:memory_settings.png|500px]]<br />
<br />
If you would like to reserve more memory for the IMSMA server '''process''', edit row 3 in ''C:\IMSMAng\trayLauncher\TrayLauncher.properties''. <br />
<br />
If you would like to reserve more memory for the IMSMA client '''process''', edit row 12 in ''C:\IMSMAng\trayLauncher\TrayLauncher.properties''. Start with increasing it to 1024 and then evaluate. <br />
<br />
{|<br />
|- valign="top"<br />
|<br />
<br />
{| class="wikitable" <br />
! Value !! Meaning <br />
|- align="right"<br />
| 512 || 0.5 GB <br />
|- align="right"<br />
| 1024 || 1 GB <br />
|- align="right"<br />
| 2048 || 2 GB <br />
|- align="right"<br />
| 3072 || 3 GB <br />
|- align="right"<br />
| 4096 || 4 GB <br />
|- align="right"<br />
|}<br />
The values should be increased step-by-step and evaluated after each change.<br />
<br />
{{Note | <br />
* Since IMSMA NG is a 32-bit application there is no effect by reserving more than total 4 GB. <br />
* On the physical server in a client/server configuration there is need to start the client, take backup and restore so do not set the client process memory to less than 512. }}<br />
<br />
{{NavBox Information Management}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Portal:Technical_Notes/FAQ&diff=24485Portal:Technical Notes/FAQ2021-06-07T14:21:45Z<p>Alnaucler: </p>
<hr />
<div>{| style="width:100%"<br />
|- <br />
| width="320"| [[ArcEngine/Java issue]]<br />
| [[Manually create PGSQL service]]<br />
| '''Known issue''' - [[Duplicate Enumvalue]]<br />
|-<br />
| [[Combine several zip files]]<br />
| [[Manually delete IMSMA Remote Entry service]]<br />
| '''Known issue''' - [[Negative Coordinates]]<br />
|-<br />
| [[Create ODBC source]]<br />
| [[Manually delete PGSQL service]]<br />
|<br />
|-<br />
| [[Data Dictionary]]<br />
| [[Ports|Ports]] used by IMSMA <br />
|<br />
|-<br />
<br />
| Difference between MySQL and [[Difference MySQL PostGreSQL| PostgreSQL]]<br />
| Pre-defined [[Saved Searches 6.0 | Saved Searches]]<br />
| <br />
|-<br />
| Delete non-fuctional [[Delete Non-functional Saved Search | Saved Searches]]<br />
| [[Renamed fields]]<br />
| '''Workaround''' - [[Export from ArcGIS to Excel]] (UTF-16)<br />
|-<br />
| [[Empty Reconciliation Tab]]<br />
| [[Shutdown IMSMA Server]]<br />
| '''Workaround''' - [[How to Install ArcEngine 10.1 with Lower or Higher Version of ArcGIS Desktop | How to install ArcEngine with other than ArcGIS 10.1]]<br />
|-<br />
| [[Environment Variables]] used by {{IMSMANG}}<br />
| [[Start-up IMSMA Server]]<br />
| '''Workaround''' - [[Open CSV in Excel]]<br />
|-<br />
| [[Error opening Data Entry Form Template]] <br />
| [[Switch Templates| Switch]] templates<br />
| '''Workaround''' - [[Using non-translated languages]]<br />
|-<br />
| [[Exporting Part of Tree Structure from IMSMANG | Exporting Part of Tree Structure from {{IMSMANG}} ]]<br />
| [[Technical Specification Equipment| Technical specifications]] for PCs and tablets <br />
|<br />
|-<br />
| [[Language and Translations | Font and language ]]problems<br />
| [[Templates do not work in IMSMA Remote Entry | Templates do not work]] in IMSMA Remote Entry<br />
| <br />
|-<br />
| [[Installation ODBC driver | Install ODBC driver]]<br />
| [[Two Terms Not to be Translated]] <br />
|<br />
|-<br />
| [[Installation package for IMSMA NG is not working | Installation package '''NG''' ]] is not working<br />
| [[Not Possible to Unapprove | Unapprove does not work]]<br />
|<br />
|-<br />
| [[Installation package for SAG is not working | Installation package '''SAG''' ]] is not working<br />
| [[How to Unblock IMSMA server | Unblock IMSMA server]] <br />
|<br />
|-<br />
| [[IReport does not start | iReport]] does not start<br />
| [[Understanding Configuration Options]]<br />
|<br />
|-<br />
| [[Java automatic update]]<br />
| Which [[Check Version of IMSMA| version]] of {{IMSMANG}} is installed?<br />
|<br />
|-<br />
| [[Java error during installation]]<br />
| [[Windows 8 and Windows 10]]<br />
|<br />
|-<br />
| [[Language Issues | Language issues]]<br />
| [[XML Documentation]]<br />
|<br />
|-<br />
| <br/><br />
|<br />
|<br />
|-<br />
| '''[[Downloads]]''' <br />
| '''[[TeamViewer]]'''<br />
| <br />
|}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=The_Making_of_IMSMA&diff=24483The Making of IMSMA2021-05-19T08:36:27Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
'''The making of IMSMA''' started in 1998. It was however not until 2004, to satisfy recurrent requests from our IMSMA users in the field, that the development of a fully re-engineered version was started. Compilation of all lessons learnt and users’ feedback were submitted to a tender competition process. The software development contract was eventually won by FGM which today is called [http://www.novetta.com/ Novetta.]<br />
Interoperability, flexibility and user-friendliness were three of the key words that laid down the foundation for the next generation of IMSMA – called IMSMA NG. This entailed moving away from somewhat rigid processes and methods towards a highly flexible and user-friendly information management system that could meet almost all local needs and requirements.<br />
<br />
==IMSMA NG==__NOEDITSECTION__ <br />
IMSMA V4 achieved this goal in 2006. One of the key enhancements was the development and integration of a fully functional GIS component. For this work, the GICHD was honoured by the presentation of the Environmental Systems Research Institute, Inc. ([http://www.esri.com/ ESRI Inc.]), [http://www.esri.com/sag/index.html Special Achievement in GIS (SAG) award] to its IMSMA support team. The award citation reads in part ''“By embracing GIS technology, these organisations have made extraordinary contributions to our global society and set new precedents throughout the GIS community.”''<br />
IMSMA V5 released in 2007 provided another major enhancement by including an [[Using_the_Impact_Scoring_Tool_in_IMSMANG|impact scoring tool]] and the possibility of recording [[Victim Summary Window| victim]]s and [[Accident Summary Window|accident]]s separately. User feedback and lessons learnt are constantly evaluated and compiled by the [http://www.gichd.org/ GICHD]. Furthermore, the GICHD close collaboration with FGM remains crucial to guarantee that we meet our users’ needs and requirements in the field. <br />
<br />
==IMSMA Legacy==__NOEDITSECTION__<br />
[[Glossary|<abbr title="Information Management System for Mine Action">IMSMA</abbr>]] Legacy refers to IMSMA versions V1.x to V3.x.<br />
Support is still being provided to installations that were performed by the GICHD, and which are currently in use.<br />
We strongly encourage all countries using IMSMA Legacy to upgrade to {{IMSMANG}} due to the technical age of the application. It is not recommended to use IMSMA Legacy on other operating systems then Windows XP.<br />
<br />
IMSMA Legacy follows a highly standardised and '''linear''' workflow. The workflow is started by the Impact Survey/Level 1 Survey, which can produce mined area reports. Technical Survey/Level 2 Survey follows, which can produce minefield reports. The minefields are by a clearance which may have associated progress reports. The process is concluded with a Completion report. Other items are Accident, Victims and MRE. Task and Auxiliary data are also supported from V3.x.<br />
===IMSMA V3===__NOEDITSECTION__<br />
IMSMA V3 was released in February 2003 and until November 2004 it was regularly updated. It presented a complete new software architecture and each update contributed substantially with new added functionalities and greater flexibility. A module for MRE and improvements of the Task tracking tool allowed information managers to account for the work accomplished by each organisation. In addition, in IMSMA V3 the database platform was changed to Microsoft SQL Server. This software improved numerous aspects, from data handling being facilitated through the design of database queries, to client/server configuration, with an increased number of simultaneous users.<br />
<br />
===IMSMA V2===__NOEDITSECTION__<br />
When IMSMA V2.2 was released in October 2001 the users expressed that it was “significantly better” than V1 as it provided among other new features, included a module for Tasking and more simultaneous users. This was a first attempt to move from the original repository database into a more operational management tool for the mine action programmes. IMSMA V2.2 was adopted by the UN on an international level as the standard for humanitarian demining information.<br />
<br />
===IMSMA V1===__NOEDITSECTION__<br />
IMSMA V1 was first deployed to the field in Kosovo in 1999. Information management being one focus principle of every mine action programme, the Zurich’s Institute of Technology (ETHZ) had been mandated by the GICHD to develop a standardised software tool to help process and coordinate both data and activities related to mine action. Valuable cooperation from field users resulted in the development of a new version. <br />
<br />
{{NavBox What is IMSMA}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24482Information Management Team2021-05-19T08:36:04Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/contact/contact/steve-hellen// Steve HELLEN] || '''Head, Information Management'''|| - || Albania, Armenia, Benin, Burundi, Congo, Cote d'Ivoire, Cyprus, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Iran, Israel, Kenya, Kosovo, Kuwait, Liberia, Mali, Morocco, Mozambique, Myanmar, Nepal, Oman, Rwanda, Sierra Leone, South Sudan, Spain, Sudan, Uganda and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan, Colombia, Lao People's Democratic Republic, and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Mauritania, Palestine, Tajikistan, Ukraine, Vietnam and Yemen<br />
<!--|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Angola, Pacific and Zimbabwe<br />
--><br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Thailand<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq, Syria, and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]], Capacity Development, IM assessments || Afghanistan, Angola, Chad, Chile, DRC, Libyan Arab Jamahiriya, Pacific, Senegal, Somalia and Zimbabwe<br />
|}<br />
[[Category:KOD]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24481Information Management Team2021-05-19T08:29:38Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/contact/contact/steve-hellen// Steve HELLEN] || '''Head, Information Management'''|| - || Albania, Armenia, Benin, Burundi, Congo, Cote d'Ivoire, Cyprus, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Iran, Israel, Kenya, Kosovo, Kuwait, Liberia, Mali, Morocco, Mozambique, Myanmar, Nepal, Oman, Rwanda, Sierra Leone, South Sudan, Spain, Sudan, Uganda and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan, Colombia, Lao People's Democratic Republic, and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Mauritania, Palestine, Tajikistan, Ukraine, Vietnam and Yemen<br />
<!--|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Angola, Pacific and Zimbabwe<br />
--><br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Thailand<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq, Syria, and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]], Capacity Development, IM assessments || Afghanistan, Angola, Chad, Chile, DRC, Libyan Arab Jamahiriya, Pacific, Senegal, Somalia and Zimbabwe<br />
|}<br />
[[Category:COO]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Standardising_Data_Analysis_and_Information_Reporting&diff=24480Standardising Data Analysis and Information Reporting2021-05-04T11:44:12Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
Two of most important purposes of an information system are:<br />
* ensure high quality of data and<br />
* support operational use of the information.<br />
One important use of the data is reporting. If it not possible in an easy way to create reports/statistics which reflect the data correctly the credibility of the data is lost. That’s why {{IMSMANG}} was designed with a robust reporting and analysis component that supports various reporting options. These options include:<br />
<br />
<center><br />
{| class="wikitable" width="1000"<br />
|-<br />
| align="center" colspan="6" | '''Comparison of {{IMSMANG}} Reporting Options'''<br />
|-<br />
| width="20pt" | <br />
| width="195pt" | '''Basic''' <br />
| width="195pt" | '''iReport'''<br />
| width="195pt" | '''Data export'''<br />
| width="195pt" | '''Other external reporting tool'''<br />
|-<br />
| align="left" | '''Description''' <br />
| align="left" | Includes printing Data Entry Forms, Summary items and maps<br />
| align="left" | Includes building iReport templates for more sophisticated reporting as well as exporting data for use in external tools such as Microsoft Excel<br />
| align="left" | Includes exporting data to CSV format for use in Excel as well as cutting and pasting from tables.<br />
| align="left" | 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<br />
|-<br />
| align="left" | '''Uses''' <br />
| align="left" | <br />
*Navigating data in {{IMSMANG}}<br />
*General summaries of pre-provided data<br />
| align="left" | <br />
*Lists and summary reports of single items<br />
*Simple cross tabs<br />
*Monthly progress reports for internal consumption<br />
*Charts<br />
| align="left" | <br />
*Manipulating data using external tools<br />
*Pivot tables and charts based on one item<br />
| align="left" | <br />
*Linking or exporting {{IMSMANG}} data for use in external tools<br />
*Building customised reporting tools for {{IMSMANG}} data<br />
*Linking data to ArcGIS Desktop, Crystal Reports and other tools<br />
|-<br />
| align="left" | '''Benefits''' <br />
| align="left" | <br />
*Fast and easy to use<br />
*Requires little or no training<br />
| align="left" | <br />
*Can limit data using searches<br />
*Can be preformatted and available on a network<br />
*Backed up and stored<br />
*Users can simply run these reports as opposed to building them<br />
*Supports charts<br />
| align="left" | <br />
*Easiest way to get {{IMSMANG}} data into Excel<br />
*Can manipulate data in common applications<br />
| align="left" | <br />
*Most powerful and customisable way of accessing data for reports<br />
*Can manipulate data in advanced or custom reporting applications<br />
*Can be linked with external databases<br />
|-<br />
| align="left" | '''Challenges''' <br />
| align="left" | <br />
*Reports are simplistic<br />
*Limited to printing and reports provided with the software. No customisation.<br />
| align="left" | <br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Limited customisation of resulting data (formats, conditional display, etc.)<br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Requires expert level understanding of SQL<br />
|}<br />
</center><br />
[[Image:BI in context graph.png|center|700px']]<br />
<br />
<br />
==Basic Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} provides several reporting options that allow users to produce basic reports directly from {{IMSMANG}}. These include printing Data Entry Forms entered into the system, maps from the main navigation window and Summary items. Any of these reports can be sent directly to a printer or to an intermediate format such as rich text format (.RTF) or portable document format (.PDF) for transmitting in electronic format or for further editing.<br />
<br />
{{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.<br />
<br />
[[Image:AdminGuide_ExampleMapLayoutTemplate.png|center|500px|''Example of a Map Layout Template'']]<br />
<div align="center"><br />
''Example of a Map Layout Template''<br />
</div> <br />
<br />
{{note|<br />
* Map layouts can be printed and scaled to any size paper. This is a simple way of producing {{IMSMANG}} maps without needing additional GIS software.<br />
* Map layout templates can be prepared and distributed to individual {{IMSMANG}} clients, allowing information managers to prepare templates based on user preferences or functional needs.<br />
}} <br />
<br />
==Embedded Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} supplements the basic reporting options available to all users with several more sophisticated reporting tools that are embedded within the system. In addition to reporting on individual elements, these embedded tools allow for statistical and aggregate reporting of data within the database. Instead of reporting the contents of a single report, statistical reporting allows information managers to produce reports about multiple items and to use functions such as sum, average and count to summarise data. <br />
<br />
There are two options for embedded reporting: iReports and data export. Both functions rely on {{IMSMANG}} searches to filter data. Using iReports, information managers can build reporting templates to visualise data in a specific and repeatable format. Using data export, managers can export search results to an external tool such as Microsoft Excel and perform aggregation and statistical analysis.<br />
<br />
===iReports===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Use iReport | Use iReport]]<br />
}}<br />
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 summarise 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.<br />
<br />
Typical uses for iReport include producing reports commonly required by multiple users within a programme. These reports can include:<br />
<br />
*clearance: monthly progress reporting<br />
*education: number of people trained by type of training<br />
*land: sum of hazardous area by province or type of land<br />
*accidents: number of accidents by type or by province<br />
*data quality: number and list of land with incorrect status<br />
<br />
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 a list of land with associated ordnance details can produce different reports depending on the search parameters.<br />
<br />
[[Image:AdminGuide_ReportUsingNoSearchParameters.png|center|500px|''Report Example Using No Search Parameters'']]<br />
<div align="center"><br />
''Report Example Using No Search Parameters''<br />
</div> <br />
<br />
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 land whose status is Worked on, a different report is generated. <br />
<br />
[[Image:AdminGuide_ReportUsingSearchParameters.png|center|500px|''Report Example Using a Search Parameter'']]<br />
<div align="center"><br />
''Report Example Using a Search Parameter''<br />
</div> <br />
<br />
Moreover, if the land is further limited to a specific type, another report is generated, using again the same template. This way, information managers can build templates and searches to fulfill multiple reporting needs.<br />
<br />
Reports created with iReport can be printed directly within {{IMSMANG}} or saved to an intermediate format such as .RTF, .PDF or .XLS for electronic transmission or additional editing or inclusion in other reports. iReport supports the inclusion of charts, images and headers and footers, and it acts as a complete reporting package.<br />
<br />
===Data Export===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Exporting| Export data]]<br />
}}<br />
{{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.<br />
<br />
Because data export is initiated with a search, it provides a flexible approach for getting data to an external tool. However, once the data is used in a tool outside of {{IMSMANG}}, it is impossible to control how this data is manipulated which may limit the consistency of reports produced in this way. <br />
<br />
{{note|{{IMSMANG}} searches return information on only one item at a time, and data export is limited to the data returned by the search. Data from linked items (such as victim data linked to accidents) is not available for export.}}<br />
<br />
==External Reporting Tools==__NOEDITSECTION__<br />
{{IMSMANG}} also allows information managers to connect advanced reporting tools such as Crystal Reports or ArcGIS Desktop directly to its relational database for highly advanced report generation. With this capability, information managers can use custom reporting solutions to connect with {{IMSMANG}}, allowing for complete control of {{IMSMANG}} outputs. Or, managers can modify existing reporting solutions to connect to {{IMSMANG}}, which leverages technology already implemented in the programme and limits the need for retraining. <br />
<br />
{{note|When using external reporting tools we recommend to connect to the '''[[IMSMA Staging Area | Staging area]]''' instead of the {{IMSMANG}} database. It does require knowledge about the IMSMA data model. Contact contact your [[Information Management Team | GICHD IM advisor]] if you have questions.}}<br />
<br />
===Connecting other External Reporting Tools===__NOEDITSECTION__<br />
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 PGSQL. 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:<br />
<br />
{| class="wikitable"<br />
! scope="col" | Reporting tools || scope="col" | Database packages || scope="col" | SQL management tools<br />
|-<br />
| Crystal Reports || Microsoft Access || PGSQL Query Browser<br />
|-<br />
| ArcGIS Desktop || OpenOffice Base || Navicat<br />
|-<br />
| iReport || Microsoft SQL Server || TOAD SQL<br />
|-<br />
| Microsoft Excel || Oracle || Heidi SQL<br />
|}<br />
<br />
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.<br />
<br />
{{note|Building database views to transform data before importing it into other tools significantly reduces the performance hit associated with connecting external tools.}}<br />
<br />
===Building Database Views===__NOEDITSECTION__<br />
Building database views is the primary way of transforming data to support external reporting. Information managers can use SQL editing tools to build and save database queries as views that can be used to format data for easier reporting. Using database views, information managers can join data together into flat tables that allow for easier incorporation into reports or other analysis tools. Database views act like database tables and can be imported or queried from external tools. Moreover, views automatically refresh as data is added to {{IMSMANG}} and provide an up-to-date data source for other applications.<br />
<br />
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. <br />
<br />
<center><br />
{| class="wikitable" width="600"<br />
|-<br />
| align="left" | '''Clearance ID'''<br />
| align="left" | '''Area cleared'''<br />
| align="left" | '''AP mines found'''<br />
| align="left" | '''Hours worked'''<br />
| align="left" | '''Number of progress reports'''<br />
|-<br />
| align="left" | CL-1022<br />
| align="left" | 23,400<br />
| align="left" | 45<br />
| align="left" | 120<br />
| align="left" | 4<br />
|-<br />
| align="left" | CL-1239 <br />
| align="left" | 22,330 <br />
| align="left" | 42 <br />
| align="left" | 160 <br />
| align="left" | 6<br />
|-<br />
| align="left" | CL-2345<br />
| align="left" | 1,920<br />
| align="left" | 4<br />
| align="left" | 20<br />
| align="left" | 1<br />
|}<br />
</center><br />
<br />
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.<br />
<br />
{{note|<br />
* 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.<br />
* 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 REPLACE VIEW syntax from SQL is an easy way to build scripts for creating or replacing views if they already exist.<br />
}}<br />
<br />
{{NavBox IMSMA NG Administration}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Standardising_Data_Analysis_and_Information_Reporting&diff=24479Standardising Data Analysis and Information Reporting2021-05-04T11:41:23Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
Two of most important purposes of an information system are:<br />
* ensure high quality of data and<br />
* support operational use of the information.<br />
One important use of the data is reporting. If it not possible in an easy way to create reports/statistics which reflect the data correctly the credibility of the data is lost. That’s why {{IMSMANG}} was designed with a robust reporting and analysis component that supports various reporting options. These options include:<br />
<br />
<center><br />
{| class="wikitable" width="1000"<br />
|-<br />
| align="center" colspan="6" | '''Comparison of {{IMSMANG}} Reporting Options'''<br />
|-<br />
| width="20pt" | <br />
| width="195pt" | '''Basic''' <br />
| width="195pt" | '''iReport'''<br />
| width="195pt" | '''Data export'''<br />
| width="195pt" | '''Other external reporting tool'''<br />
|-<br />
| align="left" | '''Description''' <br />
| align="left" | Includes printing Data Entry Forms, Summary items and maps<br />
| align="left" | Includes building iReport templates for more sophisticated reporting as well as exporting data for use in external tools such as Microsoft Excel<br />
| align="left" | Includes exporting data to CSV format for use in Excel as well as cutting and pasting from tables.<br />
| align="left" | 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<br />
|-<br />
| align="left" | '''Uses''' <br />
| align="left" | <br />
*Navigating data in {{IMSMANG}}<br />
*General summaries of pre-provided data<br />
| align="left" | <br />
*Lists and summary reports of single items<br />
*Simple cross tabs<br />
*Monthly progress reports for internal consumption<br />
*Charts<br />
| align="left" | <br />
*Manipulating data using external tools<br />
*Pivot tables and charts based on one item<br />
| align="left" | <br />
*Linking or exporting {{IMSMANG}} data for use in external tools<br />
*Building customised reporting tools for {{IMSMANG}} data<br />
*Linking data to ArcGIS Desktop, Crystal Reports and other tools<br />
|-<br />
| align="left" | '''Benefits''' <br />
| align="left" | <br />
*Fast and easy to use<br />
*Requires little or no training<br />
| align="left" | <br />
*Can limit data using searches<br />
*Can be preformatted and available on a network<br />
*Backed up and stored<br />
*Users can simply run these reports as opposed to building them<br />
*Supports charts<br />
| align="left" | <br />
*Easiest way to get {{IMSMANG}} data into Excel<br />
*Can manipulate data in common applications<br />
| align="left" | <br />
*Most powerful and customisable way of accessing data for reports<br />
*Can manipulate data in advanced or custom reporting applications<br />
*Can be linked with external databases<br />
|-<br />
| align="left" | '''Challenges''' <br />
| align="left" | <br />
*Reports are simplistic<br />
*Limited to printing and reports provided with the software. No customisation.<br />
| align="left" | <br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Limited customisation of resulting data (formats, conditional display, etc.)<br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Requires expert level understanding of SQL<br />
|}<br />
</center><br />
[[Image:BI in context graph.png|center|700px|''The different reporting options in context'']]<br />
<div align="center"><br />
''The different reporting options in context''<br />
</div> <br />
<br />
==Basic Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} provides several reporting options that allow users to produce basic reports directly from {{IMSMANG}}. These include printing Data Entry Forms entered into the system, maps from the main navigation window and Summary items. Any of these reports can be sent directly to a printer or to an intermediate format such as rich text format (.RTF) or portable document format (.PDF) for transmitting in electronic format or for further editing.<br />
<br />
{{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.<br />
<br />
[[Image:AdminGuide_ExampleMapLayoutTemplate.png|center|500px|''Example of a Map Layout Template'']]<br />
<div align="center"><br />
''Example of a Map Layout Template''<br />
</div> <br />
<br />
{{note|<br />
* Map layouts can be printed and scaled to any size paper. This is a simple way of producing {{IMSMANG}} maps without needing additional GIS software.<br />
* Map layout templates can be prepared and distributed to individual {{IMSMANG}} clients, allowing information managers to prepare templates based on user preferences or functional needs.<br />
}} <br />
<br />
==Embedded Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} supplements the basic reporting options available to all users with several more sophisticated reporting tools that are embedded within the system. In addition to reporting on individual elements, these embedded tools allow for statistical and aggregate reporting of data within the database. Instead of reporting the contents of a single report, statistical reporting allows information managers to produce reports about multiple items and to use functions such as sum, average and count to summarise data. <br />
<br />
There are two options for embedded reporting: iReports and data export. Both functions rely on {{IMSMANG}} searches to filter data. Using iReports, information managers can build reporting templates to visualise data in a specific and repeatable format. Using data export, managers can export search results to an external tool such as Microsoft Excel and perform aggregation and statistical analysis.<br />
<br />
===iReports===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Use iReport | Use iReport]]<br />
}}<br />
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 summarise 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.<br />
<br />
Typical uses for iReport include producing reports commonly required by multiple users within a programme. These reports can include:<br />
<br />
*clearance: monthly progress reporting<br />
*education: number of people trained by type of training<br />
*land: sum of hazardous area by province or type of land<br />
*accidents: number of accidents by type or by province<br />
*data quality: number and list of land with incorrect status<br />
<br />
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 a list of land with associated ordnance details can produce different reports depending on the search parameters.<br />
<br />
[[Image:AdminGuide_ReportUsingNoSearchParameters.png|center|500px|''Report Example Using No Search Parameters'']]<br />
<div align="center"><br />
''Report Example Using No Search Parameters''<br />
</div> <br />
<br />
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 land whose status is Worked on, a different report is generated. <br />
<br />
[[Image:AdminGuide_ReportUsingSearchParameters.png|center|500px|''Report Example Using a Search Parameter'']]<br />
<div align="center"><br />
''Report Example Using a Search Parameter''<br />
</div> <br />
<br />
Moreover, if the land is further limited to a specific type, another report is generated, using again the same template. This way, information managers can build templates and searches to fulfill multiple reporting needs.<br />
<br />
Reports created with iReport can be printed directly within {{IMSMANG}} or saved to an intermediate format such as .RTF, .PDF or .XLS for electronic transmission or additional editing or inclusion in other reports. iReport supports the inclusion of charts, images and headers and footers, and it acts as a complete reporting package.<br />
<br />
===Data Export===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Exporting| Export data]]<br />
}}<br />
{{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.<br />
<br />
Because data export is initiated with a search, it provides a flexible approach for getting data to an external tool. However, once the data is used in a tool outside of {{IMSMANG}}, it is impossible to control how this data is manipulated which may limit the consistency of reports produced in this way. <br />
<br />
{{note|{{IMSMANG}} searches return information on only one item at a time, and data export is limited to the data returned by the search. Data from linked items (such as victim data linked to accidents) is not available for export.}}<br />
<br />
==External Reporting Tools==__NOEDITSECTION__<br />
{{IMSMANG}} also allows information managers to connect advanced reporting tools such as Crystal Reports or ArcGIS Desktop directly to its relational database for highly advanced report generation. With this capability, information managers can use custom reporting solutions to connect with {{IMSMANG}}, allowing for complete control of {{IMSMANG}} outputs. Or, managers can modify existing reporting solutions to connect to {{IMSMANG}}, which leverages technology already implemented in the programme and limits the need for retraining. <br />
<br />
{{note|When using external reporting tools we recommend to connect to the '''[[IMSMA Staging Area | Staging area]]''' instead of the {{IMSMANG}} database. It does require knowledge about the IMSMA data model. Contact contact your [[Information Management Team | GICHD IM advisor]] if you have questions.}}<br />
<br />
===Connecting other External Reporting Tools===__NOEDITSECTION__<br />
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 PGSQL. 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:<br />
<br />
{| class="wikitable"<br />
! scope="col" | Reporting tools || scope="col" | Database packages || scope="col" | SQL management tools<br />
|-<br />
| Crystal Reports || Microsoft Access || PGSQL Query Browser<br />
|-<br />
| ArcGIS Desktop || OpenOffice Base || Navicat<br />
|-<br />
| iReport || Microsoft SQL Server || TOAD SQL<br />
|-<br />
| Microsoft Excel || Oracle || Heidi SQL<br />
|}<br />
<br />
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.<br />
<br />
{{note|Building database views to transform data before importing it into other tools significantly reduces the performance hit associated with connecting external tools.}}<br />
<br />
===Building Database Views===__NOEDITSECTION__<br />
Building database views is the primary way of transforming data to support external reporting. Information managers can use SQL editing tools to build and save database queries as views that can be used to format data for easier reporting. Using database views, information managers can join data together into flat tables that allow for easier incorporation into reports or other analysis tools. Database views act like database tables and can be imported or queried from external tools. Moreover, views automatically refresh as data is added to {{IMSMANG}} and provide an up-to-date data source for other applications.<br />
<br />
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. <br />
<br />
<center><br />
{| class="wikitable" width="600"<br />
|-<br />
| align="left" | '''Clearance ID'''<br />
| align="left" | '''Area cleared'''<br />
| align="left" | '''AP mines found'''<br />
| align="left" | '''Hours worked'''<br />
| align="left" | '''Number of progress reports'''<br />
|-<br />
| align="left" | CL-1022<br />
| align="left" | 23,400<br />
| align="left" | 45<br />
| align="left" | 120<br />
| align="left" | 4<br />
|-<br />
| align="left" | CL-1239 <br />
| align="left" | 22,330 <br />
| align="left" | 42 <br />
| align="left" | 160 <br />
| align="left" | 6<br />
|-<br />
| align="left" | CL-2345<br />
| align="left" | 1,920<br />
| align="left" | 4<br />
| align="left" | 20<br />
| align="left" | 1<br />
|}<br />
</center><br />
<br />
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.<br />
<br />
{{note|<br />
* 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.<br />
* 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 REPLACE VIEW syntax from SQL is an easy way to build scripts for creating or replacing views if they already exist.<br />
}}<br />
<br />
{{NavBox IMSMA NG Administration}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=File:BI_in_context_graph.png&diff=24478File:BI in context graph.png2021-05-04T11:40:45Z<p>Alnaucler: </p>
<hr />
<div></div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=24477Main Page2021-05-04T11:38:26Z<p>Alnaucler: </p>
<hr />
<div>{{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1px, 1px);">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#ddd; margin:1.2em 0 6px 0; border:1px solid #ddd;"<br />
| style="width:61%; color:#000;" |<br />
<!-- "WELCOME TO IMSMA" AND ARTICLE COUNT --><br />
{| style="width:280px; border:none; background:none;"<br />
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to IMSMA Wiki,</div><br />
<div style="top:+0.2em; font-size:95%;">The IMSMA online documentation</div><br />
<div id="articlecount" style="font-size:85%;">[[Special:Statistics|{{#expr:{{formatnum:{{NUMBEROFARTICLES}}|R}}-{{formatnum:{{PAGESINCATEGORY:NoPublic|pages}}|R}}}}]] articles</div><br />
{{CURRENTDAY}} {{CURRENTMONTHNAME}} {{CURRENTYEAR}}<br />
|}<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
| style="width:13%; font-size:95%;" |<br />
* [[The Making of IMSMA|History]]<br />
* [[Portal:Using IMSMA NG|Using {{IMSMANG}}]]<br />
* [[Portal:IMSMA NG Administration|{{IMSMANG}} Administration]]<br />
* [[Portal:Remote_Entry| IMSMA Remote Entry]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:GIS|GIS]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
* [[Portal:Training|Training]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" id="mf-nec" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:54%; border:1px solid #fff; background:#fff; vertical-align:top; color:#000;" |<br />
{| id="mp-left" id="mf-nec" style="width:100%; vertical-align:top; background:#fff;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" id="mf-nec" style="margin:3px; background:#c14e5f; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" id="mf-nec" style="padding:2px 5px">The '''Information Management System for Mine Action''' is a software designed to support the needs of the mine action community for decision support, monitoring and reporting. Core elements of IMSMA include a <abbr title="Open source object-relational database management system">PostgreSQL</abbr> database engine and a geographic information system (GIS) for displaying information on maps. Its [[Understanding Configuration Options| client/server architecture]] enables stand-alone installations for small [http://www.mineaction.org/ mine action programmes] as well as client/server installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that interact with the IMSMA system. This includes the [[IMSMA Staging Area]] for advanced analytics and reporting as well more common tools like [http://en.wikipedia.org/wiki/Microsoft_Excel Microsoft Excel].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is [[Portal:IMSMA_NG_Administration#Customisation|very adaptable and can be continuously customised]] by individual programmes to suit their changing information management needs. This includes defining the type of mine action data to store and the relationships among the types, the forms used to collect information in the field and the workflows - such as for instance [http://www.gichd.org/operations/land-release-and-operational-efficiency/overview/ land release]. Significant attention should be paid when setting up and customising IMSMA to make sure that it is adapted to the needs of all staff and external stakeholders. <br />
|-<br />
| style="padding:2px;" | <h2 id="mp-dyk-h2" id="mf-nec" style="margin:3px; background:#c14e5f; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk" id="mf-nec">First released in 1998, IMSMA is now the primary software<br />
in mine action and is installed in '''47''' countries. IMSMA includes built-in flexibility to support a variety of information management needs, ranging from the largest humanitarian programs in the world to the smallest. IMSMA provides humanitarian organisations and planners with the necessary information to enhance project efficiency and maximize the value of limited resources.</div><br />
|}<br />
| style="border:1px solid transparent;" |<br />
<br />
<!-- FEATURES & SPECIFICATIONS --><br />
| class="MainPageBG" id="mf-nec" style="width:45%; border:1px solid #fff; background:#fff; vertical-align:top;"|<br />
{| id="mp-right" id="mf-nec" style="width:100%; vertical-align:top; background:#fff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" id="mf-nec" style="margin:3px; background:#999; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn" id="mf-nec"><br />
* A decision-support system with embedded GIS <br />
* Designed for the Windows operating systems and requires 3 GB of free disk space.<br />
* Currently translated into multiple languages including English, French and Spanish. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" id="mf-nec" style="margin:3px; background:#999; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd" id="mf-nec"><br />
* Java/J2EE client/server application (ver 1.7 32 bits)<br />
* [[Glossary#A|ArcGIS]] Engine ver 10.1 <br />
* PostgreSQL database engine (ver 9.1.4 32 bits)<br />
* [http://en.wikipedia.org/wiki/JasperReports JasperReports] reporting engine (iReport ver 5.0.1)<br />
* Utilises Mine Action XML ([http://www.jmu.edu/cisr/journal/20.3/pdfs/kontotasiou.pdf maXML])<br />
* Runs on Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, <br /> Windows Server 2016, Windows Server 2012, Windows Server 2008 and 2003.</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" id="mf-nec" style="margin:3px; background:#CECECE; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em">Obtaining IMSMA systems&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp" id="mf-nec"> IMSMA is provided for free. Full details on how to [[Getting IMSMA systems Installation Package | get IMSMA systems installation package ]]. </div><br />
|}<br />
|}<br />
<br />
<!-- IMSMA Training and Support --><br />
{| id="mp-lower" id="mf-nec" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #fff; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" id="mf-nec" style="width:100%; vertical-align:top; background:#fff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" id="mf-nec" style="margin:3px; background:#c14e5f; font-size:120%; font-weight:bold; text-align:left; color:#fff; padding:0.2em 0.4em">IMSMA Training and Support&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp" id="mf-nec"> For IMSMA systems training, refer to the [[Portal:Training|Training]] portal. <br />
<br />
For GICHD support to your country, refer to the [[Information Management Team]] page.<br />
</div><br />
|}<br />
|}<br />
<br />
<!-- For ZIM file --><br />
{| id="mp-lower" id="mf-nec" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #fff; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" id="mf-nec" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
|}<br />
|}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Standardising_Data_Analysis_and_Information_Reporting&diff=24476Standardising Data Analysis and Information Reporting2021-05-04T11:20:10Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
Two of most important purposes of an information system are:<br />
* ensure high quality of data and<br />
* support operational use of the information.<br />
One important use of the data is reporting. If it not possible in an easy way to create reports/statistics which reflect the data correctly the credibility of the data is lost. That’s why {{IMSMANG}} was designed with a robust reporting and analysis component that supports various reporting options. These options include:<br />
<br />
<center><br />
{| class="wikitable" width="1000"<br />
|-<br />
| align="center" colspan="6" | '''Comparison of {{IMSMANG}} Reporting Options'''<br />
|-<br />
| width="20pt" | <br />
| width="195pt" | '''Basic''' <br />
| width="195pt" | '''iReport'''<br />
| width="195pt" | '''Data export'''<br />
| width="195pt" | '''Other external reporting tool'''<br />
|-<br />
| align="left" | '''Description''' <br />
| align="left" | Includes printing Data Entry Forms, Summary items and maps<br />
| align="left" | Includes building iReport templates for more sophisticated reporting as well as exporting data for use in external tools such as Microsoft Excel<br />
| align="left" | Includes exporting data to CSV format for use in Excel as well as cutting and pasting from tables.<br />
| align="left" | 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<br />
|-<br />
| align="left" | '''Uses''' <br />
| align="left" | <br />
*Navigating data in {{IMSMANG}}<br />
*General summaries of pre-provided data<br />
| align="left" | <br />
*Lists and summary reports of single items<br />
*Simple cross tabs<br />
*Monthly progress reports for internal consumption<br />
*Charts<br />
| align="left" | <br />
*Manipulating data using external tools<br />
*Pivot tables and charts based on one item<br />
| align="left" | <br />
*Linking or exporting {{IMSMANG}} data for use in external tools<br />
*Building customised reporting tools for {{IMSMANG}} data<br />
*Linking data to ArcGIS Desktop, Crystal Reports and other tools<br />
|-<br />
| align="left" | '''Benefits''' <br />
| align="left" | <br />
*Fast and easy to use<br />
*Requires little or no training<br />
| align="left" | <br />
*Can limit data using searches<br />
*Can be preformatted and available on a network<br />
*Backed up and stored<br />
*Users can simply run these reports as opposed to building them<br />
*Supports charts<br />
| align="left" | <br />
*Easiest way to get {{IMSMANG}} data into Excel<br />
*Can manipulate data in common applications<br />
| align="left" | <br />
*Most powerful and customisable way of accessing data for reports<br />
*Can manipulate data in advanced or custom reporting applications<br />
*Can be linked with external databases<br />
|-<br />
| align="left" | '''Challenges''' <br />
| align="left" | <br />
*Reports are simplistic<br />
*Limited to printing and reports provided with the software. No customisation.<br />
| align="left" | <br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Limited customisation of resulting data (formats, conditional display, etc.)<br />
*Not ideal for incorporating multiple reports together within a larger report<br />
| align="left" | <br />
*Requires expert level understanding of SQL<br />
|}<br />
</center><br />
[[Image:MINT in context graph.png|center|700px|''The different reporting options in context'']]<br />
<div align="center"><br />
''The different reporting options in context''<br />
</div> <br />
<br />
==Basic Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} provides several reporting options that allow users to produce basic reports directly from {{IMSMANG}}. These include printing Data Entry Forms entered into the system, maps from the main navigation window and Summary items. Any of these reports can be sent directly to a printer or to an intermediate format such as rich text format (.RTF) or portable document format (.PDF) for transmitting in electronic format or for further editing.<br />
<br />
{{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.<br />
<br />
[[Image:AdminGuide_ExampleMapLayoutTemplate.png|center|500px|''Example of a Map Layout Template'']]<br />
<div align="center"><br />
''Example of a Map Layout Template''<br />
</div> <br />
<br />
{{note|<br />
* Map layouts can be printed and scaled to any size paper. This is a simple way of producing {{IMSMANG}} maps without needing additional GIS software.<br />
* Map layout templates can be prepared and distributed to individual {{IMSMANG}} clients, allowing information managers to prepare templates based on user preferences or functional needs.<br />
}} <br />
<br />
==Embedded Reporting==__NOEDITSECTION__<br />
{{IMSMANG}} supplements the basic reporting options available to all users with several more sophisticated reporting tools that are embedded within the system. In addition to reporting on individual elements, these embedded tools allow for statistical and aggregate reporting of data within the database. Instead of reporting the contents of a single report, statistical reporting allows information managers to produce reports about multiple items and to use functions such as sum, average and count to summarise data. <br />
<br />
There are two options for embedded reporting: iReports and data export. Both functions rely on {{IMSMANG}} searches to filter data. Using iReports, information managers can build reporting templates to visualise data in a specific and repeatable format. Using data export, managers can export search results to an external tool such as Microsoft Excel and perform aggregation and statistical analysis.<br />
<br />
===iReports===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Use iReport | Use iReport]]<br />
}}<br />
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 summarise 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.<br />
<br />
Typical uses for iReport include producing reports commonly required by multiple users within a programme. These reports can include:<br />
<br />
*clearance: monthly progress reporting<br />
*education: number of people trained by type of training<br />
*land: sum of hazardous area by province or type of land<br />
*accidents: number of accidents by type or by province<br />
*data quality: number and list of land with incorrect status<br />
<br />
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 a list of land with associated ordnance details can produce different reports depending on the search parameters.<br />
<br />
[[Image:AdminGuide_ReportUsingNoSearchParameters.png|center|500px|''Report Example Using No Search Parameters'']]<br />
<div align="center"><br />
''Report Example Using No Search Parameters''<br />
</div> <br />
<br />
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 land whose status is Worked on, a different report is generated. <br />
<br />
[[Image:AdminGuide_ReportUsingSearchParameters.png|center|500px|''Report Example Using a Search Parameter'']]<br />
<div align="center"><br />
''Report Example Using a Search Parameter''<br />
</div> <br />
<br />
Moreover, if the land is further limited to a specific type, another report is generated, using again the same template. This way, information managers can build templates and searches to fulfill multiple reporting needs.<br />
<br />
Reports created with iReport can be printed directly within {{IMSMANG}} or saved to an intermediate format such as .RTF, .PDF or .XLS for electronic transmission or additional editing or inclusion in other reports. iReport supports the inclusion of charts, images and headers and footers, and it acts as a complete reporting package.<br />
<br />
===Data Export===__NOEDITSECTION__<br />
{{HowTo's<br />
|[[Exporting| Export data]]<br />
}}<br />
{{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.<br />
<br />
Because data export is initiated with a search, it provides a flexible approach for getting data to an external tool. However, once the data is used in a tool outside of {{IMSMANG}}, it is impossible to control how this data is manipulated which may limit the consistency of reports produced in this way. <br />
<br />
{{note|{{IMSMANG}} searches return information on only one item at a time, and data export is limited to the data returned by the search. Data from linked items (such as victim data linked to accidents) is not available for export.}}<br />
<br />
==External Reporting Tools==__NOEDITSECTION__<br />
{{IMSMANG}} also allows information managers to connect advanced reporting tools such as Crystal Reports or ArcGIS Desktop directly to its relational database for highly advanced report generation. With this capability, information managers can use custom reporting solutions to connect with {{IMSMANG}}, allowing for complete control of {{IMSMANG}} outputs. Or, managers can modify existing reporting solutions to connect to {{IMSMANG}}, which leverages technology already implemented in the programme and limits the need for retraining. <br />
<br />
{{note|When using external reporting tools we recommend to connect to the '''[[IMSMA Staging Area | Staging area]]''' instead of the {{IMSMANG}} database. It does require knowledge about the IMSMA data model. Contact contact your [[Information Management Team | GICHD IM advisor]] if you have questions.}}<br />
<br />
===Connecting other External Reporting Tools===__NOEDITSECTION__<br />
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 PGSQL. 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:<br />
<br />
{| class="wikitable"<br />
! scope="col" | Reporting tools || scope="col" | Database packages || scope="col" | SQL management tools<br />
|-<br />
| Crystal Reports || Microsoft Access || PGSQL Query Browser<br />
|-<br />
| ArcGIS Desktop || OpenOffice Base || Navicat<br />
|-<br />
| iReport || Microsoft SQL Server || TOAD SQL<br />
|-<br />
| Microsoft Excel || Oracle || Heidi SQL<br />
|}<br />
<br />
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.<br />
<br />
{{note|Building database views to transform data before importing it into other tools significantly reduces the performance hit associated with connecting external tools.}}<br />
<br />
===Building Database Views===__NOEDITSECTION__<br />
Building database views is the primary way of transforming data to support external reporting. Information managers can use SQL editing tools to build and save database queries as views that can be used to format data for easier reporting. Using database views, information managers can join data together into flat tables that allow for easier incorporation into reports or other analysis tools. Database views act like database tables and can be imported or queried from external tools. Moreover, views automatically refresh as data is added to {{IMSMANG}} and provide an up-to-date data source for other applications.<br />
<br />
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. <br />
<br />
<center><br />
{| class="wikitable" width="600"<br />
|-<br />
| align="left" | '''Clearance ID'''<br />
| align="left" | '''Area cleared'''<br />
| align="left" | '''AP mines found'''<br />
| align="left" | '''Hours worked'''<br />
| align="left" | '''Number of progress reports'''<br />
|-<br />
| align="left" | CL-1022<br />
| align="left" | 23,400<br />
| align="left" | 45<br />
| align="left" | 120<br />
| align="left" | 4<br />
|-<br />
| align="left" | CL-1239 <br />
| align="left" | 22,330 <br />
| align="left" | 42 <br />
| align="left" | 160 <br />
| align="left" | 6<br />
|-<br />
| align="left" | CL-2345<br />
| align="left" | 1,920<br />
| align="left" | 4<br />
| align="left" | 20<br />
| align="left" | 1<br />
|}<br />
</center><br />
<br />
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.<br />
<br />
{{note|<br />
* 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.<br />
* 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 REPLACE VIEW syntax from SQL is an easy way to build scripts for creating or replacing views if they already exist.<br />
}}<br />
<br />
{{NavBox IMSMA NG Administration}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Template:NavBox_Business_Intelligence&diff=24475Template:NavBox Business Intelligence2021-05-04T11:15:26Z<p>Alnaucler: </p>
<hr />
<div>{{Navbox<br />
| name = NavBox Business Intelligence<br />
| state = {{{state|<includeonly>autocollapse</includeonly><noinclude>uncollapsed</noinclude>}}}<br />
| title = [[Portal:Business Intelligence|Business Intelligence]]<br />
| liststyle = line-height:1.3em;<br />
| bodyclass = hlist<br />
<br />
| group1 = [[Staging Area Generator]]<br />
| list1 = [[Install Staging Area Generator]]&nbsp;· [[Using Staging Area Generator]]&nbsp;· [[Post Processing SQL Scripts]]&nbsp;· [[SAG Spatial reference system]]&nbsp;· [[Name Rules Staging Area]]&nbsp;· [[Scheduling the Staging Area creation]]<br />
| group2 = [[IMSMA Staging Area|IMSMA Staging Area]]<br />
| list2 = [[Staging Area Database | IMSMA Staging Area Database]]&nbsp;· [[Connecting to IMSMA Staging area from ArcGIS]]&nbsp;· [[Connecting to IMSMA Staging area from Excel]]&nbsp;· [[Sharing an IMSMA Staging Area]]<br />
<br />
<br />
<br />
| group4 = Other Reporting Tools<br />
| list4 = [[Other Reporting Tools]]<br />
| group5 = Indicators<br />
| list5 = [[Indicators | Introduction to indicators]]<br />
}}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=IMSMA_Staging_Area&diff=24474IMSMA Staging Area2021-05-04T11:14:03Z<p>Alnaucler: </p>
<hr />
<div>The IMSMA staging area is a '''flattened''' and '''read-only''' version of the {{IMSMANG}} operational database. In terms of content, the data is an exact copy of the '''approved''' information in the {{IMSMANG}} database, but the structure is less complex and therefore easier to query. <br />
<br />
While in the operational {{IMSMANG}} database the item data (e.g. the ID, status and name of a Land) is stored in one table and other information about the Land (such as multi-select and custom defined fields) are stored in separate tables. Furthermore in the {{IMSMANG}} information are also stored with enumeration values and as links between objects. In the staging area all this information is flattened in one single table for each item. Therefore, there is lesser need to write complex queries to retrieve attributes of an object. <br />
<br />
A staging area can be created out of an {{IMSMANG}} v 6.0 (and higher) database. It is typically used as a '''reporting database''', via [[Other Reporting Tools|reporting/analysis tool]] such as Excel or ArcGIS.<br />
<br />
{{NavBox Business Intelligence}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Glossary&diff=24473Glossary2021-05-04T11:12:34Z<p>Alnaucler: </p>
<hr />
<div>{{compact ToC}}<br />
<br />
<br />
==A==__NOEDITSECTION__<br />
;APMBC: [http://www.apminebanconvention.org/ Anti-Personnel Mine Ban Convention]<br />
;ArcGIS: It is a software suite developed by ESRI Inc. IMSMA incorporates the ArcGIS Engine to display the geographical data in the map pane<br />
;[[Auxiliary Data]]: Auxiliary data provide supplementary or additional information to the main items/objects in IMSMA. Auxiliary data is of the following types in IMSMA: Country structure, Organisation, Place, Ordnance classification, Cause classification, Needs classification and Assistance classification. <br />
;AXO: Abandoned Explosive Ordnance, explosive ordnance that has not been used during an armed conflict, that has been left behind or dumped by a party to an armed conflict, and which is no longer under control of the party that left it behind or dumped it. Abandoned explosive ordnance may or may not have been primed, fuzed, armed or otherwise prepared for use. (CCW protocol V) <br />
<br />
==B==__NOEDITSECTION__<br />
;[[Point Types | Benchmark]]: is a fixed point of reference used to locate a marked and recorded hazard or hazardous '''area'''. It should normally be located a short distance outside the hazardous area. It should be safe to walk from the Reference / Landmark to the Benchmark.<br />
<br />
==C==__NOEDITSECTION__<br />
;C-IED: Counter-Improvised Explosive Device is an activity done by a nation’s security forces (i.e. '''not''' humanitarian demining organisations). It includes all elements of defeating IEDs and the people funding, making and laying them, so not only neutralising the devices ([[Glossary#I |IEDD]]) but tracking where components came from, who made the IED, who planted it etc.<br />
;CCM: [http://www.clusterconvention.org/ Convention on Cluster Munitions]<br />
;CCW: [https://www.icrc.org/applic/ihl/ihl.nsf/INTRO/500?OpenDocument Convention on Certain Conventional Weapons]<br />
;CDF: [[Custom Defined Fields]] are fields that allows you to create fields for country specific needs. <br />
;Centroid: The geometric center of a feature. For line, polygon, or three-dimensional features, it is the center of mass (or center of gravity) and may fall inside the feature or outside the feature.<br />
;CHA: Confirmed Hazardous Area, refers to an area where the presence of mine/ERW contamination has been confirmed on the basis of direct evidence of the presence of mines/ERW. <br />
;CRPD: [http://www.un.org/disabilities/ Convention on the Rights of Persons with Disabilities]<br />
<br />
==D==__NOEDITSECTION__<br />
;[[Data Categories | Data Category]]: The Data Inventory Manager allows you to organise item attributes into meaningful groupings, or data categories. <br />
;[[Using Data Entry Forms|Data Entry Form]]: Data entry forms are used to collect mine action data such as accidents and victims, land, activities, locations, education activities, and quality management information and display them in a standardised format. They used to be called Field Reports.<br />
;[[Data Entry Form Templates]]: They are forms that can are used for adding data IMSMA. Templates are created by IMSMA administrators.<br />
;[[Data Inventory Manager]]: Using Data Inventory Manager, information managers can create new data elements or modify existing elements to map to their programme’s information needs.<br />
;Derived field: a field that is calculated from another object<br />
<br />
==E==__NOEDITSECTION__<br />
;EOD: Explosive Ordnance Disposal, the detection, identification, evaluation, render safe, recovery and disposal of explosive ordnance.<br />
;ERW: Explosive Remnants of War, includes landmines, Unexploded Ordnance (UXO) and Abandoned Explosive Ordnance (AXO).<br />
;[[Point Types | Evidence point]]: is used for Cluster munitions and other UXO. It is used for recording where ordnance are found i.e. a strong claim with high confidence<br />
<br />
==F==__NOEDITSECTION__<br />
<br />
==G==__NOEDITSECTION__<br />
;GICHD: [http://www.gichd.org/ Geneva International Centre for Humanitarian Demining]<br />
;GIS: Geographic Information System<br />
;GMAP: Gender and Mine Action Programme<br />
;GPS: Global positioning system<br />
<br />
==H==__NOEDITSECTION__<br />
<br />
==I==__NOEDITSECTION__<br />
;IED: Improvised Explosive Device is a device placed or fabricated in an improvised manner incorporating destructive, lethal, noxious, pyrotechnic or incendiary chemicals and designed to destroy, incapacitate, harass or distract.<br />
;IEDD: Improvised Explosive Device Disposal means neutralising the device which is '''not''' the same as '''[[Glossary#C | C-IED]]'''.<br />
;IDP: Internally Displaced Person<br />
;IM: Information Management<br />
;IMSMA: Information Management System for Mine Action<br />
;IMSMA Legacy: refers to IMSMA version 1 - 3<br />
;IMSMA NG: IMSMA New Generation, refers to IMSMA version 4 - 6 and should be written {{IMSMANG}}<br />
;IMAS: [http://www.mineactionstandards.org/ International Mine Action Standards]<br />
;Items: There are three different type of items in IMSMA:<br />
# [[Location Summary Window | Location]], <br />
# [[Task Tab | Task]] <br />
# [[Land Summary Window | Land]], [[Activity Summary Window | Activity]], [[Accident Summary Window | Accident]], [[Victim Summary Window | Victim]], [[Assistance Summary Window | Assistance]], [[Education Summary Window | Education]] and [[QM Summary Window | QM]]. <br />
:They can be viewed in the [[Items Pane]] of the [[IMSMA Navigation Window]].<br />
<br />
==J==__NOEDITSECTION__<br />
<br />
==K==__NOEDITSECTION__<br />
<br />
==L==__NOEDITSECTION__<br />
;[[Point Types | Landmark]]: is a fixed point of reference some distance outside the hazardous '''area''. It should be an easily recognised feature (such as a cross-roads or a bridge) which can be used to assist in navigating to one or more benchmarks.<br />
<br />
==M==__NOEDITSECTION__<br />
;maXML: [[XML Documentation | Mine Action Extensible Markup Language]]<br />
;MBT: Mine Ban Treaty, another acronym for APMBC [http://www.apminebanconvention.org/ Anti-Personnel Mine Ban Convention]<br />
;MGRS: Military Grid Reference System (MGRS)is the geocoordinate standard used by NATO for locating points on the earth. The MGRS is derived from the Universal Transverse Mercator (UTM) grid system and the universal polar stereographic (UPS) grid system, but uses a different labelling convention. The MGRS is used for the entire earth. An example of an MGRS coordinate, or grid reference, would be 4QFJ12345678, which consists of three parts:<br />
: '''4Q''' (grid zone designator, GZD)<br />
: '''FJ''' (the 100,000-meter square identifier)<br />
: '''12345678''' (numerical location; easting is 1234 and northing is 5678, in this case specifying a location with 10 m resolution).<br />
;MINT: (Mine action INTelligence) which was a business intelligence tool developed by GICHD<br />
;MIQ: Mine action Information management Qualification, old term for the different levels of '''[[Portal:Training | IMSMA training]]'''<br />
<br />
==N==__NOEDITSECTION__<br />
;[[IMSMA Navigation Window | Navigation Window]]:The IMSMA Navigation window is the main window from which all of IMSMA’s features are accessed. The window contains a menu toolbar, a status bar, and three panes: the country structure pane, map pane, and items pane. <br />
;NMAS: National Mine Action Standards but could also refer to National Mine Action Strategy.<br />
;Notification area: a notification area (also system tray or status area) is the portion of the user interface that displays icons for system and program features that have no presence on the desktop as well as the time and the volume icon. It contains mainly icons that show status information, though some programs, use it for minimized windows. By default, this is located in the bottom-right of the primary monitor (or bottom-left on languages of Windows that use right-to-left reading order), or at the bottom of the taskbar if docked vertically. <br />
;Novetta Solutions: The consulant company that was first contracted for IMSMA software development<br />
;NTS: Non-Technical Survey, refers to the collection and analysis of data, without the use of technical interventions, about the presence, type, distribution and surrounding environment of mine/ERW contamination, in order to define better where mine/ERW contamination is present, and where it is not, and to support land release prioritisation and decision-making processes through the provision of evidence.<br />
<br />
==O==__NOEDITSECTION__<br />
<br />
==P==__NOEDITSECTION__<br />
;P-code : A P-code, short for Place code, is referring to:<br />
* a unique identifier of parts of the Country Structure defined by a governmental organization;<br />
* a kind of addressing system used mostly by emergency response teams. It provides unique identifiers to thousands of locations and administrative units in a humanitarian operation. The p-codes are represented by combinations of letters and/or numbers to identify a specific location or feature on a map or within a database. These codes provide a systematic means of linking data to an unambiguous location. Any information that is tagged with P-codes can be combined and analyzed with any other p-coded data. The p-codes for a country can be found in the Common Operational Datasets, which are standard geographic references for the humanitarian community provided by UN OCHA.<br />
==Q==__NOEDITSECTION__<br />
;QA: Quality Assurance (QA) part of QM focused on providing confidence that quality requirements will be fulfilled. [ISO 9000:2000]<br />
:Note: The purpose of QA in humanitarian demining is to confirm that management practices and operational procedures for demining are appropriate, are being applied, and will achieve the stated requirement in a safe, effective and efficient manner. Internal QA will be conducted by demining organisations themselves, but external inspections by an external monitoring body should also be conducted.<br />
<br />
;QC: Quality Control (QC) part of QM focused on fulfilling quality requirements. [ISO 9000:2000]<br />
:Note: QC relates to the inspection of a finished product. In the case of humanitarian demining, the 'product' is safe cleared land.<br />
<br />
;QM: Quality Management(QM) coordinated activities to direct and control an organisation with regard to quality. [ISO 9000:2000]<br />
<br />
==R==__NOEDITSECTION__<br />
;[[Point Types | Reference point]]: is a fixed point of reference some distance outside the hazardous '''area'''. It should be an easily recognised feature (such as a cross-roads or a bridge) which can be used to assist in navigating to one or more benchmarks.<br />
<br />
==S==__NOEDITSECTION__<br />
;SADD: Sex- and Age-Disaggregated Data <br />
;SHA: Suspected Hazardous Area. refers to an area where there is reasonable suspicion of mine/ERW contamination on the basis of indirect evidence of the presence of mines/ERW.<br />
;SOPs: Standard Operating Procedures, instructions which define the preferred or currently established method of conducting an operational task or activity. Their purpose is to promote recognisable and measurable degrees of discipline, uniformity, consistency and commonality within an organisation, with the aim of improving operational effectiveness and safety. SOPs should reflect local requirements and circumstances.<br />
;Subobject: Subobjects are subcategories within certain IMSMA items (land, activity, accident, victim, education, organisation, task). Subobjects are normally displayed in table format. <br />
;[[Summary Window]]: A Summary Window displays when you open an object from the Items Pane of the IMSMA Navigation window. The Summary Window shows the most important available fields that have been selected to be included from the Data Entry Form.<br />
<br />
==T==__NOEDITSECTION__<br />
;TS: Technical Survey, refers to the collection and analysis of data, using appropriate technical interventions, about the presence, type, distribution and surrounding environment of mine/ERW contamination, in order to define better where mine/ERW contamination is present, and where it is not, and to support land release prioritisation and decision making processes through the provision of evidence.<br />
<br />
==U==__NOEDITSECTION__<br />
;UAV: Unmanned Aerial Vehicle (piloted by remote control) used for taking aerial photos of an area.<br />
;UN: United Nations<br />
;[[Point Types | Usage point]]: is used for Cluster munitions and other UXO. Usage point has three main types: verified target point, intended target point and firing point (both land and air)<br />
;UXO: Unexploded Ordnance, explosive ordnance that has been primed, fuzed, armed or otherwise prepared for use or used. It may have been fired, dropped, launched or projected yet remains unexploded either through malfunction or design or for any other reason.<br />
<br />
==V==__NOEDITSECTION__<br />
<br />
==W==__NOEDITSECTION__<br />
<br />
==X==__NOEDITSECTION__<br />
;xml: Extensible Markup Language (XML) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. The Mine Action sector has defined a schema, [[XML Documentation | maXML]], for data sharing.<br />
==Y==__NOEDITSECTION__<br />
<br />
==Z==__NOEDITSECTION__<br />
<br><br />
{{compactTOC}}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Patch_Installation_Guide&diff=24471Patch Installation Guide2021-05-04T11:09:28Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
<br />
{{Note| Patch installation of {{IMSMANG}} v 6.0 is '''ONLY''' possible to use when {{IMSMANG}} v 6.0 is already installed.}}<br />
<br />
==Part 1. Preparations==__NOEDITSECTION__ <br />
{{Warning| Read this section carefully because the patch installation will change configuration files.}}<br />
<br />
[[Image:PatchInstallationGuideStep1.png|center|500px|''Preparation before running the IMSMA Patch Installer'']]<br />
<br />
<ol><br />
<li>Stop the {{IMSMANG}} client and server.<br />
<li>If you have made any changes to the [[Install IMSMANG Version 6#Part 5 Type of configuration| client and/or server configuration]], note them down.<br />
<li>Take a backup of the {{IMSMANG}} database.<br />
<li>Exit the IMSMA Control Centre.<br />
<li>Take a copy of the two main PostGreSQL configuration files ''C:\IMSMAng\pgsql\data\pg_hba.conf'' and ''C:\IMSMAng\pgsql\data\postgresql.conf''. These contain any custom configurations, e.g. allowing remote database access, etc.<br />
<li>If you have set up [[PgSQL_Replication|SQL replication]], you also should take a copy of ''recovery.conf'' on the standby server, as well as the above mentioned configuration files on '''both the master and the standby server'''.<br />
</ol><br />
<br />
==Part 2. Run the {{IMSMANG}} Patch Installer==__NOEDITSECTION__ <br />
[[Image:PatchInstallationGuideStep2.png|center|500px|''Running the IMSMA Patch Installer'']]<br />
<br />
[[Image:Cmd NG.png|center|400px]]<br />
<ol><br />
<li>Double-click the '''Install_IMSMA.exe''' file in the patch installation package.</li><br />
<li>When the command window displays, follow the instructions.<br />
<br />
[[Image:Graphic NG.png|center|200px]]</li><br />
<br />
<li>On the Language Selection window, select the language you want to use during installation and click '''OK'''.<br />
<br />
[[Image:1st panel NG.png|center|400px]]</li><br />
<br />
<li>Navigate the Installation panels of the graphical installer as described below:<br />
<ol><br />
<li>In the Welcome panel, click '''Next'''.</li><br />
<li>Select the ''I accept the terms of this license agreement'' option, and click '''Next'''.</li><br />
<li>In the packages selection panel, click '''Next'''.</li><br />
<li>Wait for the installation progress bar to finish, then click '''Next'''.</li><br />
<li>When the Setup Shortcuts panel displays, click '''Next'''.</li><br />
<li>When the installation has completed successfully, click '''Done'''.<br />
<br />
{{note | When the graphical installer has finished the focus goes back to the command window and the next steps of the installation continue so please do not close the command window.}}</li></ol><br />
</li><br />
<br />
<li>When prompted by the command window, press any key on the keyboard to continue.</li><br />
</ol><br />
<br />
==Part 3. Set Permissions for the IMSMA Control Centre==__NOEDITSECTION__ <br />
[[Image:PatchInstallationGuideStep3.png|center|500px|''Setting IMSMA Control Centre Permissions'']]<br />
<div align="center"><br />
</div><br />
<br />
<ol><li>On your desktop, right-click the IMSMA Tray Launcher icon and select the '''Properties''' option.</li><br />
<li>In the IMSMA Tray Launcher Properties window, select the '''Shortcut''' tab, then click '''Advanced'''. </li><br />
<li>In the Advanced Properties window, check the '''Run as administrator''' checkbox, then click '''OK'''. It is important to use ''Run as administrator'' the first time {{IMSMANG}} is started since other installation programs will be triggered. Depending on how much user permissions are limited, it might be better to not Run as administrator.</li><br />
<li>Back in the IMSMA Tray Launcher Properties window, click '''OK'''. It is important to set this property since you will start other applications with the Tray Launcher.</li><br />
</ol><br />
==Part 4. PostGreSQL configuration==__NOEDITSECTION__ <br />
[[Image:PatchInstallationGuideStep4.png|center|500px|''PostGreSQL configuration'']]<br />
<br />
If there have been any changes done in the PostGreSQL configuration files<br />
# C:\IMSMAng\pgsql\data\pg_hba.conf<br />
# C:\IMSMAng\pgsql\data\postgresql.conf<br />
# C:\IMSMAng\pgsql\data\recovery.conf<br />
they have to be '''re-applied'''. <br />
<br />
{{Note| There might have been changes of the files in the patch so all customisation needs to be '''re-applied'''. Note that if you have [[PgSQL_Replication|SQL replication]] set up, the right configuration files need to be restored on the master and the standby server, and the initial backup procedure from the master to the standby needs to be applied. }}<br />
<br />
==Part 5. Verification of the client/server configuration==__NOEDITSECTION__ <br />
[[Image:PatchInstallationGuideStep5.png|center|500px|''Verification of the client/server configuration'']]<br />
<br />
The patch installation may also update other configurations than the PostGreSQL so the client and/or server configurations should be verified before continuing.<br />
<ol><br />
<li>The file ''C:\IMSMAng\trayLauncher\TrayLauncher.properties'' where the memory allocation is set, should not changed by the patch installation.<br/><br/><br />
[[Image:ClientConfig.png|center|500px]]<br />
<div align="center"><br />
</div><br />
<br />
<li>The client configuration should not changed by the patch installation.<br />
<li> The file ''c:\imsmang\server\imsmaserver\conf\GisService.properties'' needs to be double-checked.<br />
</ol><br />
<br />
==Part 6. Database Update==__NOEDITSECTION__ <br />
[[Image:PatchInstallationGuideStep6.png|center|500px|''Database update'']]<br />
<br />
<ol><br />
<li>On your desktop, double-click the IMSMA Tray Launcher icon.<br />
<br/><br />
<br />
[[Image:DBupdate1.png|center|400px]]</li><br />
<br />
<li>A message will be displayed notifying you if there are any database changes that needs to be applied. Click '''OK''' to begin the process(es).</li><br />
<br />
<br />
[[Image:DBupdate2.png|center|600px]]</li><br />
<br />
<li>A SQL Upgrade window will display and the progress will be shown in the lower part of the window.<br />
<br />
<br />
[[Image:DBupdate3.png|center|400px]]</li><br />
<br />
<br />
<li>When the update process is done a message will be displayed. Click '''OK'''.<br />
<br />
</ol><br />
<br />
{{NavBox IMSMA NG Administration}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Exchange&diff=24470Information Exchange2021-05-04T11:08:38Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
{{IMSMANG}} is designed to support data/information exchange with many IMSMA users and Mine Action stakeholders at numerous sites. These users can include implementing partners, Regional Mine Action Centers and other authorities (e.g. Ministry of Health). <br />
<br />
{{IMSMANG}} supports several patterns for exchanging '''data''' including <br />
* one-direction exchange<br />
* two-direction exchange<br />
* peer-to-peer exchange<br />
* combinations of the above.<br />
<br />
{{HowTo's<br />
| [[Information Exchange Models]]<br />
| Centralised Data Entry<br />
| [[Setting-up Decentralised Information Exchange | Decentralised Data Entry]]<br />
}}<br />
The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners. <br />
<br />
{{IMSMANG}} supports several methods for exchanging '''information''' including <br />
* producing maps with [[Connecting to IMSMA Staging area from ArcGIS | external GIS]] software<br />
* producing reports with [[Use iReport | iReport]] and [[Connecting to IMSMA Staging area from Excel | Excel]]<br />
* publish information to websites via the [[IMSMA Staging Area]].<br />
<br />
[[Image:Data Information Organisation.png|650px|center]]<br />
<div align="center"><br />
'' Who needs what''<br />
</div><br />
An important part of establishing data/information exchange is to plan and document the data/informations exchange flows including the different steps in the workflows so a sustainable and smooth exchanges and high-quality information are obtained.<br />
<br />
==Plan Data/Information Exchange==__NOEDITSECTION__<br />
{| class="wikitable"<br />
|-<br />
| [[Image:Understanding Configuration Options - One way.png|300px|center|]]<br />
| [[Image:Information exchange.png|300px|center|]]<br />
|- <br />
| '' One way exchange plan only covering operators and national database ''<br />
| '' Example of information exchange between stakeholders''<br />
|}<br />
<br />
It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents and with different periodicity.<br />
<br />
The following points need to be taken in consideration when planning exchange:<br />
* why is the data/information shared? <br />
* what are the consequences if data/information are not shared on time?<br />
* what data/information need/could be shared?<br />
* who is the receiver?<br />
* what will the receiver use the data/information for?<br />
:* show contamination impact<br />
:* input to operational planning<br />
:* show the outcome of Mine Action<br />
:* other purposes<br />
* will the receiver share the data/information in his turn?<br />
* how often? <br />
* in which format?<br />
:* paper/pdf<br />
:* Excel<br />
:* shape files<br />
:* xml<br />
:* IMSMA backup<br />
:* Staging area database<br />
:* website<br />
<br />
==Workflows==__NOEDITSECTION__ <br />
When the plan for data/information exchange is outlined it is very important to document the different exchanges so it is clear to all stakeholders in each data/information exchange workflow:<br />
* who does what?<br />
* how often?<br />
* who is responsible for data quality?<br />
* who solves data conflicts including duplicates?<br />
* how and who corrects mistakes?<br />
* who deletes data?<br />
<br />
A process map of each exchange workflow is a good complement to the detailed written documentation of the workflow. <br />
<br />
==IMSMA specific rules==__NOEDITSECTION__ <br />
Data exchange workflows to the national database should include:<br />
* how to decide which Location to use?<br />
* which items should have links to what?<br />
* nice-to-have - desired - required data fields<br />
* who decides final ID of items?<br />
<br />
{{Note | When data is shared between implementing partners and National Mine Action Authority it is important that IDs are '''not''' changed. E.g. Progress report created by implementing partner with ID ''PR-NPA-CHA-15/1'' should still have the same ID after import and approval in the national database.}}<br />
<br />
===Ensuring Correct Roles and Permissions are Assigned===__NOEDITSECTION__<br />
Establishing correct [[Defining Roles, Permissions and Users | roles and permissions]] in {{IMSMANG}} is a key factor in managing and maintaining data exchange with {{IMSMANG}}. Using the permissions structure, the information manager can carefully control access to key functions that affect data exchange including Data Entry Form templates, Custom Defined Fields, Auxiliary data and Data Entry Form approval. When permissions are correctly established and user accounts created, information managers can distribute the {{IMSMANG}} dataset to implementing partners knowing that key data controls are in place.<br />
<br />
These are the recommended role permissions:<br />
* Ensure that the Central Mine Action Authority has exclusive control over <br />
:* user accounts and roles<br />
:* Data Entry Form templates<br />
:* Data Inventory Manager and <br />
:* Auxiliary data.<br />
* Ensure that the implementing partners have Data Entry, Approval and export/import Data Entry Forms permissions. <br />
<br />
By establishing a set of limited permissions for the implementing partners, information managers can prevent the accidental or intentional creation of new data elements that will affect the ability of the Central Mine Action Authority to import Data Entry Forms and cause the national dataset to become fractured.<br />
<br />
By limiting Auxiliary data permissions to the Central Mine Action Authority, information managers can prevent complications when importing Data Entry Forms. Because Data Entry Forms refers to Auxiliary data, it is important that each country have one common set of [[Standardising Auxiliary Data | Auxiliary data]] to facilitate exchange. If the Auxiliary data is not properly synchronised, the exchange of Data Entry Forms can result in import issues which must be manually resolved. While {{IMSMANG}} provides an interface for resolving these kinds of issues, it is recommended to reduce the occurrence of these issues by limiting any creation of Auxiliary data to the Central Mine Action Authority who can then distribute an updated dataset as necessary. <br />
<br />
==Collecting Regular Feedback==__NOEDITSECTION__<br />
In any data/information exchange activity, it is important to have regular follow-up or meetings to collect feedback and discuss issues or improvements to the data/information exchange process. One recommendation is to establish a feedback forum where implementing partners and stakeholders can address data quality issues and make adjustments to the data/information exchange process. Topics to address in such a forum include:<br />
<br />
* frequency of data/information exchange<br />
* standardisation of reports and searches to be included in the central dataset<br />
* permissions and role changes<br />
* creation or modification of Auxiliary data<br />
* which data to collect<br />
* changes of templates<br />
* output products like reports, statistics, maps<br />
<br />
By collecting feedback on these points, information managers can help ensure that data/information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.<br />
<br />
{{NavBox IMSMA NG Administration}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Other_Reporting_Tools&diff=24469Other Reporting Tools2021-05-04T11:07:26Z<p>Alnaucler: </p>
<hr />
<div>Some commonly used tools are:<br />
* [https://products.office.com/en/excel Excel]: data from the staging area can be accessed from Excel, where charts, Pivot Tables etc. can be created to show and disseminate statistics. [[Connecting_to_IMSMA_Staging_area_from_Excel|This page]] describes how to connect from Excel to the [[IMSMA_Staging_Area|IMSMA Staging Area]].<br />
* [https://products.office.com/en/access Access]<br />
* [https://www.tableau.com/ Tableau]<br />
* [https://powerbi.microsoft.com/en-us/ PowerBI]<br />
<br />
Many other tools exist on the market, but are more rarely used in mine action. A longer list of reporting software can be found [https://en.wikipedia.org/wiki/List_of_reporting_software here], and comparisons between tools can easily be found in the internet.<br />
<br />
If you are unsure what system to test or use, please contact your [[Information_Management_Team|GICHD IM focal point]] who will discuss requirements and assist in finding appropriate solutions.<br />
<br />
{{NavBox Business Intelligence}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Assistance_Summary_Window&diff=24468Assistance Summary Window2020-09-28T12:30:19Z<p>Alnaucler: </p>
<hr />
<div>{{New_6.0 | The Assistance item was added in 6.0.}}<br />
The '''assistance''' to both individuals (direct and indirect beneficiaries) and communities may be recorded with this new object in version 6.0. Assistance is the '''action''' of assisting victims. Monitoring of assistance projects may be done with the existing [[Using the Tasking Tool in IMSMANG| Task]] module.<br />
<br />
[[Image:VA Principle.png|500px|center]]<br />
<br />
'''Assistance''' is closely linked to the [[Victim Summary Window#Cause subobject|Cause]] of someone becoming a victim and the [[Victim Summary Window#Needs subobject|Needs assessment]] of the Victim(s). The assistance can be provided to:<br />
* an individual;<br />
* a family / extended family;<br />
* a group of victims;<br />
* a community.<br />
<br />
[[Image:Beneficiaries.png|500px|center]]<br />
<br />
The [[Victim Summary Window#Cause subobject| Cause]] and [[Victim Summary Window#Needs subobject | Needs assessment]] of individuals are entered in the [[Victim Summary Window | Victim]]. <br />
<br />
The ''business rules'' for calculating which pillar a victim is at must take in consideration the following: <br />
* There is no global definition of number of pillars<br />
* There are no mandatory pillars<br />
* There is no chronological or logical order between pillars<br />
* A victim may receive assistance of more than one pillar at the same time<br />
* A victim may receive assistance of a pillar more than once.<br />
<br />
==Given Assistance subobject==__NOEDITSECTION__<br />
[[Image:Assistance.png|thumb|500px]]<br />
<br />
The Assistance (actions) may be classified in the following phases:<br />
* Emergency (health care and humanitarian aid)<br />
* Stabilisation (health services, education, economic reintegration and physical accessibility)<br />
* Transition (social inclusion, advocacy, data collection and physical accessibility)<br />
* Protection (risk analysis)<br />
* Legal support (law/policy)<br />
* Institutional reinforcement (institution staff support, education/awareness and access to services)<br />
<br />
Each country needs to define what is included in each of the above [[Auxiliary Data | phases/pillars]].<br />
<br />
Assistance items may contain more than one Given Assistance.<br />
<br />
==Database fields==__NOEDITSECTION__<br />
{|<br />
|- valign="top"<br />
|<br />
{| class="wikitable" width="400"<br />
|-<br />
| align="center" colspan="2" | '''Assistance'''<br />
|-<br />
| width="200pt" | '''Field'''<br />
| width="150pt" | '''Data Type'''<br />
|-<br />
| Assistance ID || String<br />
|-<br />
| Assistance Name || String<br />
|-<br />
| Assistance decided by || Organisation<br />
|-<br />
| Assistance given at || Place<br />
|-<br />
| Assistance given by || Organisation<br />
|-<br />
| Assistance paid by || Organisation<br />
|-<br />
| Comment || Text<br />
|-<br />
| Cost/Grant || BigDecimal<br />
|-<br />
| Currency || Single Select<br />
|-<br />
| Needs assessment done by || Organisation<br />
|-<br />
| Number of Direct Beneficiaries || Integer<br />
|-<br />
| Number of Indirect Beneficiaries || Integer<br />
|-<br />
| Priority || Single Select<br />
|-<br />
| Status || Single Select<br />
|-<br />
| Status changed reason || Single Select<br />
|-<br />
| Status changed date|| Date<br />
|-<br />
| Status changed comment || Text<br />
|}<br />
|<br />
{| class="wikitable"<br />
| align="center" colspan="2" | '''Given Assistance'''<br />
|-<br />
| width="200pt" | '''Field'''<br />
| width="150pt" | '''Data Type'''<br />
|-<br />
| Given Assistance||Single-select<br />
|-<br />
| Status||Single-select<br />
|-<br />
| Start Date||Date<br />
|-<br />
| End Date||Date<br />
|-<br />
| Quantity||Integer<br />
|}<br />
|}<br />
{{note | The '''Assistance''' item has a status and each row in the subobject Given Assistance has a status.}}<br />
<br />
The parts of the Summary window are explained [[Summary Window|here]].<br />
<br />
{{New_6.0| The Inspiration Data Entry Form template for Assistance has been updated to included the field ''Status changed date'' and is available for [[Downloads | download]] here.}}<br />
<br />
==External links==__NOEDITSECTION__<br />
Guidence on Victim assistance reporting <br/><br />
[http://www.apminebanconvention.org/fileadmin/APMBC/Guidance-on-Victim-Assistance-Reporting.pdf Guide]<br />
<br />
Read more about Victim assistance in the different conventions on:<br />
* [http://www.apminebanconvention.org/ Anti-Personnel Mine Ban Convention]<br />
* [http://www.clusterconvention.org/ Convention on Cluster Munitions]<br />
* [http://www.un.org/disabilities/ Convention on the Rights of Persons with Disabilities]<br />
<br />
{{NavBox HowTo Viewing and Browsing}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Java_automatic_update&diff=24467Java automatic update2020-06-18T09:26:40Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
Java has the standard configuration to check for updates automatically. If higher version of Java is installed then the Java version that {{IMSMANG}} is using might get uninstalled. The environment variable JAVA_HOME will also get updated. It is possible to have both Java 7 and Java 8 installed. This page explains how to stop Java from automatically check for updates which will prevent users from installing a version that might affect {{IMSMANG}}.<br />
<br />
The Java control panel is sometimes not easy to find. The ''Alternative method'' should work on all Windows versions.<br />
If the change does not seem to have effect i.e. you still get notification to update Java then may sure that you are making the change with '''Administrator''' permission.<br />
<br />
==Step 1 - Start the Java control panel==__NOEDITSECTION__ <br />
How to find it depends on Java version and operating system.<br />
<br />
=== Find the Java Control Panel - Java versions below 7u40===__NOEDITSECTION__ <br />
==== Windows XP ====__NOEDITSECTION__<br />
# Click on the Start button and then click on the Control Panel option.<br />
# Double click on the Java icon to open the Java Control Panel.<br />
<br />
==== Windows 7 and Vista ====__NOEDITSECTION__<br />
# Click on the Start button and then click on the Control Panel option.<br />
# In the Control Panel Search enter Java Control Panel.<br />
# Click on the Java icon to open the Java Control Panel.<br />
<br />
==== Windows 8====__NOEDITSECTION__<br />
# Use search to find the Control Panel <br />
## Press Windows logo key + W to open the Search charm to search settings '''OR'''<br />
## Drag the Mouse pointer to the bottom-right corner of the screen, then click on the Search icon. <br />
# In the search box enter Java Control Panel<br />
# Click on Java icon to open the Java Control Panel. <br />
<br />
==== Windows 10 ====__NOEDITSECTION__<br />
# Right-click on the Start button and select the Control Panel option.<br />
# In the Windows Control Panel, click on Programs.<br />
# Click on the Java icon to open the Java Control Panel.<br />
<br />
=== Find the Java Control Panel - Java 7 Update 40 (7u40) and later versions===__NOEDITSECTION__ <br />
Starting with Java 7 Update 40, you can find the Java Control Panel through the Windows Start menu. <br />
# Launch the Windows Start menu<br />
# Click on Programs (All Apps on Windows 10)<br />
# Find the Java program listing<br />
# Click Configure Java to launch the Java Control Panel<br />
<br />
=== Alternative method===__NOEDITSECTION__ <br />
If you did not find Java control panel with the above methods then try with:<br />
<ol start="1"><br />
<li> Click Windows Start button. </li><br />
<li> In the Start Search box, type: <br />
: Windows 32-bit OS: c:\Program Files\Java\jre7\bin<br />
: Windows 64-bit OS: c:\Program Files (x86)\Java\jre7\bin</li><br />
<li> In the folder find javacpl.exe</li><br />
<li> Right-click and choose ''Run as administrator''</li><br />
</ol><br />
<br />
==Step 2 - Change Automatic Update Settings==__NOEDITSECTION__ <br />
[[Image:Jcp-autocheck.jpg|350px]]<br/><br />
# Click the Update tab.<br />
# To disable Java Update, '''deselect''' the ''Check for Updates Automatically'' check box. <br />
# Click OK.<br />
<br />
<br/><br />
[[Image:Update-bubble.jpg|250px]]<br/><br />
Now this message should not be shown again.<br />
<br />
{{NavBox Technical Notes}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Downloads&diff=24466Downloads2020-05-08T09:55:45Z<p>Alnaucler: </p>
<hr />
<div>{{Note | These files should only be downloaded if needed}} <br />
<br />
On this page you will find miscellaneous files for download. All files will be zipped and will need to be unzipped/extracted before you may use them.<br />
{| class="wikitable sortable"<br />
|-<br />
!width="200" | Contains <br />
!width="200" | File name <br />
!width="500" | Comment<br />
|- valign = "top"<br />
|-<br />
| Administrator Level 1 || '''[[Media:Wiki_training_flow_chart.vsd | wiki training flowchart]]''' ||<br />
|-<br />
| Assistance classification || '''[[Media:Assistance classification.xlsx|Excel file]]''' || The '''inspiration''' classification that comes with the installation <br />
|- <br />
| Background map World image || '''[[Media:World backgroundmap.zip| mxd file]]''' || ''Clean'' version of the World map<br />
|-<br />
| Background map World on-line|| '''[[Media:WorldOnline backgroundmap.zip| mxd file]]''' || ''Clean'' version of the World map with ArcGIS Online layers<br />
|-<br />
| Cause classification || '''[[Media:Cause classification.xlsx|Excel file]]''' || The '''inspiration''' classification that comes with the installation<br />
|-<br />
| Configuration file for PostgreSQL || '''[[Media:Pg hba.zip|Pg hba.zip]]''' || If you do not have an editor for text file<br />
|-<br />
| Data Entry Form Template || '''[[Media:Inspiration_Assistance.zip| Inspiration Assistance]]''' || The field Status changed date has been added (September 2015)<br />
|-<br />
| Data Entry Form Template || '''[[Media:Inspiration_Education.zip| Inspiration Education]]''' || The template has been corrected (March 2017)<br />
|-<br />
| Data Entry Form Template || '''[[Media:Inspiration_Education_Details.zip| Inspiration Education Details]]''' || The template has been corrected (March 2017)<br />
|-<br />
| Data Entry Form Template || '''[[Media:RAPID_Accident.zip| RAPID Accident]]''' || The combobox ''Wind speed'' has been corrected<br />
|-<br />
| Excel file template || '''[[Media:ExcelImportTemplate.zip|ExcelImportTemplate.zip]]''' || [[Import Geospatial Data from Excel]]<br />
|-<br />
| French translation || '''[[Media:French translation.zip|French_translation.zip]]'''|| Updated June 2016<br />
|-<br />
| IMSMA logo || '''[[Media:IMSMA_Logo51px.jpg| IMSMA logo 51 pixel]]''' || Suitable for Data Entry Template page header<br />
|-<br />
| Installer .Net 3.5. SP1 || '''[http://mwiki.gichd.org/mediawiki/images/0/00/dotnetfx35sp1.zip dotnetfx35sp1.zip]'''|| In case .Net 3.5 is not installed on the computer (required for ArcEngine installation). On Windows 8 and Windows 10 you may activate .NET in the Control panel but that requires Internet connection.<br />
|-<br />
| Land Release Symbology || '''[[Media:LR Symbology.zip | LR Symbology.zip]]''' || In style format to be used with ArcGIS<br />
|-<br />
| Map Layout examples || '''[[Media:MapLayoutExamples.zip|MapLayoutExamples.zip]]''' || 2 templates of Layout Examples (one with scale bar in meters, another in km). In order to use them you should go to Map Layout in IMSMA, click on the Layout (first button: [[Apply a Template to the Map Page Layout]]) and select examples. Please note that you should select All Types (not .mxt). MXT. doesn’t exist anymore as a format. It has been replaced by the .mxd format. <br />
|-<br />
| mxd in ArcGIS 10.1 version || '''[[Media:imsma_mxd_10_1.zip|imsma_mxd_10_1.zip]]''' || <br />
|-<br />
| Needs assessment classification || '''[[Media:Needs assessment classification.xlsx|Excel file]]''' || The '''inspiration''' classification that comes with the installation<br />
|-<br />
| Offline Installer .Net 3.5. 32 bits Win10 || '''[http://mwiki.gichd.org/mediawiki/images/0/00/Net Framework 3.5 offline installer Win_10_32.zip]''' || In case .Net 3.5 activation is not working on Windows 10 32 bits.<br />
|-<br />
| Offline Installer .Net 3.5. 64 bits Win10 || '''[http://mwiki.gichd.org/mediawiki/images/0/00/Net Framework 3.5 offline installer Win_10_64.zip]'''|| In case .Net 3.5 activation is not working on Windows 10 64 bits.<br />
|-<br />
| PostgreSQL files for ArcGIS || '''[[Media:PGsupportArcGIS.zip|PGsupportArcGIS.zip]]''' || To be copied to ''ArcGIS\Desktop10.1\bin''<br />
|-<br />
| PostgreSQL ODBC '''32-bits''' driver || '''[[Media:PGSQL_ODBC.zip|PGSQL_ODBC.zip]]''' || To be used with 32-bits Microsoft <span style="color:#ff0000">'''Office'''</span>, see [[Installation ODBC driver ]]<br />
|-<br />
| PostgreSQL ODBC '''64-bits''' driver || '''[[Media:PGSQL_ODBC_64.zip|PGSQL_ODBC_64.zip]]''' || To be used with 64-bits Microsoft <span style="color:#ff0000">'''Office'''</span>, see [[Installation ODBC driver ]]<br />
|- <br />
| Rosetta-J || '''[[Media:Rosetta_J.zip | Rosetta_J.zip]]''' || Rosetta-J is used for translation<br />
|- <br />
| SAG mxd with LR Symbology || '''[[Media:Staging-13-04-17.zip|Staging-13-04-17.zip]]''' || This mxd replaces the previous one. The only change is that it contains LR Symbology.<br />
|- <br />
| Shape file template Point || '''[[Media:PointImportTemplate.rar | PointImportTemplate.rar]] || [[Import Geospatial Data from Shapefile]]<br />
|-<br />
| Shape file template Polygon || '''[[Media:PolygonImportTemplate.rar | PolygonImportTemplate.rar]] || [[Import Geospatial Data from Shapefile]]<br />
|-<br />
| Spanish translation || '''[[Media:Spanish_translation.zip|Spanish_translation.zip]]'''|| Newer than what is included in the installation package<br />
|-<br />
| Web Mercator projection || '''[[Media:WGS_1984_Web_Mercator_(auxiliary_sphere).zip|WGS_1984_Web_Mercator_(auxiliary_sphere).zip]]''' || Should be stored in ''C:\IMSMAng\server\gis\coordinate systems\Projected Coordinate Systems\World'' folder<br />
|-<br />
| ZIM file || '''[http://mwiki.gichd.org/mediawiki/images/0/00/ImsmaWiki.zim ImsmaWiki.zim]''' || To be copied to ''C:\IMSMAng\trayLauncher\exe\Kiwix'' (Created 8 March 2019)<br />
|}<br />
<br />
{{NavBox Technical Notes}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Save_the_Page_Layout_as_a_Template&diff=24465Save the Page Layout as a Template2020-05-08T09:52:58Z<p>Alnaucler: </p>
<hr />
<div>{{Warning | Since mxt files are not supported with ArcGIS 10.1 this function has issues.}}<br />
<br />
A map Layout includes any shapes, text, page setup options, images, scale bar, north indicator, or legend that you have added to the map Layout.<br />
To save a Layout:<br />
<ol><br />
<li>Click the [[Image:SaveMapLayIcon.png]] button on the Map Layout toolbar.</li><br />
:The Save window displays.<br />
[[Image:Map template save.png|500px|center]]<br />
<li>From the Save window:</li><br />
<ol type="a"><br />
<li>Change file type to ''All files''.<br />
<li>Navigate to the directory where you would like to save the Layout.</li><br />
<li>Enter a name for the Layout (e.g. MyLayout.mxd) in the File Name field.</li><br />
<li>Click the '''Save''' button.</li><br />
</ol><br />
</ol><br />
<br />
{{NavBox HowTo Work with the Map}}<br />
<br />
[[Category:CRI]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24464Information Management Team2020-04-28T15:53:13Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olivier-cottray/ Olivier COTTRAY] || '''Head, Information Management'''|| - || Albania, Armenia, Benin, Burundi, Congo, Cote d'Ivoire, Cyprus, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Iran, Israel, Kenya, Kosovo, Kuwait, Liberia, Mali, Morocco, Mozambique, Myanmar, Nepal, Oman, Rwanda, Sierra Leone, South Sudan, Spain, Sudan, Uganda and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan, Colombia, Lao People's Democratic Republic, and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Mauritania, Palestine, Tajikistan, Ukraine, Vietnam and Yemen<br />
<!--|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Angola, Pacific and Zimbabwe<br />
--><br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Thailand<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq, Syria, and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]], Capacity Development, IM assessments || Afghanistan, Angola, Chad, Chile, DRC, Libyan Arab Jamahiriya, Pacific, Senegal, Somalia and Zimbabwe<br />
|}<br />
[[Category:COO]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24461Information Management Team2020-04-06T17:01:59Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olivier-cottray/ Olivier COTTRAY] || '''Head, Information Management'''|| - || Albania, Armenia, Benin, Burundi, Congo, Cote d'Ivoire, Cyprus, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Iran, Israel, Kenya, Kosovo, Kuwait, Liberia, Mali, Morocco, Mozambique, Myanmar, Nepal, Oman, Rwanda, Sierra Leone, South Sudan, Spain, Sudan, Uganda and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan, Colombia, Lao People's Democratic Republic, and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Mauritania, Palestine, Tajikistan, Ukraine, Vietnam and Yemen<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Angola, Pacific and Zimbabwe<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Thailand<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq, Syria, and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]], Capacity Development, IM assessments || Chad, Chile, DRC, Libyan Arab Jamahiriya, Senegal, and Somalia <br />
|}<br />
[[Category:COO]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24460Information Management Team2020-03-23T20:24:40Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olivier-cottray/ Olivier COTTRAY] || '''Head, Information Management'''|| - || Albania, Armenia, Benin, Burundi, Chad, Congo, Cote d'Ivoire, Cyprus, DRC, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Iran, Israel, Kenya, Kosovo, Kuwait, Liberia, Mali, Morocco, Mozambique, Myanmar, Nepal, Oman, Rwanda, Senegal, Sierra Leone, South Sudan, Spain, Sudan, Thailand, Uganda, Vietnam and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Chile, Colombia, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Libyan Arab Jamahiriya, Mauritania, Palestine, Somalia, Syria, Ukraine and Yemen<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Angola, Lao People's Democratic Republic, Pacific and Zimbabwe<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Tajikistan<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]] ||<br />
|}<br />
[[Category:COO]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=24459Information Management Team2020-03-23T20:16:53Z<p>Alnaucler: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Country focal point''' <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olivier-cottray/ Olivier COTTRAY] || '''Head, Information Management'''|| - || Armenia, Benin, Burundi, Cyprus, Eritrea, Ethiopia, Georgia, Guinea-Bissau, Israel, Kenya, Kuwait, Liberia, Myanmar, Nepal, Oman, Rwanda, Sierra Leone, Spain, Thailand, Uganda and Zambia<br />
|- <br />
|| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/olena-davydenko/ Olena DAVYDENKO] || Project Officer || EGIS || -<br />
|-<br />
| Olivier Demars || Consultant|| IMSMA Core and IMSMA NG || Argentina, Chile, Colombia, Ecuador, Lebanon, Nicaragua, and Peru <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/marlene-joris/ Marlène JORIS] || Programme Officer || Project management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/harry-kendall Harry KENDALL] || Geoservices Advisor || GIS Infrastructure Management || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/andrew-kesterton/ Andrew KESTERTON] || IM technical development coordinator || IMSMA Core || Azerbaijan and Western Sahara<br />
|-<br />
| Dionysia KONTOTASIOU ||Consultant|| Wiki, Pedagogical Tools and Methods || -<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/sulaiman-mukahhal Sulaiman MUKAHHAL] || Advisor, Information Management || 3rd Party applications and maXML || Egypt, Jordan, Libyan Arab Jamahiriya, Mauritania, Palestine, Somalia, Syria, Ukraine and Yemen<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/anne-li-naucler/ Anne-Li NAUCLÉR] || Advisor, Information Management || [[Portal:Technical Notes |Technical support]] and IMSMA Legacy || Afghanistan, Albania, Angola, Iran, Kosovo, Lao People's Democratic Republic, Mozambique, Pacific, South Sudan, Sudan and Zimbabwe<br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/wendi-pedersen/ Wendi PEDERSEN] || Advisor, Geographic Information Systems || Geoservices, [[Portal:GIS|GIS]] and Mapping Support || Cambodia, Sri Lanka and Tajikistan<br />
|-<br />
| Henrik RYDBERG || Advisor, Information Management || IMSMA Core and Data standards || BiH, Iraq and Turkey<br />
|-<br />
| Firoz VERJEE || Consultant || EGIS System Engineer || <br />
|-<br />
| [https://www.gichd.org/en/the-gichd/who-we-are/detail/contact/noor-zangana/ Noor ZANGANA] || Information Management Support Coordinator || [[Portal:Training| Training]] || Chad, Congo, Cote d'Ivoire, DRC, Mali, Morocco, Senegal and Vietnam<br />
|}<br />
[[Category:COO]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=FieldReportInfo_Artifact&diff=24458FieldReportInfo Artifact2020-02-26T14:07:27Z<p>Alnaucler: </p>
<hr />
<div>{{Note | The table is called ''fieldreport'' and the ''maXML element level3'' is called ''FieldReportInfo''. }}<br />
<br />
FieldReportInfo contains metadata describing '''item''' MineActionFieldReports. All item data reports contains a FieldReportInfo and an item data part. In {{IMSMANG}} FieldReportInfo is referred to as Data Entry Form (DEF). <br />
<br />
FieldReportInfo data has ''FieldReport'' in ''maXML element level2'' and ''FieldReportInfo'' in ''maXML element level3''.<br/><br />
E.g. Land item data has ''FieldReport'' in ''maXML element level2'' and ''Hazard'' in ''maXML element level3''.<br />
<br />
[[Image:Fr xml.png|900px]]<br />
<br />
{| class="wikitable sortable"<br />
! maXML element level4 !! maXML Type !! DIM Label <br />
|-<br />
| FieldReportName || String || Data Entry Form Template<br />
|-<br />
| Version || String || Version<br />
|-<br />
| ReportingPerson || String || Reported By<br />
|-<br />
| ReportingPosition || String || Reported By Position<br />
|-<br />
| ReportingOrg || String || Report Owner<br />
|-<br />
| ReportingDate || Date || Date Of Information<br />
|-<br />
| VerifyingDate || Date || Approved Date<br />
|-<br />
| VerifiedBy || String || Approved By<br />
|-<br />
| ReportCompletedDate || Date || Submitted Date<br />
|-<br />
| Other || String || Comments<br />
|}<br />
{{NavBox XML Documentation}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=FieldReportInfo_Artifact&diff=24457FieldReportInfo Artifact2020-02-26T14:07:08Z<p>Alnaucler: </p>
<hr />
<div>{{Note | The table is called ''fieldreport'' and the ''maXML element level3'' is called ''FieldReportInfo''. }}<br />
<br />
FieldReportInfo contains metadata describing '''item''' MineActionFieldReports. All item data reports contains a FieldReportInfo and an item data part. In {{IMSMANG}} FieldReportInfo is referred to as Data Entry Form. <br />
<br />
FieldReportInfo data has ''FieldReport'' in ''maXML element level2'' and ''FieldReportInfo'' in ''maXML element level3''.<br/><br />
E.g. Land item data has ''FieldReport'' in ''maXML element level2'' and ''Hazard'' in ''maXML element level3''.<br />
<br />
[[Image:Fr xml.png|900px]]<br />
<br />
{| class="wikitable sortable"<br />
! maXML element level4 !! maXML Type !! DIM Label <br />
|-<br />
| FieldReportName || String || Data Entry Form Template<br />
|-<br />
| Version || String || Version<br />
|-<br />
| ReportingPerson || String || Reported By<br />
|-<br />
| ReportingPosition || String || Reported By Position<br />
|-<br />
| ReportingOrg || String || Report Owner<br />
|-<br />
| ReportingDate || Date || Date Of Information<br />
|-<br />
| VerifyingDate || Date || Approved Date<br />
|-<br />
| VerifiedBy || String || Approved By<br />
|-<br />
| ReportCompletedDate || Date || Submitted Date<br />
|-<br />
| Other || String || Comments<br />
|}<br />
{{NavBox XML Documentation}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=IMSMA_NG_Training_Levels&diff=24456IMSMA NG Training Levels2020-02-23T15:01:37Z<p>Alnaucler: </p>
<hr />
<div>This page describes the various training courses and realated qualification level that currently exist for {{IMSMANG}}.<br />
Training courses provided by the GICHD are advertised few months before the actual training dates on the [https://www.gichd.org/what-we-do/upcoming-events/ GICHD Calendar of Events].<br />
<br />
==User level description==__NOEDITSECTION__ <br />
User training is mostly provided in-country by IMSMA administrators holding an A1 certificate. User training is only occasionally provided by the GICHD.<br />
The aim of the user training is to train people in using the IMSMA application, i.e. get familiar with the application, enter data, search for data, and get familiar with built-in GIS functionalities.<br />
<br />
User level 1 (U1) is staff who occasionally need to browse, search and print information from {{IMSMANG}} using reports or maps that are created by an administrator. <br />
<br />
User level 2 (U2) is data entry staff and staff involved in operational planning / tasking. <br />
<br />
User level 3 (U3) is staff that participates in the data quality and data approval processes. <br />
<br />
'''[[Media:Agenda IMSMA User.pdf | Agenda IMSMA User]]'''<br />
<br />
==Administrator Level 1 description==__NOEDITSECTION__ <br />
The course provides an opportunity for Mine Action stakeholders to enhance the capacity of Information Management (IM) personnel in national mine action programmes to administer the {{IMSMANG}} application and to provide effective Information Management services to their organisations.<br />
<br />
<u>Course objectives</u><br />
<br />
On a managerial level, the objectives of the course are to <br />
* Acquire knowledge on IM principles and concepts<br />
* Understand the importance of identifying information requirements prior to designing Data Entry forms<br />
* Gain awareness of the need to communicate and coordinate with strategic and operational personnel within their respective organisations.<br />
<br />
On a technical level, the objectives of the course are to <br />
* Learn how to install, use and administer {{IMSMANG}}<br />
* Customize IMSMA according to the programmes’ needs and in coordination with operations and programme management. <br />
<br />
This course is intended for participants from National Mine Action Programmes and their Operating Partners who are or will be posted to Information Management positions within their respective organisations. It is important that participants of this course have strong technical database skills and team or project management skills.<br />
<br />
'''[[Media:Agenda IMSMA A1.pdf | Agenda IMSMA A1]]'''<br />
{{NavBox Training}}<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Template:NavBox_Training&diff=24455Template:NavBox Training2020-02-23T15:00:00Z<p>Alnaucler: </p>
<hr />
<div>{{Navbox<br />
| name = NavBox Training<br />
| state = {{{state|<includeonly>autocollapse</includeonly><noinclude>uncollapsed</noinclude>}}}<br />
| title = [[Portal:Training|Training Portal]]<br />
| liststyle = line-height:1.3em;<br />
| bodyclass = hlist<br />
<br />
| group1 = ''IMSMA''<br />
| list1 = [[IMSMA NG Training Levels]]&nbsp;· [[Pages used in User]]&nbsp;· [[Pages used in A1]]<br />
| group2 = ''GIS''<br />
|list2 = [[Basic GIS training]]&nbsp;· [[Advanced GIS training]]<br />
<br />
}}</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Pages_used_in_A1&diff=24454Pages used in A12020-02-23T14:59:29Z<p>Alnaucler: </p>
<hr />
<div>{|<br />
|- valign="top"<br />
|<br />
{| class="wikitable sortable"<br />
! Day !! Session !! External link !! Internal link !! Language<br />
|-<br />
| Day01 || IMSMA v6 installation || http://mwiki.gichd.org/IM/Install_IMSMANG_Version_6 || [[Install_IMSMANG_Version_6 ]] || English<br />
|-<br />
| Day01 || IMSMA v6 installation || http://mwiki.gichd.org/IM/Installer_IMSMANG_version_6 || [[Installer_IMSMANG_version_6]] || French<br />
|-<br />
| Day01 || IMSMA v6 installation || http://mwiki.gichd.org/IM/Starting_and_Stopping_IMSMANG || [[Starting_and_Stopping_IMSMANG ]] || English<br />
|-<br />
| Day01 || IMSMA v6 installation || http://mwiki.gichd.org/IM/Restore_IMSMA_Backup_on_Server || [[Restore_IMSMA_Backup_on_Server]] || English<br />
|-<br />
| Day01 || IMSMA v6 installation || http://mwiki.gichd.org/IM/Patch_Installation_Guide || [[Patch_Installation_Guide]] || English<br />
|-<br />
| Day07 || Configure IMSMA: Define roles, permissions and users || http://mwiki.gichd.org/IM/Restore_IMSMA_Backup_on_Server || [[Restore_IMSMA_Backup_on_Server]] || English<br />
|-<br />
| Day07 || Configure IMSMA: Define roles, permissions and users || http://mwiki.gichd.org/IM/Backup_and_Restore || [[Backup_and_Restore ]] || English<br />
|-<br />
| Day07 || Configure IMSMA: Define roles, permissions and users || http://mwiki.gichd.org/IM/Import_an_IMSMA_Map || [[Import_an_IMSMA_Map ]] || English<br />
|-<br />
| Day07 || Configure IMSMA: Define roles, permissions and users || http://mwiki.gichd.org/IM/Defining_Roles,_Permissions_and_Users || [[Defining_Roles,_Permissions_and_Users]] || English<br />
|-<br />
| Day07 || IMSMA Search Functionalities || http://mwiki.gichd.org/IM/Searching_for_Data_in_IMSMANG || [[Searching_for_Data_in_IMSMANG ]] || English<br />
|-<br />
| Day07 || IMSMA Search Functionalities || http://mwiki.gichd.org/IM/Building_Searches || [[Building_Searches ]] || English<br />
|-<br />
| Day02 || IMSMA data model || http://mwiki.gichd.org/IM/Understanding_IMSMA_Information_Model || [[Understanding_IMSMA_Information_Model ]] || English<br />
|-<br />
| Day03 || Process mapping || http://mwiki.gichd.org/IM/Documenting_Customisations || [[Documenting_Customisations ]] || English<br />
|-<br />
| Day03 || Identifying information requirements || http://mwiki.gichd.org/IM/Understanding_Mine_Action_Information_Management || [[Understanding_Mine_Action_Information_Management ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Data_Inventory_Manager || [[Data_Inventory_Manager]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Standardising_Data_Entry_Forms || [[Standardising_Data_Entry_Forms ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Data_Entry_Form_Templates || [[Data_Entry_Form_Templates ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Save_a_Data_Entry_Form_Template || [[Save_a_Data_Entry_Form_Template ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Change_the_Status_of_a_Published_Data_Entry_Form_Template || [[Change_the_Status_of_a_Published_Data_Entry_Form_Template ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Configuring_the_Items_ID_Generator || [[Configuring_the_Items_ID_Generator ]] || English<br />
|-<br />
| Day04 || IMSMA Customisation concept || http://mwiki.gichd.org/IM/Summary_Templates || [[Summary_Templates ]] || English<br />
|-<br />
| Day04 || Customize and enter auxiliary data || http://mwiki.gichd.org/IM/Auxiliary_Data || [[Auxiliary_Data ]] || English<br />
|-<br />
| Day04 || Customize and enter auxiliary data || http://mwiki.gichd.org/IM/Standardising_Auxiliary_Data || [[Standardising_Auxiliary_Data]] || English<br />
|-<br />
| Day04 || Import data entry scripts || http://mwiki.gichd.org/IM/Importing_and_Exporting_Data_with_IMSMANG || [[Importing_and_Exporting_Data_with_IMSMANG ]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Using_Data_Entry_Forms || [[Using_Data_Entry_Forms]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Enter_Geospatial_Data_in_the_Data_Entry_Form || [[Enter_Geospatial_Data_in_the_Data_Entry_Form ]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Manual_Geospatial_Data_Entry || [[Manual_Geospatial_Data_Entry ]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Point_Types || [[Point_Types ]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Reconciling_and_Approving_Data_in_IMSMANG || [[Reconciling_and_Approving_Data_in_IMSMANG]] || English<br />
|-<br />
| Day05 || Data entry and reconciliation || http://mwiki.gichd.org/IM/Reconcile || [[Reconcile]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Setting-up_Maps_and_Coordinate_Systems || [[Setting-up_Maps_and_Coordinate_Systems ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Customise_Sub-Themes || [[Customise_Sub-Themes]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Map_Pane || [[Map_Pane ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Enable_a_Map_Theme || [[Enable_a_Map_Theme]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Explore_the_Toolbars || [[Explore_the_Toolbars ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Display_Items_in_Map_Pane || [[Display_Items_in_Map_Pane]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Enable_an_IMSMA_Theme || [[Enable_an_IMSMA_Theme]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Change_IMSMA_Theme_Display_Properties || [[Change_IMSMA_Theme_Display_Properties ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Identify_Selected_Items_and_Symbols || [[Identify_Selected_Items_and_Symbols]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Display_Items_in_Map_Pane || [[Display_Items_in_Map_Pane]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Measure_Distance_on_the_Map || [[Measure_Distance_on_the_Map]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Display_the_Area_and_Length_of_a_Polygon || [[Display_the_Area_and_Length_of_a_Polygon]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Drop_a_Visual_Pin_on_the_Map || [[Drop_a_Visual_Pin_on_the_Map]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Identify_Objects_on_the_Map || [[Identify_Objects_on_the_Map]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Change_the_Coordinate_Reference_System_Display || [[Change_the_Coordinate_Reference_System_Display ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Printing_the_Map_in_IMSMANG || [[Printing_the_Map_in_IMSMANG]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Control_the_Page_Layout || [[Control_the_Page_Layout ]] || English<br />
|-<br />
| Day02 || IMSMA GIS functionality || http://mwiki.gichd.org/IM/Display_the_Map_Layout_Shapes_Toolbar || [[Display_the_Map_Layout_Shapes_Toolbar]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Add_a_Coordinate_System || [[Add_a_Coordinate_System]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Enter_Geospatial_Data_in_the_Data_Entry_Form || [[Enter_Geospatial_Data_in_the_Data_Entry_Form ]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Manual_Geospatial_Data_Entry || [[Manual_Geospatial_Data_Entry ]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Draw_on_the_Map_to_Specify_Geographic_Coordinates || [[Draw_on_the_Map_to_Specify_Geographic_Coordinates]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Import_Geospatial_Data_from_Excel || [[Import_Geospatial_Data_from_Excel ]] || English<br />
|-<br />
| Day05 || Importing geospatial data || http://mwiki.gichd.org/IM/Import_Geospatial_Data_from_Shapefile || [[Import_Geospatial_Data_from_Shapefile ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Data_Entry_Form_Templates || [[Data_Entry_Form_Templates ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Save_a_Data_Entry_Form_Template || [[Save_a_Data_Entry_Form_Template ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Share_Data_Entry_Form_Templates || [[Share_Data_Entry_Form_Templates ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Reconcile_CDFs_When_Publishing_a_Data_Entry_Form || [[Reconcile_CDFs_When_Publishing_a_Data_Entry_Form ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Import_a_Data_Entry_Form_from_a_xml_File || [[Import_a_Data_Entry_Form_from_a_xml_File ]] || English<br />
|-<br />
| Day05 || Share DEF templates || http://mwiki.gichd.org/IM/Export_Data_Entry_Form_from_Workbench || [[Export_Data_Entry_Form_from_Workbench ]] || English<br />
|-<br />
| Day06 || Other objects in IMSMA || http://mwiki.gichd.org/IM/Add_a_Data_Entry_Form_from_the_Summary_Window#Special_case_-_Double_reconciliation_Education_Details || [[Add_a_Data_Entry_Form_from_the_Summary_Window#Special_case_-_Double_reconciliation_Education_Details ]] || English<br />
|-<br />
| Day06 || Other objects in IMSMA || http://mwiki.gichd.org/IM/Accident_Summary_Window || [[Accident_Summary_Window]] || English<br />
|-<br />
| Day06 || Other objects in IMSMA || http://mwiki.gichd.org/IM/Victim_Summary_Window || [[Victim_Summary_Window]] || English<br />
|-<br />
| Day06 || Other objects in IMSMA || http://mwiki.gichd.org/IM/Assistance_Summary_Window || [[Assistance_Summary_Window ]] || English<br />
|-<br />
| Day06 || Tasking Tool || http://mwiki.gichd.org/IM/Using_the_Tasking_Tool_in_IMSMANG || [[Using_the_Tasking_Tool_in_IMSMANG ]] || English<br />
|-<br />
| Day08 || Introduction to reporting and data analysis || http://mwiki.gichd.org/IM/Standardising_Data_Analysis_and_Information_Reporting || [[Standardising_Data_Analysis_and_Information_Reporting ]] || English<br />
|-<br />
| Day08 || iReport || http://mwiki.gichd.org/IM/IReport_does_not_start || [[IReport_does_not_start ]] || English<br />
|-<br />
| Day08 || iReport || http://mwiki.gichd.org/IM/Producing_Reports_Using_IMSMANG || [[Producing_Reports_Using_IMSMANG ]] || English<br />
|-<br />
| Day08 || iReport || http://mwiki.gichd.org/IM/Manage_Report_Templates_in_IMSMA || [[Manage_Report_Templates_in_IMSMA ]] || English<br />
|-<br />
| Day08 || iReport || http://mwiki.gichd.org/IM/Manage_Reports_in_IMSMA || [[Manage_Reports_in_IMSMA ]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/IMSMA_Staging_Area || [[IMSMA_Staging_Area ]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/Staging_Area_Generator || [[Staging_Area_Generator ]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/Scheduling_the_Staging_Area_creation || [[Scheduling_the_Staging_Area_creation ]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/Installation_ODBC_driver || [[Installation_ODBC_driver ]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/Create_ODBC_source || [[Create_ODBC_source]] || English<br />
|-<br />
| Day08 || Staging Area || http://mwiki.gichd.org/IM/Connecting_to_IMSMA_Staging_area_from_ArcGIS || [[Connecting_to_IMSMA_Staging_area_from_ArcGIS ]] || English<br />
|}<br />
{{NavBox Training}}<br />
<br />
[[Category:NAA]]</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Portal:Training/IMSMA&diff=24453Portal:Training/IMSMA2020-02-23T14:57:42Z<p>Alnaucler: </p>
<hr />
<div>The establishment of the Mine action Information management Qualification (MIQ) scheme made the training courses delivered by the GICHD more effective, through greater standardisation of outcome competencies for each core Information Management role of a Mine Action Programme. The training courses have formal prerequisites, learning objectives and are role-oriented. Note that all training course have '''exams''' with minimum scores defined for reaching the certification.<br />
The levels of qualification are divided into two groups with several levels:<br />
* U = User training which is conducted in country by certified {{IMSMANG}} Administrators. <br />
* A = Administrator training which is conducted by GICHD. For upcoming courses consult [http://www.gichd.org/calendar-of-events/calendar-of-events/ the calendar of events]. <br />
<br />
The different target participants for the different levels are described '''[[IMSMA NG Training Levels | here]]'''.<br />
<br />
<br />
Download the [http://mwiki.gichd.org:8090/mediawiki/images/9/99/Wiki_training_flow_chart.vsd wiki IMSMA administrator level 1 training flowchart]<br />
<br />
{| class="wikitable"<br />
! colspan="2" | These pages are referenced during our training courses<br />
|- <br />
| width="220" | [[Pages used in User]]<br />
| width="220" | [[Pages used in A1]]<br />
|}<br />
<br />
Do you plan to conduct a User training or would you like GICHD to conduct a training in your country/region? Then contact your [[Information Management Team | GICHD IM advisor]].<br />
<br />
We have developed a standard set of User training material in English that we may share with you.</div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=File:Overview_IMSMA_to_MINT.png&diff=24449File:Overview IMSMA to MINT.png2020-02-20T19:48:54Z<p>Alnaucler: Alnaucler uploaded a new version of File:Overview IMSMA to MINT.png</p>
<hr />
<div></div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=File:Overview_IMSMA_to_MINT.png&diff=24448File:Overview IMSMA to MINT.png2020-02-20T19:47:36Z<p>Alnaucler: Alnaucler uploaded a new version of File:Overview IMSMA to MINT.png</p>
<hr />
<div></div>Alnauclerhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Create_iReport_Templates_with_Subreports&diff=24447Create iReport Templates with Subreports2020-02-20T19:32:19Z<p>Alnaucler: </p>
<hr />
<div>{{TOC right}}<br />
==Creating Subreports==__NOEDITSECTION__<br />
A subreport is a report within a report; thus, providing a way to generate a report that includes data on the target IMSMA item as well as data on other IMSMA items that are associated to the target IMSMA item. Generally a subreport is used in a situation where you have one or more sets of data relating to a single IMSMA item. A common use case would be a Location report with multiple details bands of different IMSMA items (Land, Activity, Accident, Victim, Education, and QM).<br />
<br />
Regardless of what IMSMA data you’re including in your report and subreports, there are 5 basic steps to create a report with subreports:<br />
:Step 1 – Create the main report<br />
:Step 2 – Add a subreport to the main report<br />
:Step 3 – Add a parameter to the subreport<br />
:Step 4 – Define the report query for the subreport<br />
:Step 5 – Add subreport parameter to the main report<br />
<br />
====Step 1 – Create the Main Report====__NOEDITSECTION__<br />
<br />
Before creating the main report, you will need to determine what data should be included in your report. For example, if you are creating a report about Land with all the Progress Report data, then the target IMSMA item for your main report should be Land and the target data for your subreport should be Activity assuming that Progress Reports are entered into the system as Activity. Below is a list of questions and things to be considered when designing a report.<br />
*What are all the data to be included on the report?<br />
*What is the target IMSMA item for the main report? This is the primary data of your report.<br />
*What is the target IMSMA item for the subreports? This is the secondary data of your report.<br />
*Determine the relationship between the primary data and the secondary data. How did they get reconciled to one another? How are they linked?<br />
<br />
The main report should be created with the IMSMA item determined to be the primary data of your report. The main report is just a basic report and can be created using the steps provided in the [[Create a Basic iReport Template]] section.<br />
<br />
====Step 2 – Add Subreport to the Main report====__NOEDITSECTION__<br />
<br />
Once the main report has been created you can add a subreport to the main report. The intent of the subreport is to bring data from a different but related datasource into the main report. For example, you could include Activity data on a report about Land. Below are the instructions to create a subreport:<br />
<br />
# On the main report, from the '''Palette''' pane, select '''Subreport''' and drag it to the desired band on the iReport template (normally this is the '''Detail''' band).<br />
#:[[Image:IReportSubReportPalette.png|center|300px|''Subreport Palette'']]<div align="center">''Subreport Palette''</div><br />
# Release the button and the window below displays.<br />
#:[[Image:IReportSubReport1.png|center|500px|''Add Subreport to the Main report'']]<br />
# Click '''Next''' to define a new subreport unless you have an existing report that you would like to use for subreport.<br />
# Select the desired iReport Template to apply (Blank is recommended).<br />
#:[[Image:IReportSubReport2.png|center|500px|''Select the desired iReport Template'']]<br />
# Select from the '''Connection/Data Source''' list. This should be the IMSMA item determined as the secondary data of your report. For example, if you are creating a report about Land with Progress Reports, then “Hazard Reduction” should be the data source for the subreport. Click Next.<br />
#:[[Image:IReportSubReport3.png|center|500px|''Select the desired datasource'']]<br />
# Select the attributes to be included in your subreport. Click '''Next'''.<br />
#:[[Image:IReportSubReport4.png|center|500px|''Select the desired fields for the subreport'']]<br />
# Select the fields to group by. This step is not required. Click '''Next'''.<br />
#:[[Image:Subreport_Group_by.png|center|500px|''Select the fields to group by'']]<br />
# Enter a name for the subreport or use the default. Choose '''Next'''.<br />
#:[[Image:IReportSubReport5.png|center|500px|''Enter a name for the subreport'']] <br />
# Select '''Use the same connection used to fill master report'''. Click Finish. <br />
#:[[Image:IReportSubReport6.png|center|500px|''Use same connection'']] <br />
# The subreport displays.<br />
<br />
====Step 3 – Add Parameter to Subreport====__NOEDITSECTION__<br />
<br />
To connect a subreport to the main report, we next need to create a parameter for passing the identification (guid) of the primary IMSMA item between the subreport and the main report. In the '''Report Inspector''' on the subreport, [[Modify an iReport Template#Adding a Parameter to an iReport Template|add a Parameter]] to hold the guid of the IMSMA item on the main report. It is recommended to add a fairly generic parameter name such as ''ItemGUID'' so that the subreport can be more easily re-used.<br />
<br />
# From the Report Inspector, '''right click''' on the '''Parameter''' tree and choose '''Add Parameter'''.<br />
#: [[Image:IReport AddParameter1.png|center|250px|''Add Parameter'']]<br />
# In the '''Properties''' pane, enter a parameter name (e.g. ItemGUID} and edit any other properties. Normally it is not required to edit anything other than the name, you might however want to deselect the '''Use as a prompt''' option.<br />
#: [[Image:IReport AddParameter2.png|center|250px|''Add Parameter'']]<br />
# Once the parameter is added it will be available in the '''Report Inspector''' and can be referenced as ''$P{parametername}''. For example:<br />
$P{ItemGUID}<br />
<br />
====Step 4 – Define Report Query for Subreport====__NOEDITSECTION__<br />
<br />
The next step is to create a report query for the subreport you just created in Step 2 to define how the IMSMA item on the main report is related to the IMSMA item on the subreport. Typically the subreport report query will receive the guid from the main report via the parameter created in Step 3 and then use it to limit items in the subreport to those linked to the main report. Below is the instructions on how to define the report query:<br />
<br />
# Open the [[Modify an iReport Template#Using Report Query filters|report query window]].<br />
# From the report query window, select '''ImsmaQuery''' from the query language list.<br />
# Enter a report query filter using the parameter defined above to limit the objects according to the main report object. The most common report query filter would be to filter to only linked objects. For example '''''links.toGuid="$P{ItemGUID}"'''''. In this step, the Report Query tells the subreport to return only rows that are linked to the guid of the item in the main report via the link table. Other combinations of report query filters can be used on subreports beyond the link table. These are documented in the [[#Example Subreport Relationships|Possible Subreport Relationships]] section below.<br />
# Click '''OK'''. The report query window closes. <br />
# Save the subreport.<br />
<br />
====Step 5 – Link the Subreport to the Main Report====__NOEDITSECTION__<br />
Now that both the main and the subreport are ready, the only thing that remains to be done is linking the two together. Below are the instructions to link the two reports:<br />
# Make sure you are at the main report by selecting the name of the main report from the tabs at the top of the iReport Designer canvas pane.<br />
# Select the subreport box within the main report.<br />
#: [[Image:IReportSubReportSelection.png|center|500px|''Select the Subreport on the main report'']]<div align="center">''Select the Subreport on the main report''</div><br />
# On the '''Properties''' pane for the Subreport, select the '''Parameter''' selector.<br />
#: [[Image:IReport_SubReportProperties.png|center|200px|''Subreport properties'']]<div align="center">''Subreport properties''</div><br />
# '''Add''' a parameter and type '''exactly the name of the subreport parameter created in step 3''' (e.g. ''ItemGUID'')<br />
#: [[Image:IReport_SubReportParameter.png|center|200px|''Add a parameter'']]<div align="center">''Add a parameter''</div><br />
# For the '''value expression''', select the appropriate field to include in the parameter. '''Normally this is ''$F{guid}''''' but other choices are available.<br />
#: [[Image:IReport_SubReportParameter2.png|center|200px|''Select the appropriate field'']]<div align="center">''Select the field to include in the parameter''</div><br />
# Click '''OK''' and close Subreport Parameters window.<br />
<br />
You are now ready to run your main report. Running (i.e. previewing) the main report will automatically run the subreport(s) as well, and the data from the main as well as from the subreport(s) will be included in the output.<br />
<br />
==Kinds of Subreports==__NOEDITSECTION__<br />
There are three main kinds of relationships in IMSMA on which subreports can be generated from IMSMA data. These are:<br />
*Location relationship<br />
*Link relationship<br />
*Geospatial relationship<br />
*Other relationship<br />
<br />
===Location relationship subreports===__NOEDITSECTION__<br />
Because each of the main items in {{IMSMANG}}, Accident, Activity, Assistance, Education, Land, QM, and Victim, must be reconciled to a Location during the data entry phase, each of these objects has a relationship with Location and can thus be a subreport on a Location main report. Since all accidents, land, activities, educations, QMs, assistances, and victims are associated with a single location each record knows what location it is related to based on the '''''location guid''''' field. When creating a report where the main report is a Location and the subreport is one of the associated objects the Location's guid is passed to the subreport in a parameter and the subreport can use a special ImsmaQuery language syntax to limit the subreport data to those associated with the main report's location:<br />
location.guid = "$P{parametername}"<br />
<br />
The location guid field in the subreport item table contains the guid of the location to which the item record is associated. The figure below 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.<br />
<br />
[[Image:iRep14.png|center|500px|''location_guid example'']]<br />
<div align="center"><br />
''location_guid example''<br />
</div><br />
<br />
To create a subreport using the Location relationship:<br />
# From the main "Location" report, pass the location '''''guid''''' to the subreport in a parameter (e.g. in a parameter called '''ItemGUID''').<br />
# Create a parameter on the subreport with the same name as in #1.<br />
# In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax<br />
location.guid="$P{parametername}"<br />
<br />
This has the effect of limiting the subreport records to '''only those records that are associated to the location''' from the main report.<br />
<br />
===Link relationship subreports===__NOEDITSECTION__<br />
In addition to the Location relationship, the main items in {{IMSMANG}} can also be linked with one another during the reconciliation process. This is how, for example, Activities are linked with Land in the {{IMSMANG}} database. Accidents, land, activities, educations, assistances, 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. This special relationship can also be modeled in iReport using a report and subreport(s).<br />
<br />
The process for creating a report on an item and its linked items is similar to the process for creating a report on items with a Location relationship. The item in the main report is the primary item for which you would like to find linked items. The subreport would return the records for the particular item that is linked to the primary item. The key difference is the query used in the subreport.<br />
<br />
To create a subreport using the link relationship:<br />
# From the main report, pass the '''''guid''''' of the main report object to the subreport in a parameter (e.g. pass an accident's '''''guid''''' in a parameter called '''ItemGUID''').<br />
# Create a parameter on the subreport with the same name as in #1.<br />
# In the subreport for the related item (e.g. a Victim) use the parameter in the following ImsmaQuery language syntax<br />
links.toGuid="$P{parametername}"<br />
<br />
This has the effect of limiting the subreport records to only those records that have a '''link''' to the guid or object passed from the main report.<br />
<br />
===Geospatial relationships===__NOEDITSECTION__<br />
In addition to Location and Link relationships, many objects in IMSMA can store geospatial/geographic information (i.e. point/polygon information). This relationship with the geospatial data can be modeled in a report/subreport relationship for any item that has geospatial information associated with it. To include point/polygon information on an object's main report, follow 3 basic steps:<br />
<br />
*Step 1: Create a main report for an object with geospatial info<br />
*Step 2: Create a GeospatialInfo subreport on the main report, i.e. a report using the GeospatialInfo datasource<br />
*Step 3: Create a Geopoint subreport on the GeospatialInfo report, i.e. a report using the Geopoint datasource<br />
<br />
Step 1: Create a main report for an object with geospatial info<br />
* Create a main report with an object that has geospatial information (e.g. Land).<br />
* Ensure that the '''''geospatialInfos''''' field is added to the main report.<br />
<br />
Step 2: Create a GeospatialInfo subreport on the main report<br />
* On the main report, add a subreport using the '''GeospatialInfo''' datasource<br />
* Pass the '''''geospatialInfos''''' field to the subreport in a parameter (e.g. GeospatialInfoList). '''Note:''' instead of passing the '''''$F{guid}''''' field to the parameter, the parameter value should be '''''$F{geospatialInfos}'''''<br />
* In the GeospatialInfo subreport use the parameter in the following ImsmaQuery language syntax<br />
guid IN $P{parametername}<br />
<br />
Step 3: Create a Geopoint subreport on the GeospatialInfo report<br />
* On the Geospatialinfo subreport, add a subreport using the '''Geopoint''' datasource<br />
* Pass the '''''guid''''' field to the subreport in a parameter (e.g. GeospatialGUID). '''Note:''' Pass the '''''$F{guid}''''' field '''NOT''' the '''''$F{geospatialInfos}''''' value.<br />
* In the Geopoint subreport use the parameter in the following ImsmaQuery language syntax<br />
geospatialinfoguid IN $P{parametername}<br />
<br />
This has the effect of limiting the Geospatial records to only those records whose guid is linked to the geospatialinfo of the main report. This is an example of nested reports, i.e. a main report, a subreport, and a sub-subreport.<br />
<br />
===Other subreport relationships===__NOEDITSECTION__<br />
Certain items in {{IMSMANG}} have subsets of data that are contained within them. For example, an education may have education details such as the education type, total audience, and percentage of women and men. Examples of other subreport relationships include:<br />
<br />
<center><br />
{| class="wikitable" width="600"<br />
|-<br />
| align="center" colspan="2" | '''Other subreport relationships'''<br />
|-<br />
| width="150pt" | '''Parent item'''<br />
| width="450pt" | '''Child item(s)'''<br />
|-<br />
| Activity || Activity Device<br />
<br />
Impact survey<br />
<br />
Interviewee<br />
<br />
Question<br />
<br />
|-<br />
| Education || Education details<br />
|-<br />
| Victim || Received Education<br />
<br />
Needs Assessment<br />
<br />
Cause<br />
<br />
|-<br />
| Land || Land Device<br />
|-<br />
| Accident || Accident Device<br />
|-<br />
| Assistance || Assistance Given<br />
|-<br />
| Task || Work Item<br />
|}<br />
</center><br />
<br />
The process for creating a report on a parent item and its children is the same as any other report/subreport relationship. <br />
<br />
===Example Subreport Relationships===__NOEDITSECTION__<br />
{| class="wikitable"<br />
| align="center" style="background:#f0f0f0;"|'''Main Report'''<br />
| align="center" style="background:#f0f0f0;"|'''Subreport can be'''<br />
| align="center" style="background:#f0f0f0;"|'''Value to Pass to Subreport'''<br />
| align="center" style="background:#f0f0f0;"|'''Report Query'''<br />
|-<br />
| Location||Any Item with a Location||location guid||location.guid = "$P{ItemGUID}"<br />
|-<br />
| Any linked item||Any linked Item||Item guid (e.g. Land guid)||links.toGuid="$P{ItemGUID}"<br />
|-<br />
| Activity||Impact survey or Interviewee||Activity guid||hazreduc.guid = "$P{ItemGUID}"<br />
|-<br />
| Interviewee||Question||interviewee guid||interviewee.guid = “$P{ItemGUID}”<br />
|-<br />
| Task||Work Item||Task guid||task.guid = "$P{ItemGUID}"<br />
|-<br />
| Any Item with Geospatial information||GeospatialInfo||geoSpatialInfos||guid IN $P{GeospatialInfoList}<br />
|-<br />
| Geospatial Info||GeoPoint||GeospatialInfo guid||geospatialInfoGuid = "$P{ItemGUID}"<br />
|-<br />
| Any item with devices||Item Device (e.g. AccidentDevice)||Item guid (e.g. Accident guid)||accident.guid = "$P{ItemGUID}" hazard.guid = "$P{ItemGUID}"<br />
|-<br />
| MRE||MREDetail||MRE guid||mre.guid = "$P{ItemGUID}"<br />
|-<br />
| Victim||Needs Assessment||victim guid||victim.guid="$P{ItemGUID}"<br />
|-<br />
| Victim||Cause||victim guid||victim.guid="$P{ItemGUID}"<br />
|-<br />
| Assistance||Assistance Given||victimAssistance.guid||victimAssistance.guid="$P{ItemGUID}"<br />
|-<br />
| Task||Objective||SQL Field list of Objectives||guid IN ($P{SQLList})<br />
|-<br />
| Work Item||Linked Items (Activity, Education, QM, Assistance)||SQL Field list of Items||guid IN ($P{SQLList})<br />
|}<br />
{{NavBox HowTo Standardizing Data Analysis and Information Reporting}}<br />
[[Category:NAA]]</div>Alnaucler