http://mwiki.gichd.org:8090/mediawiki/api.php?action=feedcontributions&user=Daniel&feedformat=atomIMSMA Wiki - User contributions [en]2024-03-29T06:33:26ZUser contributionsMediaWiki 1.28.0http://mwiki.gichd.org:8090/mediawiki/index.php?title=Information_Management_Team&diff=12073Information Management Team2013-12-05T16:19:34Z<p>Daniel: Added links to author categories</p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
| '''Name''' || '''Position''' || '''Thematic area'''|| '''Countries supported''' <br />
|-<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/daniel-eriksson/ Daniel ERIKSSON] || Assistant Director || [[:Category:ERD|IMSMA NG Support]] || -<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/vera-bohle/ Vera BOHLE] || Advisor, Evaluation and Quality Management || Evaluation and Quality Management || -<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/olivier-cottray/ Olivier COTTRAY] || Advisor, Information Management||Information Services Coordinator || Benin, Burundi, Eritrea,Ethiopia, Kenya, Liberia, Rwanda, Sierra Leone, South Sudan, Uganda, Zambia, Zimbabwe<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/inna-cruz/ Inna CRUZ] ||Advisor, Information Management||GIS and Mapping Support || Armenia, Azerbaijan, Cyprus, Georgia, Tajikistan, Turkey, Ukraine, Georgia, ICRC Georgia<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/angela-de-santis/ Angela DE SANTIS] ||Advisor, Information Management || Victim Assistance and Geoportal || Argentina, Chile,Colombia, Ecuador, Nicaragua, Peru, Spain<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/rana-elias/ Rana ELIAS] ||Advisor, Information Management || Wiki, Pedagogical Tools and Methods || Chad, Congo, Côte d'Ivoire, Democratic Republic of the Congo, Egypt, Jordan, Kuwait, Lebanon, Libyan Arab Jamahiriya, Mauritania, Morocco, Oman, Senegal, Sudan, Western Sahara<br />
|-<br />
| Russel GASSER ||Advisor, Quality and Results-based Management Systems || || <br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/ursin-hofmann/ Ursin HOFMANN] || Programme Officer || || -<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/dionysia-kontotasiou/ Dionysia KONTOTASIOU] ||MediaWiki Specialist || || -<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/anne-li-naucler/ Anne-Li NAUCLÉR] ||Software Development Coordinator || Import Scripts and Migrations, Legacy || Cambodia, Iran, Lao People's Democratic Republic, Myanmar, Nepal, Sri Lanka, Thailand, Vietnam<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/halil-radogoshi/ Halil RADOGOSHI] ||Advisor, Information Management ||Novel uses of IMSMA || Guinea-Bissau, Mozambique, Angola <br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/jean-paul-rychener/ Jean-Paul RYCHENER] ||Advisor, Information Management ||Upgrading Your System|| Afghanistan, Iraq, Israel, Mali, Somalia, Syrian Arab Republic, State of Palestine, Yemen<br />
|-<br />
| [http://www.gichd.org/about-gichd/staff-and-organisation-chart/elisabeth-vinek/ Elisabeth VINEK] ||Data Analyst || [[:Category:VIE|Business Intelligence Solutions, Reporting and MINT]] || -<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Core_Design_Concepts&diff=12069Core Design Concepts2013-12-05T16:07:37Z<p>Daniel: Added category</p>
<hr />
<div>[[File:User Window FINAL.png|frame|alt=Elements of the main IMSMA user interface|The [[IMSMA Navigation Window]] displays at the launch of the system.]]<br />
The '''core design concepts''' of IMSMA are the fundamental ideas and values that have driven the development. <br />
<br />
==Usability==__NOEDITSECTION__<br />
Designed with the end user in mind, the IMSMA Navigation Window provides immediate access to the the most commonly used tools including data entry, data validation, data search and reporting. A user can interact with elements of any of the panes and access additional details. The user can browse for more details including past information leading up to the current situation.<br />
<br />
==Flexibility==__NOEDITSECTION__<br />
IMSMA<sup>NG</sup> was designed to be adapted to the reality surrounding it. It provides customisation tools that enable an IMSMA administrator mine action programme to adjust the information management system to meet the needs of the programme. <br />
<br />
===Adaptable data collection forms===__NOEDITSECTION__<br />
The [[Access the Data Entry Form Template Designer Window|Data Entry Form Template Design]] is a tool that allows for the creation of survey ''forms'' or any other form needed to record data on mine action objects and activities. The IMSMA<sup>NG</sup> forms can be created to look like the actual survey forms used in the field for data collection.<br />
<br />
===Report Designer===__NOEDITSECTION__<br />
The report designer is a graphic tool for creating Report Templates. Report templates are saved reports that can be run on the dataset by any user to give statistics or tables of information.<br />
<br />
{{NavBox What is IMSMA}}<br />
[[Category:ERD]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=The_Making_of_IMSMA&diff=12067The Making of IMSMA2013-12-05T16:06:18Z<p>Daniel: Added categories</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 Inc.]]<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. ([[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]]s and [[accident]]s separately. User feedback and lessons learnt are constantly evaluated and compiled by the [[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 Systems refers to older IMSMA versions (V1.x to V3.x) deployed in the field before IMSMA NG.<br />
Support is still being provided to installations that were performed by the GICHD, and which are currently in use for field operations.<br />
New installations can only be done with IMSMA NG, due to the close dependence of the Legacy Systems on Microsoft Office Suite and Windows [[operating system]]s. Read more on [[Upgrading to IMSMA NG]].<br />
Legacy Systems requires a highly standardised and linear [[workflow]]. The workflow is started by the [[Impact Survey]] or other [[Level 1 Survey]], which can produce [[mined area]] reports. [[Technical Survey]] or [[Level 2 Survey]] follows. This produces a [[minefield]] which is addressed by a [[clearance]] which may have associated [[progress report]]s. The process is concluded with a [[Completion report]].<br />
===IMSMA V3===__NOEDITSECTION__<br />
[[IMSMA V3]] was released in 2002 and followed by regular updates over the next couple of years. It presented a complete new software architecture and each update contributed substantially with new added functionalities and greater flexibility. This was a first attempt to move from the original repository database into a more operational management tool for the mine action programmes. The task tracking tool allowed information managers to account for the work accomplished by each organisation. <br />
In addition, IMSMA V3 started embracing professional database platforms such as [[Microsoft SQL Server]] for its technical development. This software improved numerous aspects, from data handling being facilitated through the design of database queries, to installations into a client-server configuration, with an increased number of simultaneous users.<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. IMSMA V2.2 was said to be “significantly better” as it provided among others, a plug-in to ArcVIEW allowing to view information on a map. It was with this newly developed version that IMSMA was adopted by the UN on an international level as the standard for humanitarian demining information.<br />
<br />
{{NavBox What is IMSMA}}<br />
<br />
[[Category:ERD]]<br />
[[Category:History]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Configuration_Options&diff=11267Understanding Configuration Options2013-09-19T15:46:20Z<p>Daniel: </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 Standalone and Client-Server Configuration Options <br />
! Configuration<br />
! Advantages<br />
! Disadvantages<br />
|-<br />
| <b>Standalone</b><br />
|<br />
* Simple to set up and maintain<br />
* Limited IT knowledge required<br />
* Can be upgraded to a networked configuration later<br />
|<br />
* One-at-a-time data access<br />
|-<br />
| <b>Networked</b><br />
|<br />
* Multiple concurrent data access<br />
* Redundancy<br />
|<br />
* Complicated to set up and maintain<br />
* Networked 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 />
{{important| 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 properties-service.xml and gisServer.properties files on the server must be configured. For more information, see the IMSMA 4.0 Installation Guide for a client-server installation. <br />
* The client(s) must be configured to connect to the server. For more information, see the IMSMA 4.0 Installation Guide for a Client-Server Installation. <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, GIS information (points, polygons) will NOT be immediately rendered to all clients. To either post your GIS-related 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 />
<br />
[[Image:Understanding Configuration Options- Client Server Architecture.png|center|500px|''Client-Server Architecture'']]<br />
<div align="center"><br />
''Client-Server Architecture''<br />
</div><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 MySQL 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 MySQL 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 and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS 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 />
{{NavBox Information Management}}<br />
<br />
[[Category:Information management]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=10368Main Page2013-09-12T13:24:33Z<p>Daniel: Improved link</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" 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 [[PostgreSQL]] 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 [[mine action programme]]s as well as networked installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that directly interact with the IMSMA system. This includes an [[Portal:Business Intelligence|online Mine action INTelligence tool]] ([[MINT]]) for advanced analytics and reporting as well more common tools like [[Microsoft Excel]].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is [[Portal:IMSMA_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 [[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" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including English, French and Spanish. There will be more translations available in the future such as Arabic, Russian and Ukranian. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[PostgreSQL]] database engine<br />
* [[JasperReports]] reporting engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=10367Main Page2013-09-12T13:23:40Z<p>Daniel: Wikified more</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" 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 [[PostgreSQL]] 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 [[mine action programme]]s as well as networked installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that directly interact with the IMSMA system. This includes an [[Portal:Business Intelligence|online Mine action INTelligence tool]] ([[MINT]]) for advanced analytics and reporting as well more common tools like [[Microsoft Excel]].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is [[Portal:IMSMA_Administration|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 [[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" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including English, French and Spanish. There will be more translations available in the future such as Arabic, Russian and Ukranian. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[PostgreSQL]] database engine<br />
* [[JasperReports]] reporting engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=10366Main Page2013-09-12T13:03:42Z<p>Daniel: Wikified</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" 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 [[PostgreSQL]] 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 [[mine action programme]]s as well as networked installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that directly interact with the IMSMA system. This includes an online Mine action INTelligence tool ([[MINT]]) for advanced analytics and reporting as well more common tools like [[Microsoft Excel]].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is 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 [[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" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including English, French and Spanish. There will be more translations available in the future such as Arabic, Russian and Ukranian. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[PostgreSQL]] database engine<br />
* [[JasperReports]] reporting engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=10365Main Page2013-09-12T11:25:22Z<p>Daniel: Corrected PostgreSQL</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" 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 [[PostgreSQL]] database engine and a geographic information system (GIS) for displaying information on maps. Its client-server architecture enables stand-alone installations for small [[mine action programme]]s as well as networked installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that directly interact with the IMSMA system. This includes an online Mine action INTelligence tool ([[MINT]]) for advanced analytics and reporting as well more common tools like [[Microsoft Excel]].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is 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 [[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" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including English, French and Spanish. There will be more translations available in the future such as Arabic, Russian and Ukranian. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[PostgreSQL]] database engine<br />
* [[JasperReports]] reporting engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Core_Design_Concepts&diff=10364Core Design Concepts2013-09-12T11:08:22Z<p>Daniel: Renamed top headings</p>
<hr />
<div>[[File:User Window FINAL.png|frame|alt=Elements of the main IMSMA user interface|The [[IMSMA Navigation Window]] displays at the launch of the system.]]<br />
The '''core design concepts''' of IMSMA are the fundamental ideas and values that have driven the development. <br />
<br />
==Usability==__NOEDITSECTION__<br />
Designed with the end user in mind, the IMSMA Navigation Window provides immediate access to the the most commonly used tools including data entry, data validation, data search and reporting. A user can interact with elements of any of the panes and access additional details. The user can browse for more details including past information leading up to the current situation.<br />
<gallery><br />
File:User Items.png|Example how the map pane is continously connected to the other panes<br />
File:User Browse.png|The [[Items Pane]] stores information about mine action objects (dark gray below) and mine action activities (light gray). These are locations, tasks, lands, activities, accidents, victims, education activities and quality management activities.<br />
File:Field Report Template Designer (QRG).png|Interface for creating or editing forms<br />
</gallery><br />
<br />
==Flexibility==__NOEDITSECTION__<br />
IMSMA<sup>NG</sup> was designed to be adapted to the reality surrounding it. It provides customisation tools that enable an IMSMA administrator mine action programme to adjust the information management system to meet the needs of the programme. <br />
<br />
===Adaptable data collection forms===__NOEDITSECTION__<br />
The [[Access the Data Entry Form Template Designer Window|Data Entry Form Template Design]] is a tool that allows for the creation of survey ''forms'' or any other form needed to record data on mine action objects and activities. The IMSMA<sup>NG</sup> forms can be created to look like the actual survey forms used in the field for data collection.<br />
<br />
===Report Designer===__NOEDITSECTION__<br />
The report designer is a graphic tool for creating Report Templates. Report templates are saved reports that can be run on the dataset by any user to give statistics or tables of information.<br />
<gallery><br />
File:Report Templates.png|Report Templates<br />
File:Graphic Display of Data.png|Graphic Display of Data<br />
File:Report Customization.png|Report Customization<br />
</gallery><br />
{{NavBox What is IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=10363Main Page2013-09-12T11:07:33Z<p>Daniel: Rewrote What is IMSMA</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" 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 [[PostGRS]] database engine and a geographic information system (GIS) for displaying information on maps. Its client-server architecture enables stand-alone installations for small [[mine action programme]]s as well as networked installations for large programmes with many users distributed across multiple sites and organisations. Additionally, IMSMA can be connected to supporting components that directly interact with the IMSMA system. This includes an online Mine action INTelligence tool ([[MINT]]) for advanced analytics and reporting as well more common tools like [[Microsoft Excel]].<br />
<br />
[[Core Design Concepts|Designed with ''flexibility'' and ''usability'']] at heart, IMSMA is 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 [[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" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including English, French and Spanish. There will be more translations available in the future such as Arabic, Russian and Ukranian. </div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[Postgres]] Database <br />
* [[i-Report]] reporting Engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Configuration_Options&diff=10264Understanding Configuration Options2013-09-09T13:31:59Z<p>Daniel: Added category</p>
<hr />
<div>__NOEDITSECTION__<br />
==Standalone versus Client-Server Configuration==__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 Standalone and Client-Server Configuration Options <br />
! Configuration<br />
! Advantages<br />
! Disadvantages<br />
|-<br />
| <b>Standalone</b><br />
|<br />
* Simple to set up and maintain<br />
* Limited IT knowledge required<br />
* Can be upgraded to a networked configuration later<br />
|<br />
* One-at-a-time data access<br />
|-<br />
| <b>Networked</b><br />
|<br />
* Multiple concurrent data access<br />
* Redundancy<br />
|<br />
* Complicated to set up and maintain<br />
* Networked 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 />
{{important| 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 properties-service.xml and gisServer.properties files on the server must be configured. For more information, see the IMSMA 4.0 Installation Guide for a client-server installation. <br />
* The client(s) must be configured to connect to the server. For more information, see the IMSMA 4.0 Installation Guide for a Client-Server Installation. <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, GIS information (points, polygons) will NOT be immediately rendered to all clients. To either post your GIS-related 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 />
<br />
[[Image:Understanding Configuration Options- Client Server Architecture.png|center|500px|''Client-Server Architecture'']]<br />
<div align="center"><br />
''Client-Server Architecture''<br />
</div><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 MySQL 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 MySQL 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 and reporting tools. Based on ESRI’s ArcGIS Engine, the GIS performs all geospatial calculations including distance/bearing calculation, coordinate conversion and reprojection. The GIS 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 />
{{NavBox Information Management}}<br />
<br />
[[Category:Information management]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_IMSMA_Workflows_and_Business_Rules&diff=10263Understanding IMSMA Workflows and Business Rules2013-09-09T13:31:10Z<p>Daniel: Added category</p>
<hr />
<div>__NOEDITSECTION__<br />
Rather than establishing one workflow that all programmes must use, IMSMA<sup>NG</sup> allows information managers to establish their own programme-appropriate workflows and business rules to better support their specific needs. To document their programme-specific workflows, information managers describe the processes undertaken on each object in IMSMA<sup>NG</sup> and the outputs or products from the processes. Typically, these workflows relate to the various categories of lands and activities, but they can also be applied to other IMSMA<sup>NG</sup> items as appropriate.<br />
<br />
During this step, information managers map the process that each land goes through as it is cleared or its impact is otherwise reduced. Using a combination of the relevant land types, status values and relationships, information managers design an information workflow that will be implemented as standard operating procedures (SOPs) for data entry and analysis. Some programmes may have only one process for all categories of lands while other programmes may have three or more processes.<br />
<br />
===Mapping the Workflow===__NOEDITSECTION__<br />
The first element of mapping the activity workflow is to build a map of the relationship between the objects and processes involved in the activity. Starting with the first representation of the land, the workflow map should describe the processes done to the land and the output of the process. The workflow map should trace the entire process from land identification through clearance and release of the land according to the operational process in use in the programme. In the example below, a confirmed hazardous area (CHA) is linked to a technical survey that was conducted on the land. The survey resulted in a minefield on which a clearance was done, and the clearance resulted in a cleared land. Finally, a completion survey was logged to close the land.<br />
<br />
<br />
[[Image:Understanding Mine Action Information Management - Mapping workflow.png|center|''Mapping the Workflow'']]<br />
<div align="center"><br />
''Mapping the Workflow''<br />
</div><br />
<br />
<br />
This workflow map identifies the activity that is used within the programme and can be mapped in IMSMA<sup>NG</sup> to track the clearance of lands. Because IMSMA<sup>NG</sup> supports customisable workflows, it can be used to track different workflows for different objects. For example, a programme may have a separate abbreviated workflow for spot UXO tasks that involve only the identification of the UXO hazard (object) and a clearance of the land (process) without additional surveys or steps. This process should also be mapped for implementing in IMSMA<sup>NG</sup>.<br />
<br />
===Business Rules Updating Structure===__NOEDITSECTION__<br />
====Status Changes====__NOEDITSECTION__<br />
<br />
Along with a workflow map that describes the relationship between the various types of objects and processes in a workflow, the status changes or outputs from the process are critical in adequately mapping the land clearance process. IMSMA<sup>NG</sup> uses the status value of items to track where the object or process is in its workflow. Objects and processes in IMSMA<sup>NG</sup> can have different status values. For example, lands can be defined as "Active", "Worked On," or "Closed," while activities that are more process-oriented can be "Planned," "Ongoing," "Completed," "Suspended," or "Aborted." Defining a set of status values for each item provides the capability to:<br />
<br />
* manage workflows according to status<br />
* search and report on items based on a particular status<br />
* display items on the map with different symbols based on their status<br />
<br />
Some IMSMA<sup>NG</sup> items may have many status values. For example, process-oriented items such as activities and quality management likely have many status values, but lands and other object- or output-oriented items typically have only the three status values listed above. Some items like victims and accidents may not need status values depending on how information is used. Defining the possible status values for each object in the workflow as outputs of the processes conducted on them provides a set of business rules for information management that govern how information should be entered and analysed.<br />
<br />
====Example Workflows with Status Changes====__NOEDITSECTION__<br />
The following figures show how each programme can tailor the system to support a specific land clearance/activity workflow process for each type of land, from a traditional process for minefield clearance with multiple steps including a technical survey, clearance and completion survey to a simplified process for UXO clearance that includes only a clearance. Each example involves a single land on which one or more activities are conducted. At each step, information about the land's status and type is updated as a result of the activity.<br />
<br />
In the figure below, a CHA is created and its status is set to "Active." A technical survey process is then conducted on the land, which results in changing the subcategory of the land from "CHA" to "Minefield" and defining the land's perimeter. Next, a clearance process is conducted on the minefield that results in updating the status of the land to "Worked On." Finally, a completion survey is submitted that updates the status of the land to "Closed."<br />
<br />
<br />
[[Image:Understanding Mine Action Information Management - Example Workflow.png|center|''Example of a Traditional Workflow'']]<br />
<div align="center"><br />
''Example of a Traditional Workflow''<br />
</div><br />
<br />
<br />
Simpler processes can be defined for other types of lands. For example, a spot UXO task would likely not go through this complete workflow and instead start with a subcategory of "UXO" and a status of "Open." A clearance could then be conducted and the UXO spot status updated to "Closed," without requiring a completion survey.<br />
<br />
<br />
[[Image:Understanding Mine Action Information Management - Example Workflow 2.png|center|''Example of a Spot UXO Workflow'']]<br />
<div align="center"><br />
''Example of a Spot UXO Workflow''<br />
</div><br />
<br />
<br />
By documenting the entire process conducted on each type of land, including the changes in status and type that result from activities, information managers create a complete map of the land/activity workflow that informs how linking and reconciliation decisions should be made and provide a guide to data entry personnel.<br />
<br />
===Progress Reporting Structure===__NOEDITSECTION__<br />
Once the land/activity relationships and workflow are defined and documented for each type of land, the next step is to define how progress data for the land clearance processes is collected. Traditionally, incremental progress data is collected using progress reports. These reports are typically linked to the overall clearance operation and are used to collect the incremental progress for a reporting period, usually, the number of mines/UXO cleared, area cleared and hours worked. In IMSMA<sup>NG</sup>, each progress report is stored as a new activity and linked to the clearance. As a result, individual progress reports can be queried to determine how much progress was made during a given reporting period. In addition, aggregate progress information can be queried for each clearance (for example, the total mines that have been reported cleared for a given clearance operation).<br />
<br />
An alternative approach to storing progress information is to collect incremental progress reports and reconcile them as updates to the clearance using the combine option during reconciliation. Using this method, progress reports do not create independent activity items; rather, their information is combined with, and added to, the clearance information collected to that point. This approach simplifies the reconciliation step for progress reports as well as provides a simple summary of clearance data on each land in the Summary. It may, however, become slightly more complicated to determine progress during individual reporting periods. Information managers should assess which approach better meets the needs of their programs when selecting an approach to tracking progress.<br />
<br />
In the example below, progress reports were collected for three separate reporting periods during a clearance operation. Collecting and linking information in this way makes it easy to determine that in Period 2 (PR-2), 4,500 sqm were cleared and 25 AP mines were found and that, overall, 15,000 sqm were cleared and 61 AP mines were found. A defined, standardized approach to collecting and storing progress information simplifies querying and reporting of statistical information and is a critical element to supporting operational mine action information management needs.<br />
<br />
<br />
[[Image:Understanding Mine Action Information Management - Progress Report Workflow.png|center|''Progress Report Workflow'']]<br />
<div align="center"><br />
''Progress Report Workflow''<br />
</div><br />
<br />
<br />
{{Document|<b>Document the following decisions about information workflows and business rules:</b><br />
<br />
* Workflow process for each land type including which processes or activities are done on which types<br />
* Outputs or results of activities on lands including the resulting status and type changes<br />
* Progress tracking process<br />
}}<br />
<br />
{{NavBox Information Management}}<br />
<br />
[[Category:Information management]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_IMSMA_Information_Model&diff=10262Understanding IMSMA Information Model2013-09-09T13:30:12Z<p>Daniel: Added category</p>
<hr />
<div>{{TOC right}}<br />
Most important information management concepts key to understand the IMSMA<sup>NG </sup> information model and their impact on information management are covered here. To help information managers apply the concepts, some sections conclude with a list of requirements to define and document that can be used when establishing the information model for a programme.<br />
<br />
==Data Types==__NOEDITSECTION__<br />
===Core Data===__NOEDITSECTION__<br />
In the IMSMA<sup>NG</sup> information model, items are the containers for core data, such as mine action data. An item is an area, activity or event that a programme records information about and stores in IMSMA<sup>NG</sup>. There are six categories of items, which are described in the table below. Each category can be characterized by a type that reflects whether the item is designed to track process or activity information or the object or product of an activity.<br />
<br />
<br />
{| class="wikitable"<br />
|+ Items<br />
! Item<br />
! Description<br />
! Type<br />
|-<br />
| Land<br />
| Information about an area<br />
| Object/Product<br />
|-<br />
| Activity<br />
| Information about an activity, such as efforts to survey, clear, or reduce the threat of a hazard<br />
| Process/Activity<br />
|-<br />
| Accident<br />
| Information about an accidental event<br />
| Object/Product<br />
|-<br />
| Victim<br />
| Information about a person injured or affected by an accident<br />
| Object/Product<br />
|-<br />
| Education activity<br />
| Information about an activity designed to inform or educate people, such as about local hazards<br />
| Object/Product<br />
|-<br />
| Quality Management (QM) activity<br />
| Information about an quality-improvement activity, such as an effort to control and monitor the clearance and/or reduction of lands or activities<br />
| Object/Product<br />
|-<br />
|}<br />
<br />
<br />
Items are entered into IMSMA<sup>NG</sup> by means of a Data Entry Form. Typically, each category of items has its own Data Entry Form template for recording information specific to that category. When entered into IMSMA<sup>NG</sup>, all Data Entry Form items must be assigned to a location, which is tied to the country’s gazetteer, or political or administrative structure. The items can then be traced back to the country structure so that users can easily report data such as the number and size of hazardous areas within a particular province.<br />
<br />
Part of defining and documenting an information model includes defining the useful information attributes for each IMSMA<sup>NG</sup> item. IMSMA<sup>NG</sup> comes with more than 1,000 data elements already defined as well as the capability to create additional custom-defined fields (CDFs). This makes it important to critically assess which data elements are useful to a programme for decision-making, analysis and reporting and to focus on those while ignoring data elements that don’t provide additional value. Limiting information to only that which is useful to the programme provides long-term benefits including reducing the data collection and data entry burden and improving system performance. And, while many data elements may be collected for each IMSMA<sup>NG</sup> item, some elements may be more important for analysis than others. For example, whether a victim has been injured or killed may be more important for analysis than the victim’s nationality.<br />
<br />
<br />
{| class="wikitable"<br />
|+ Item Subcategories<br />
! Item<br />
! Subcategory Examples<br />
|-<br />
| Land<br />
|<br />
* Battle area<br />
* Dangerous area<br />
* Minefield<br />
* CHA<br />
* UXO spot<br />
|-<br />
| Activity<br />
|<br />
* Clearance<br />
* Completion survey<br />
* Technical survey<br />
* Progress report<br />
|-<br />
| Accident<br />
|<br />
* Demining accident<br />
* Mine accident<br />
|-<br />
| Victim<br />
|<br />
* Civilian<br />
* Deminer<br />
|-<br />
| Education activity<br />
|<br />
* Peer-to-peer<br />
|-<br />
| Quality Management (QM) activity<br />
|<br />
* Quality management<br />
* Quality control<br />
|-<br />
|}<br />
<br />
<br />
Each of the six categories of items can be divided into subcategories or types so users can collect information for each subcategory. For example, users can specify different types of lands such as dangerous areas, confirmed hazardous areas (CHAs), minefields and battle areas and manage each kind of land differently. Using subcategories, information managers can:<br />
<br />
* create separate workflows for each type of land<br />
* create and manage separate data entry forms<br />
* differentiate between item categories on the map<br />
<br />
Additionally, information managers can customise the subcategories so that unused subcategories can be removed and other subcategories added. The same is true for all top-level items within IMSMA<sup>NG</sup>, which lets information managers specify their exact information model, including the relationships among item categories, and adjust the model as their needs change over time. To accurately map the information model for a programme, it’s helpful to evaluate the available item subcategories and determine if changes to the information model in IMSMA<sup>NG</sup> are required. While these values can be customized after system setup, understanding the types of information for each item is critical to implementing an effective workflow in IMSMA<sup>NG</sup>. Table 5 shows examples of the possible subcategories of IMSMA<sup>NG</sup> items.<br />
<br />
<br />
{{Document|<b>Document the following decisions about items:</b><br />
<br />
* data elements to be collected and managed in IMSMA<sup>NG</sup><br />
* data elements that are not predefined in IMSMA<sup>NG</sup> and should be created as CDFs<br />
* particularly important, or key, data elements for the programme<br />
* relevant subcategories for each item<br />
* status values for each item<br />
}} <br />
<br />
<br />
Below is an example of a fully-documented hazard.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Example of Documented Hazard.png|center|500px|''Example of Documented Hazard'']]<br />
<div align="center"><br />
''Example of Documented Hazard''<br />
</div><br />
<br />
===Auxiliary Data===__NOEDITSECTION__<br />
In addition to defining the required information for IMSMA<sup>NG</sup> items, it is important to define the relevant information to be collected about auxiliary data. This includes defining and documenting the [[Setup Country Structure Levels in a New Installation|Country Structure]], [[Access the Explosive Ordnance List Window|Explosive Ordnance]], [[Organisation List window|Organisation]] and [[Place List window|Place]], such as military bases, hospitals and cultural sites; any additional CDFs that should be created; and any subcategories for each of the auxiliary data types.<br />
<br />
<br />
{{Document|<b>Document the following decisions about auxiliary data:</b><br />
<br />
* data elements to be collected and managed in IMSMA<sup>NG</sup><br />
* data elements that are not already configured in IMSMA<sup>NG</sup> and can be created as CDFs<br />
* relevant subcategories for each data type<br />
}} <br />
<br />
<br />
Below is an example of a fully-documented place.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Example of Documented Auxiliary Data.png|center|500px|''Understanding IMSMA Information Model - Example of Documented Auxiliary Data'']]<br />
<div align="center"><br />
''Understanding IMSMA Information Model - Example of Documented Auxiliary Data''<br />
</div><br />
<br />
==Data Entry Forms and Summaries==__NOEDITSECTION__<br />
A <b>Data Entry Form</b> is a data entry form used to record and store information about an item.<br />
<br />
A <b>Summary</b> is a summary of all the information collected about an item on Data Entry Forms.<br />
<br />
<b>Reconciliation</b> is the process of assigning the information in a Data Entry Form to an existing item or creating a new item/Summary.<br />
<br />
All information is entered into IMSMA<sup>NG</sup> via a Data Entry Form, a data entry form used to collect information about an item. When a Data Entry Form is completed, it is either reconciled to an existing item (that is, it is determined to be information about an item that already exists in IMSMA<sup>NG</sup>) or it is reconciled as new (that is, it is determined to be information about an item that does not already exist in IMSMA<sup>NG</sup>).<br />
<br />
With this approach, users can collect and store multiple Data Entry Forms about the same item over time so that the entire history of the item is preserved in the system. The approach also provides a complete audit trail of all changes made to any information so that information managers can answer the question, "What did we know and when did we know it?"<br />
<br />
IMSMA<sup>NG</sup> also provides a constantly updated Summary of the item which represents the sum of information about the item at any given time. As subsequent information is collected about a specific attribute of an item, IMSMA<sup>NG</sup> updates the item’s Summary on an attribute-by-attribute basis. For example, Data Entry Form #1 collects some initial information about a hazardous land area. It sets the priority to "Medium" and specifies that the land contains AP mines and is 25,000 sqm. Data Entry Form #2 updates information about the land area after a subsequent assessment. The report sets the priority to "High" and specifies the presence of AP and AT mines, but it does not change the size or the status of the land area. Data Entry Form #3 updates the land area's size and status after clearance operations are complete. The figure below shows how the land area's Summary is updated after all three reports are entered into the system.<br />
<br />
[[Image:Understanding_IMSMA_Information_Model_-_Updating_CVs.png|center|500px|''Example of Updating Summaries'']]<br />
<div align="center"><br />
''Example of Updating Summaries''<br />
</div><br />
<br />
Summary calculations are based on the date of the Data Entry Form, so it is possible to enter data into the system out of chronological order (that is, to collect past information about an item) without disrupting the Summary. For example, if a fourth Data Entry Form were collected and dated between Data Entry Form #1 and Data Entry Form #2, it would have no effect on the Summary as all information in the example was updated with Data Entry Form #2 or later.<br />
<br />
===Location Folder===__NOEDITSECTION__<br />
A location in IMSMA<sup>NG</sup> is a grouping of information, whether logical, geographical or sociopolitical. Using locations, users can group data that belongs together or is associated with each other and handle it as a group, including facilitating data entry, searching and running reports. To do this, locations must link the data to the country’s political or administrative structure (existing gazetteer), whether at the province, district or town level. This method also provides geographical context to the data. As shown in the figure below, locations in IMSMA<sup>NG</sup> are governed by two simple rules:<br />
<br />
*all data must be linked to a location<br />
*all locations must be linked to the country structure<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Using Locations to Link Mine Action Data to the Country Structure.png|center|''Using Locations to Link Mine Action Data to the Country Structure'']]<br />
<div align="center"><br />
''Using Locations to Link Mine Action Data to the Country Structure''<br />
</div><br />
<br />
<br />
Two fundamental decisions to make when customizing IMSMA<sup>NG</sup> is to decide what country structure level locations will be consistently linked to and what concept locations will represent. Typical concepts that a location is used to represent include:<br />
<br />
*a work area (where activities are taking place)<br />
*a community (a group of people affected by the mine/UXO threat)<br />
*the nearest town (the town closest to where the activity is taking place)<br />
<br />
{{Document|<b>Document the following decisions about locations:</b><br />
<br />
* what concept locations will represent<br />
* what country structure level locations will be linked to<br />
}} <br />
<br />
<br />
===Assigning and Linking===__NOEDITSECTION__<br />
<b>Assigning</b> refers to the assignment of an item to a location for the purposes of grouping information. All items must be assigned a location.<br />
<br />
<b>Linking</b> refers to the association between items for the purposes of analysis. Linking is optional, for example, when linking clearances to minefields.<br />
<br />
IMSMA<sup>NG</sup> provides the capability to assign items to locations and create links between items, a function that shows the relationships between items and processes and that enriches the data collected. Assignments and links are defined during the Data Entry Form approval process. An item is assigned to one location, which ties the item to the country structure and allows for reporting data by area. The same item can then be linked to as many other items as necessary. In this way, IMSMA<sup>NG</sup> supports the idea of linking activities to lands, victims to accidents or any item to any other item. When used with item subcategories, linking adds a powerful capacity to implement an information workflow and create rich and useful data for decision makers. To ensure the integrity of this data, system administrators must clearly specify the kinds of links to track in IMSMA<sup>NG</sup>.<br />
<br />
The example below shows how users can build a workflow of complex relationships among top-level items and item subcategories to model the information management process for their programmes.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Example of How Relationships Among Items are Created.png|center|400px|''Example of How Relationships Among Items are Created'']]<br />
<div align="center"><br />
''Example of How Relationships Among Items are Created''<br />
</div><br />
<br />
<br />
The next figure shows how the Summary changes with each activity that is linked to the original land. The CHA starts with a status of "Open." When the technical survey is linked to the land, it changes the landsubcategory to "Minefield." Then, linking the clearance updates the land's status to "Worked On." Finally, linking the completion survey changes the land's status to "Closed." The result is one land whose information is updated over time by the four activities linked to the land. This way to track information can be used to represent the information management process and status rules accurately for a land release, risk management or other process model.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Example of How Current View Statuses Change.png|center|400px|''Example of How Summary Statuses Change'']]<br />
<div align="center"><br />
''Example of How Summary Statuses Change''<br />
</div><br />
<br />
<br />
The IMSMA<sup>NG</sup> information model is flexible enough for each programme to customise the system to support its needs. For example, programmes that do not conduct education activities do not need to complete information about education activities, and they still retain full utility of the system. Similarly, programmes that conduct victim tracking and education activities only can disregard lands and activities without any loss of utility. This flexibility, however, requires that programmes define the relevant uses of each item.<br />
<br />
Although any item can be linked to any other item, not all relationships necessarily make sense for every programme. The diagrams below describe some of the more common logical relationships among items and can serve as the basis for an information model when implementing IMSMA<sup>NG</sup>.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Example Relationships Among Items.png|center|400px|''Example Relationships Among Items'']]<br />
<div align="center"><br />
''Example Relationships Among Items''<br />
</div><br />
<br />
<br />
The rationale for each relationship or link should also be documented so the meaning is understood. For example, an activity may be conducted on a land and an accident may be a result of a hazardous land or produce a victim. These relationships are used when entering data to ensure that the links between items are available for searching and reporting, like when searching for all lands that have clearances linked to them.<br />
<br />
{{Document|<b>Document the following business rules about assigning and linking:</b><br />
<br />
* which items will have links between them, for example, victims will always be linked to accidents<br />
* rationale or logical meaning of the relationships between items, for example, a link between a clearance and a minefield means that the clearance was conducted on the minefield<br />
* what effects linking has on the items, for example, a link between a clearance and land may indicate that the land status should change from "Open" to "Worked on"<br />
}} <br />
<br />
<br />
<br />
===The Workbench===__NOEDITSECTION__<br />
Items, Data Entry Forms, Summaries, assigning and linking come together at the Workbench. The Workbench is a holding area where users enter data into Data Entry Forms and reconcile each item in the Data Entry Form either as a new item or as an update to an existing item. Users have the ability to assign Data Entry Form items to locations and to link items to other items (like linking a technical survey to an existing CHA). They then save the reports in the Workbench pending the appropriate quality checks and approvals.<br />
<br />
Until a Data Entry Form is approved, it exists only in the Workbench and does not update any Summaies. The report can still be modified or deleted. When a Data Entry Form is approved, however, it becomes part of the Summaries and cannot be deleted.<br />
<br />
<br />
[[Image:Understanding IMSMA Information Model - Adding Field Report Information to the Current View.png|center|''Adding Data Entry Form Information to the Summary'']]<br />
<div align="center"><br />
''Adding Data Entry Form Information to the Summary''<br />
</div><br />
<br />
<br />
For data quality purposes, it is important that the data is adequately checked at this stage. IMSMA<sup>NG</sup> allows information managers to control permissions for the Workbench and other areas of IMSMA<sup>NG</sup> through the management of users and roles. With multiple permission levels for the Workbench, different users can be assigned different permissions, allowing programmes to implement a data-entry workflow that distinguishes between data entry and data verification roles. It is recommended to set up a permission structure that reserves approval authority for Data Entry Forms for the most trusted users.<br />
<br />
<br />
{{NavBox Information Management}}<br />
<br />
[[Category:Information management]]</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Mine_Action_Information_Management&diff=10261Understanding Mine Action Information Management2013-09-09T13:29:15Z<p>Daniel: Added category</p>
<hr />
<div>__NOEDITSECTION__<br />
'''Understanding Mine Action Information Management''' is a prerequisite to be a good information manager. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities, planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it definitely is not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.<br />
<br />
==Objects and Processes==__NOEDITSECTION__<br />
In mine action information management, the primary object or focus is contaminated [[land]] and the activities or processes undertaken to reduce or eliminate the contamination in a process called [[land release]]. Other important objects and processes include [[accident]]s, [[victim]]s, [[victim assistance]], [[quality management]] and [[risk education]]. Although it is not the standard situation, these elements may sometimes take the prominent role from the land release process in some mine action programmes. <br />
<br />
The process of clearing hazards follows an operational workflow that is reflected in information management as a set of ''business rules''. As each step in the clearance process is completed, attributes of the hazard change so that the hazard eventually is cleared. It is the role of information management to collect information about each step and accurately report the status and attributes of each hazard as it makes its way through the workflow to assist in operational activities such as planning, tasking and clearance operations. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, the concepts are the same. Hazards are reduced and changed over time by various processes. To implement this effectively in {{IMSMANG}}, information managers must first fully understand the workflow and business rules in use in their programmes.<br />
<br />
==Information management needs assessment==__NOEDITSECTION__<br />
Before setting up {{IMSMANG}}, information managers should have an understanding of the information management needs of their programmes and the workflows that are used. Then they can begin designing the information workflow in {{IMSMANG}} to meet those needs. The table below lists the information management concepts to review along with the possible resources that may be available to help assess the needs.<br />
<br />
{| class="wikitable"<br />
! IM cycle step<br />
! Possible Resources<br />
|-<br />
| '''Data collection'''<br />
* Reports collected from mine action actors<br />
* Existing databases<br />
|<br />
* '''Data collection forms:''' Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in {{IMSMANG}}. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.<br />
* '''Information systems''': Whether databases, spreadsheets or [[GIS]], existing information systems can provide a key source of information requirements for {{IMSMANG}}. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.<br />
* '''Information consumers''': It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing {{IMSMANG}}, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using {{IMSMANG}}.<br />
|-<br />
| '''Information use'''<br />
* Prioritizing<br />
* Tasking<br />
* Operations and planning<br />
| '''Mine action processes''': Assessing existing and planned processes and their required information is a key source of information for this activity and allows the {{IMSMANG}} system to be customized to accurately support these processes. It is important, however, that these processes correspond to the actual operational needs of the mine action programme.<br />
|-<br />
| '''Information dissemination'''<br />
* Monthly progress reports<br />
* Statistical reports<br />
* Treaty obligations reports<br />
| '''Reports''': Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in {{IMSMANG}}.<br />
|}<br />
<br />
[[Category:Information management]]<br />
{{NavBox Information Management}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Mine_Action_Information_Management&diff=10245Understanding Mine Action Information Management2013-09-09T12:22:54Z<p>Daniel: Updated table</p>
<hr />
<div>__NOEDITSECTION__<br />
'''Understanding Mine Action Information Management''' is a prerequisite to be a good information manager. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities, planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it definitely is not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.<br />
<br />
==Objects and Processes==__NOEDITSECTION__<br />
In mine action information management, the primary object or focus is contaminated [[land]] and the activities or processes undertaken to reduce or eliminate the contamination in a process called [[land release]]. Other important objects and processes include [[accident]]s, [[victim]]s, [[victim assistance]], [[quality management]] and [[risk education]]. Although it is not the standard situation, these elements may sometimes take the prominent role from the land release process in some mine action programmes. <br />
<br />
The process of clearing hazards follows an operational workflow that is reflected in information management as a set of ''business rules''. As each step in the clearance process is completed, attributes of the hazard change so that the hazard eventually is cleared. It is the role of information management to collect information about each step and accurately report the status and attributes of each hazard as it makes its way through the workflow to assist in operational activities such as planning, tasking and clearance operations. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, the concepts are the same. Hazards are reduced and changed over time by various processes. To implement this effectively in {{IMSMANG}}, information managers must first fully understand the workflow and business rules in use in their programmes.<br />
<br />
==Information management needs assessment==__NOEDITSECTION__<br />
Before setting up {{IMSMANG}}, information managers should have an understanding of the information management needs of their programmes and the workflows that are used. Then they can begin designing the information workflow in {{IMSMANG}} to meet those needs. The table below lists the information management concepts to review along with the possible resources that may be available to help assess the needs.<br />
<br />
{| class="wikitable"<br />
! IM cycle step<br />
! Possible Resources<br />
|-<br />
| '''Data collection'''<br />
* Reports collected from mine action actors<br />
* Existing databases<br />
|<br />
* '''Data collection forms:''' Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in {{IMSMANG}}. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.<br />
* '''Information systems''': Whether databases, spreadsheets or [[GIS]], existing information systems can provide a key source of information requirements for {{IMSMANG}}. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.<br />
* '''Information consumers''': It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing {{IMSMANG}}, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using {{IMSMANG}}.<br />
|-<br />
| '''Information use'''<br />
* Prioritizing<br />
* Tasking<br />
* Operations and planning<br />
| '''Mine action processes''': Assessing existing and planned processes and their required information is a key source of information for this activity and allows the {{IMSMANG}} system to be customized to accurately support these processes. It is important, however, that these processes correspond to the actual operational needs of the mine action programme.<br />
|-<br />
| '''Information dissemination'''<br />
* Monthly progress reports<br />
* Statistical reports<br />
* Treaty obligations reports<br />
| '''Reports''': Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in {{IMSMANG}}.<br />
|}<br />
<br />
{{NavBox Information Management}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Mine_Action_Information_Management&diff=10243Understanding Mine Action Information Management2013-09-09T12:14:35Z<p>Daniel: Second section edited</p>
<hr />
<div>__NOEDITSECTION__<br />
'''Understanding Mine Action Information Management''' is a prerequisite to be a good information manager. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities, planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it definitely is not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.<br />
<br />
==Objects and Processes==__NOEDITSECTION__<br />
In mine action information management, the primary object or focus is contaminated [[land]] and the activities or processes undertaken to reduce or eliminate the contamination in a process called [[land release]]. Other important objects and processes include [[accident]]s, [[victim]]s, [[victim assistance]], [[quality management]] and [[risk education]]. Although it is not the standard situation, these elements may sometimes take the prominent role from the land release process in some mine action programmes. <br />
<br />
The process of clearing hazards follows an operational workflow that is reflected in information management as a set of ''business rules''. As each step in the clearance process is completed, attributes of the hazard change so that the hazard eventually is cleared. It is the role of information management to collect information about each step and accurately report the status and attributes of each hazard as it makes its way through the workflow to assist in operational activities such as planning, tasking and clearance operations. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, the concepts are the same. Hazards are reduced and changed over time by various processes. To implement this effectively in {{IMSMANG}}, information managers must first fully understand the workflow and business rules in use in their programmes.<br />
<br />
==Information Management Needs Assessment==__NOEDITSECTION__<br />
Before installing {{IMSMANG}}, information managers should have an understanding of the information management needs of their programmes and the workflows that are used. Then they can begin designing the information workflow in {{IMSMANG}} to meet those needs. The table below lists the information management concepts to review along with the possible resources that may be available to help assess the needs.<br />
<br />
{| class="wikitable"<br />
|+ Information Management Needs Assessment <br />
! Information Management Concept<br />
! Possible Resources<br />
|-<br />
| '''Sources of Information'''<br />
* Reports collected from mine action actors<br />
* Existing databases<br />
|<br />
* '''Data collection forms:''' Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in {{IMSMANG}}. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.<br />
* <b>Information systems:</b> Whether databases, spreadsheets or GIS, existing information systems can provide a key source of information requirements for {{IMSMANG}}. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.<br />
* <b>Information consumers:</b> It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing {{IMSMANG}}, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using {{IMSMANG}}.<br />
|-<br />
| <b>Key decisions requiring information</b><br />
* Prioritizing<br />
* Tasking<br />
* Operations and planning<br />
| <b>Mine action processes:</b> Assessing existing and planned processes and their required information is a key source of information for this activity and allows the {{IMSMANG}} system to be customized to accurately support these processes. It is important, however, that these processes map to the actual operational needs of the mine action programme and are not created without relating to operational needs.<br />
|-<br />
| <b>Output reports</b><br />
* Monthly progress reports<br />
* Statistical reports<br />
* Treaty obligations<br />
| <b>Reports:</b> Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in {{IMSMANG}}.<br />
|}<br />
<br />
{{NavBox Information Management}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Understanding_Mine_Action_Information_Management&diff=10236Understanding Mine Action Information Management2013-09-09T11:42:20Z<p>Daniel: Cleaned wiki markup and expanded intro</p>
<hr />
<div>{{TOC right}}<br />
__NOEDITSECTION__<br />
'''Understanding Mine Action Information Management''' is a prerequisite to be a good information manager. The practice of information management in mine action is similar to information management in any other domain. Information managers oversee the collection, processing and analysis of information to support decision making in operational activities, planning and reporting. Information management is not an end in itself. Although archiving is one of the roles of information management, it definitely is not the central role. Rather, information management is an activity that enables evidence-based decision making and increases transparency and accountability. Good information management is a pre-requisite to an effective and efficient mine action organisation.<br />
<br />
==Hazards and Processes==__NOEDITSECTION__<br />
In mine action information management, the primary object or focus is a hazard, whether it is a minefield, UXO spot or other ERW contamination, and the activities or processes undertaken to reduce or eliminate the hazard. Other important objects and activities include accidents, victims, quality management and mine risk education activities. In certain programmes, these elements may take a more prominent role, with {{IMSMANG}} supporting them equally well. However, the traditional focus of information management in mine action is on hazards and the processes done to eliminate them.<br />
<br />
The process of clearing hazards follows an operational workflow that is reflected in information management as a set of business rules. As each step in the clearance process is completed, attributes of the hazard change so that eventually the hazard is cleared. It is the role of information management to collect information about each step and accurately report the status and attributes of each hazard as it makes its way through the workflow to assist in operational activities such as planning, tasking and clearance operations. Whether a programme is implementing a land release model for hazard clearance or a risk reduction model, the concepts are the same. Hazards are reduced and changed over time by various processes. To implement this effectively in {{IMSMANG}}, information managers must first fully understand the workflow and business rules in use in their programmes.<br />
<br />
==Information Management Needs Assessment==__NOEDITSECTION__<br />
Before installing {{IMSMANG}}, information managers should have an understanding of the information management needs of their programmes and the workflows that are used. Then they can begin designing the information workflow in {{IMSMANG}} to meet those needs. The table below lists the information management concepts to review along with the possible resources that may be available to help assess the needs.<br />
<br />
{| class="wikitable"<br />
|+ Information Management Needs Assessment <br />
! Information Management Concept<br />
! Possible Resources<br />
|-<br />
| '''Sources of Information'''<br />
* Reports collected from mine action actors<br />
* Existing databases<br />
|<br />
* '''Data collection forms:''' Programs often have existing data collection forms or spreadsheets that describe what information must be collected from operators or key stakeholders. These forms can serve as the basis for data collection forms in {{IMSMANG}}. It is important, however, to critically assess the information provided by these forms since existing forms may not accurately reflect current data collection needs and may have more information than necessary.<br />
* <b>Information systems:</b> Whether databases, spreadsheets or GIS, existing information systems can provide a key source of information requirements for {{IMSMANG}}. Often, these information systems document the specific information the programs must collect and report on and so serve as a valuable source for detailing information needs.<br />
* <b>Information consumers:</b> It is important to collect information about decisions made in mine action programs by interviewing consumers of information. Often, existing data collection forms, reports and systems do not fully represent the needs of the consumers or users of this information. While implementing {{IMSMANG}}, it is an ideal time to readdress the needs of these information users to determine how additional requirements can easily be met using {{IMSMANG}}.<br />
|-<br />
| <b>Key decisions requiring information</b><br />
* Prioritizing<br />
* Tasking<br />
* Operations and planning<br />
| <b>Mine action processes:</b> Assessing existing and planned processes and their required information is a key source of information for this activity and allows the {{IMSMANG}} system to be customized to accurately support these processes. It is important, however, that these processes map to the actual operational needs of the mine action programme and are not created without relating to operational needs.<br />
|-<br />
| <b>Output reports</b><br />
* Monthly progress reports<br />
* Statistical reports<br />
* Treaty obligations<br />
| <b>Reports:</b> Donor reports, monthly or quarterly reports, statistical reports, reports supporting the Ottawa convention and other reports provide details about information that must be collected and managed in {{IMSMANG}}.<br />
|}<br />
<br />
{{NavBox Information Management}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Pages&diff=10233Pages2013-09-09T11:27:43Z<p>Daniel: Added to intro</p>
<hr />
<div>__NOTOC__<br />
'''Pages''' on the IMSMA Wiki are structured into several headings. The page title is the top Level&nbsp;1 heading displayed above each page's contents. The title indicates what the page is about and is a unique reference to the page. The title may simply be the name of the subject of the page, or it may be a description of the topic. This page explains the considerations, or ''naming conventions'', on which choices of page title are based. When possible, the page should start with the name of the page in bold. Avoid starting the page with a heading. <br />
<br />
== Deciding on a page title ==<br />
A good IMSMA page title has the five following characteristics:<br />
* '''Recognizability''': the title is a name or description of the subject that someone familiar with, although not necessarily an expert in, the subject will recognize.<br />
* '''Naturalness''': the title is one that IMSMA users are likely to look or search for and that editors would naturally use to link to the page from other pages. <br />
* '''Precision''': the title is sufficiently identify the page's subject and distinguish it from other subjects.<br />
* '''Conciseness''': the title is no longer than necessary to identify the page's subject and distinguish it from other subjects.<br />
* '''Consistency''': the title is consistent with the pattern of similar pages' titles.<br />
<br />
== Format ==<br />
The following points are used in deciding on questions not covered by the five principles. Consistency on these helps avoid duplicate articles:<br />
* '''Short''': Keep titles short but descriptive. <br />
* '''Unique''': No two page titles should have the same title.<br />
* '''Capitalisation''': The first letter of every word should be capital, except for prepositions and articles. Titles cannot begin with a lowercase letter.<br />
* '''Singular''': In general only create page titles that are in the singular, unless that term is always in a plural form in English or it is valid to use in an IMSMA context like Sub-Themes, Customise Views, localisation files, etc.<br />
* '''Acronyms''': Should be used in a page name if the subject is known primarily by its abbreviation and that abbreviation is primarily associated with the subject, otherwise avoid using Acronyms. All acronyms will be in the glossary.<br />
* '''Symbols''': Titles cannot contain certain restricted characters (e.g # < > [ ] | { } : ) or encoded characters (%, &#47). <br />
**Titles cannot contain 3 or more contiguous tildes (<nowiki>~~~</nowiki>), as strings of tildes are used to create editors' signatures on talk pages.<br />
**Titles should not include question marks.<br />
* '''Spaces''': MediaWiki treats Spaces ( ) and underscores (_) are equivalently. Underscores are used in URL and Spaces in displayed titles, there is no need to add underscore in the page titles.<br />
* '''Formatting''': It is not possible for a title as stored in the database to contain formatting, such as italics or bolding. The double or triple apostrophes normally used to produce these effects in wikitext are treated just as groups of apostrophes if they appear in titles but avoid apostrophes and quotes unless absolutely required.<br />
* '''Images''': Titles cannot contain images.<br />
<br />
== Section headings ==<br />
Equal signs are used to mark the enclosed text as a section heading: <nowiki>==Title==</nowiki> for a primary section; <nowiki>===Title===</nowiki> for the next level (a subsection); and so on to the lowest-level subsection, with <nowiki>=====Title=====</nowiki>. (The highest heading level technically possible is =Title=; but do not use it in pages, because it is reserved for the automatically generated top-level heading at the top of the page containing the title of the whole page.) <br />
The heading must be typed on a separate line. Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window. <br />
<br />
== Readability ==<br />
An article longer than one or two pages when printed should be divided into sections to ease navigation.<br />
Articles that cover particularly technical subjects should, in general, be shorter than articles on less technical subjects.<br />
<br />
== Talk pages ==<br />
Talk pages are used to discuss the development of their corresponding Page. The discussions are hence not intended to be generic on the topic of the Page, but centred on edits and structure of the page.<br />
<br />
== User talk pages ==<br />
While the purpose of talk pages is to discuss the content of pages, the purpose of user talk pages is to draw the attention or discuss the edits of a user. IMSMA Wiki is not a social networking site, and all discussion should ultimately be directed solely toward the improvement of the wiki. As opposed to the case with the Main name space, users may freely remove comments from their own talk pages.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Links&diff=10232Links2013-09-09T11:26:11Z<p>Daniel: Cleanup</p>
<hr />
<div>__NOTOC__<br />
'''Links''' on the IMSMA wiki can either internal, so called Wikilinks, or external links. <br />
<br />
==Wikilinks==<br />
Wikilinks are links that point to other Pages on the IMSMA Wiki. Wikilinks are [[red]] if the Page that they point to does not exist. <br />
*'''Make links only where they are relevant and helpful in the context:''' Excessive use of hyperlinks can be distracting, and may slow the reader down. Redundant links clutter the page and make future maintenance harder. <br />
*'''Link the first mentioning''': Unless the context calls for it, link only the first time a topic is mentioned rather than every time that it appears in the text.<br />
*'''Linking to sections:''' A hash sign&nbsp;(#) followed by the appropriate heading will lead to a relevant part of a page. For example, <code><nowiki>[[Geospatial Data#How To Manually Add a Geospatial Point]]</nowiki></code> links to a particular section of the page [[Geospatial Data]].<br />
*'''Check links:''' Ensure that the destination is the intended one.<br />
<br />
==External links==<br />
Avoid using external links in the body of a page. Pages can include an ''external links'' section at the end, pointing to further information outside IMSMA Wiki. The standard format is a primary heading, <code>==External links==</code>, followed by a bulleted list of links.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Lists&diff=10231Lists2013-09-09T11:13:04Z<p>Daniel: Centred tables and cleaned up</p>
<hr />
<div>__NOTOC__<br />
'''Lists''' are used to better structure text that is unsuitable as a paragraph. <br />
<br />
== General rules ==<br />
* Do not use lists if text is read easily as plain paragraphs.<br />
* Use proper wikimarkup.<br />
* Do not leave blank lines between items in a bulleted or numbered list unless there is a reason to do so, since this causes the Wiki software to interpret each item as beginning a new list.<br />
* Use the same grammatical form for all elements in a list, and do not mix sentences and sentence fragments as elements.<br />
* When the elements are complete sentences, each one is formatted with sentence case (its first letter is capitalized) and a final period (full stop).<br />
* Use numbers rather than bullets only if:<br />
** a need to refer to the elements by number may arise;<br />
** the sequence of the items is critical; or<br />
** the numbering has some independent meaning.<br />
<br />
== Bulleted lists ==<br />
<br />
{| class="wikitable" style="margin: 1em auto 1em auto;"<br />
|+Good example<br />
! scope="col" | Wikitext<br />
! scope="col" | Appearance<br />
|- style="vertical-align:top;"<br />
| <pre style="margin:0px;"><br />
== Title of list ==<br />
* Example 1<br />
* Example 2<br />
* Example 3<br />
</pre><br />
| style="white-space:nowrap; padding:1em;" | <div style="padding-top:0.5em; padding-bottom:0.17em; border-bottom:1px solid #aaa; font-size:150%; margin-bottom:0.6em;"> Title of list </div><br />
* Example 1<br />
* Example 2<br />
* Example 3<br />
|}<br />
<br />
In particular, '''do not double-space the lines of the list''' by leaving blank lines or extra HTML <nowiki><br></nowiki> tags after them, as in this example:<br />
{| class="wikitable" style="margin: 1em auto 1em auto;"<br />
|+Bad example<br />
! scope="col" | Wikitext<br />
! scope="col" | Appearance<br />
|- style="vertical-align:top;"<br />
| <pre style="margin:0px;"><br />
== Title of list ==<br />
* Example 1<br />
<br />
* Example 2<br />
<br />
* Example 3<br />
</pre><br />
| style="white-space:nowrap; padding:1em;" | <div style="padding-top:0.5em; padding-bottom:0.17em; border-bottom:1px solid #aaa; font-size:150%; margin-bottom:0.6em;"> Title of list </div><br />
* Example 1<br />
<br />
* Example 2<br />
<br />
* Example 3<br />
|}<br />
<br />
==Numbered lists==<br />
Similar to the above, use a # symbol to obtain a numbered list:<br />
{| class="wikitable" style="margin: 1em auto 1em auto;"<br />
! Wikitext<br />
! Appearance<br />
|-<br />
| <pre><br />
== Title of list ==<br />
# Example 1<br />
# Example 2<br />
# Example 3<br />
</pre><br />
| style="white-space:nowrap; padding:1em;" | <div style="padding-top:0.5em; padding-bottom:0.17em; border-bottom:1px solid #aaa; font-size:150%; margin-bottom:0.6em;"> Title of list </div><br />
# Example 1<br />
# Example 2<br />
# Example 3<br />
|}<br />
Blank lines between items of an ordered list will not only cause the same problems as in the previous example, but will also restart the numbering at "1".<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Template:Policies&diff=10230Template:Policies2013-09-09T10:45:59Z<p>Daniel: Updated Template group</p>
<hr />
<div>{{Navbox<br />
| name = IMSMA Wiki policies <br />
| state = {{{state|<includeonly>{{{1|autocollapse}}}</includeonly>}}}<br />
| bodyclass = hlist<br />
| titlestyle = {{{titlestyle|}}}<br />
| title = [[IMSMA Wiki Policies]]<br />
<br />
| group1 = [[Pages]]<br />
| list1 =<br />
* [[Pages#Format|Format]]<br />
* [[Pages#Section_headings|Section headings]]<br />
* [[Pages#Talk_pages|Talk pages]]<br />
* [[Pages#Users_talk_pages|User talk pages]]<br />
<br />
| group2 = [[Images]]<br />
| list2 =<br />
* [[Images#General_rules|General rules]]<br />
* [[Images#Copyright and licensing|Copyright and licensing]]<br />
* [[Images#Image titles and file names|Image titles]]<br />
* [[Images#Placement|Placement]]<br />
* [[Images#Format|Format]]<br />
* [[Images#Size|Size]]<br />
<br />
| group3 = [[Templates]]<br />
| list3 =<br />
* [[Templates#Informative templates|Informative]]<br />
* [[Templates#Formatting templates|Formatting]]<br />
* [[Templates#Navigation templates|Navigation]]<br />
<br />
| group4 = [[Lists]]<br />
| list4 =<br />
* [[Lists#General rules|General rules]]<br />
* [[Lists#Bulleted lists|Bulleted lists]]<br />
* [[Lists#Numbered lists|Numbered lists]]<br />
<br />
| group5 = [[Links]]<br />
| list5 =<br />
* [[Links#Wikilinks|Wikilinks]]<br />
* [[Links#External links|External links]]<br />
<br />
}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Templates&diff=10229Templates2013-09-09T10:24:11Z<p>Daniel: Added actual temlaptes</p>
<hr />
<div>__NOTOC__<br />
'''Templates''' are used to give standard messages on Pages. Templates are called using these brackets <nowiki>{{template name}}</nowiki>. There are many purposes for using templates. They can be to convey or format messages to the reader of the Page, they can be used to facilitate navigation, or they can be used to convey messages or to flag pages to the editors. <br />
<br />
==Informative templates==<br />
===Notes===<br />
Every page that is linked to a note should use the [[Template:Note|Note template]]. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{Note | Text should be placed here}}</nowiki><br />
{{Note | Text should be placed here}}<br />
<br />
===Warnings===<br />
Every page that is linked to a warning should use the [[Template:Warning|Warning template]]. Users can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{Warning| Text should be placed here}}</nowiki><br />
{{Warning| Text should be placed here}}<br />
<br />
==Formatting templates==<br />
==={{IMSMANG}}===<br />
Every page that uses the word {{IMSMANG}} should use the [[Template:IMSMANG|IMSMANG template]]. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{IMSMANG}}</nowiki><br />
===TOC===<br />
Per default the Table of Contents (TOC) on a page are placed to the left of the Page. If the editor prefers the TOC to the right, the [[Template:TOC right|TOC template]] is used. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{TOC right}}</nowiki><br />
<br />
==Navigation templates==<br />
On IMSMA Wiki, a navbox is a template that lists at least several pages that are related. The relationship between all the pages in a single navbox is such that the reader of the current page will be readily referred to other related material with a single link. The goal is to have a navbox in every page (bottom).<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Templates&diff=10228Templates2013-09-09T10:22:43Z<p>Daniel: Cleaned up</p>
<hr />
<div>__NOTOC__<br />
'''Templates''' are used to give standard messages on Pages. Templates are called using these brackets <nowiki>{{template name}}</nowiki>. There are many purposes for using templates. They can be to convey or format messages to the reader of the Page, they can be used to facilitate navigation, or they can be used to convey messages or to flag pages to the editors. <br />
<br />
==Informative templates==<br />
===Notes===<br />
Every page that is linked to a note should use the [[Template:Note|Note template]]. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{Note | Text should be placed here}}</nowiki><br />
<br />
===Warnings===<br />
Every page that is linked to a warning should use the [[Template:Warning|Warning template]]. Users can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{Warning| Text should be placed here}}</nowiki><br />
<br />
==Formatting templates==<br />
==={{IMSMANG}}===<br />
Every page that uses the word {{IMSMANG}} should use the [[Template:IMSMANG|IMSMANG template]]. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{IMSMANG}}</nowiki><br />
===TOC===<br />
Per default the Table of Contents (TOC) on a page are placed to the left of the Page. If the editor prefers the TOC to the right, the [[Template:TOC right|TOC template]] is used. Editors can add it in the corresponding place of the page using the following command:<br />
<nowiki>{{TOC right}}</nowiki><br />
<br />
==Navigation templates==<br />
On IMSMA Wiki, a navbox is a template that lists at least several pages that are related. The relationship between all the pages in a single navbox is such that the reader of the current page will be readily referred to other related material with a single link. The goal is to have a navbox in every page (bottom).<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Images&diff=10224Images2013-09-09T09:11:02Z<p>Daniel: Rewrote copyright para</p>
<hr />
<div>__NOTOC__<br />
'''Images''' uploaded should be [[print screen]]s from the [[current IMSMA version]]. Upload [[high resolution]] print screens. <br />
<br />
==General rules==<br />
* '''Image description''': Use the image description page to describe the image, its source and purpose. For IMSMA screenshots this includes the data source used, the IMSMA version and the interface language.<br />
* '''Title''': Use a clear, detailed title. Note that if any image with the same title has already been uploaded, it will be replaced with your new one.<br />
* '''Resolution''': Upload a high-resolution version of your image whenever possible, and use the automatic thumbnailing option of the MediaWiki image markup to scale down the image. MediaWiki accepts images up to 100 MB in size. Do not scale down the image yourself, as scaled-down images may be of limited use in the future.<br />
* '''Cropping''': Crop the image to highlight the relevant subject.<br />
* '''Translation''': If you create an image that contains text, please also upload a version without any text. It will be useful in the future to translate the image into other languages.<br />
* '''Colours''': Try not to use colour alone to convey information, as it is inaccessible in many situations.<br />
* '''Thumbnails''': In general, there is no need to specify thumbnail size. Users can select their ideal size in preferences.<br />
<br />
== Copyright and licensing ==<br />
Copyright and licensing is not a major issue for the IMSMA wiki. However, when making screenshots, be sure that you use a database that have been approved for sharing. Use the image description to document the IMSMA version, data source and interface language. It is also useful to indicate other meta data like whether the image is a screenshot. <br />
<br />
== Image titles and file names ==<br />
Descriptive file names are useful. Check whether there are already similar images in IMSMA Wiki. Then decide whether your image should replace one (in each page that uses it) or be additional. In the first case give it exactly the same name, otherwise a suitable other name. Avoid special characters in filenames or excessively long filenames, though, as that might make it difficult for some users to download the files onto their machines. Note that names are case sensitive, "Test.PNG" is considered different from "Test.png". For uniformity, lower case file name extensions are recommended.<br />
<br />
== Placement ==<br />
* '''Image galleries''': Images are typically interspersed individually throughout a page near the relevant text. However, the use of a gallery may be appropriate in some pages if a collection of images can illustrate aspects of a subject that cannot be easily or adequately described by text or individual images. Images in a gallery should be suitably captioned to explain their relevance both to the article subject and to the theme of the gallery, and the gallery should be appropriately titled (unless the theme of the gallery is clear from the context of the article). Note that galleries will be small if the wiki is printed. See the [https://en.wikipedia.org/wiki/Help:Gallery_tag Wikipedia help file for galleries].<br />
<gallery><br />
File:User Items.png|Example image gallery from the IMSMA [[Core Design Concepts]]<br />
File:User Browse.png<br />
File:Field Report Template Designer (QRG).png<br />
</gallery><br />
* '''Image queuing''': Articles may get ugly and difficult to read if there are too many images onto a page with relatively little text. They may even overlap. Avoid adding images after each other. Use a gallery, if this is required.<br />
<br />
== Format ==<br />
* '''Drawings, icons, maps, flags''': are preferably uploaded in [[SVG]] format as vector images. Images with large, simple, and continuous blocks of colour which are not available as SVG should be in PNG format.<br />
* '''Software screenshots''': should be in [[PNG]] format.<br />
* '''Photos and scanned images''': should be in [[JPEG]] format.<br />
* '''Inline animations''': should be in animated [[GIF]] format.<br />
* '''Video''': should be in [[Ogg]]/[[Theora]] format.<br />
<br />
== Size ==<br />
* '''Uploaded image size''': Uploaded files must be smaller than 100 megabytes. The MediaWiki software can resize images automatically, so it is rarely necessary to resize images yourself.<br />
* '''Displayed image size''': Images beside the text should generally use a caption and the "thumb" (thumbnail) option; the default results in a display ''220 pixels wide'', except for those logged-in users who have set a different default in their user preferences. Where size forcing is appropriate, larger images should generally be a maximum of ''500 pixels tall'' and ''400 pixels wide'', so that they can comfortably be displayed on the smallest displays in common use. Since MediaWiki dynamically scales inline images there is no need to reduce file size via scaling or quality reduction when uploading images, although compressing PNGs may be useful. Lead images should usually be no wider than ''"upright=1.35" or "300px"''.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=IMSMA_Wiki_Policies&diff=10223IMSMA Wiki Policies2013-09-09T09:00:00Z<p>Daniel: Rephrased intro</p>
<hr />
<div>The '''IMSMA Wiki Policies''' guides the work of the editors by describing the standards that all users should follow in order to maintain a consistent coherent content. It is important for the editors to read and understand the policy before starting to make edits.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Pages&diff=10222Pages2013-09-09T08:50:13Z<p>Daniel: Reformated and reduced Talk page policy</p>
<hr />
<div>__NOTOC__<br />
'''Pages''' on the IMSMA Wiki are structured into several headings. The page title is the top Level&nbsp;1 heading displayed above each page's contents. The title indicates what the page is about and is a unique reference to the page. The title may simply be the name of the subject of the page, or it may be a description of the topic. This page explains the considerations, or ''naming conventions'', on which choices of page title are based. <br />
<br />
== Deciding on a page title ==<br />
A good IMSMA page title has the five following characteristics:<br />
* '''Recognizability''': the title is a name or description of the subject that someone familiar with, although not necessarily an expert in, the subject will recognize.<br />
* '''Naturalness''': the title is one that IMSMA users are likely to look or search for and that editors would naturally use to link to the page from other pages. <br />
* '''Precision''': the title is sufficiently identify the page's subject and distinguish it from other subjects.<br />
* '''Conciseness''': the title is no longer than necessary to identify the page's subject and distinguish it from other subjects.<br />
* '''Consistency''': the title is consistent with the pattern of similar pages' titles.<br />
<br />
== Format ==<br />
The following points are used in deciding on questions not covered by the five principles. Consistency on these helps avoid duplicate articles:<br />
* '''Short''': Keep titles short but descriptive. <br />
* '''Unique''': No two page titles should have the same title.<br />
* '''Capitalisation''': The first letter of every word should be capital, except for prepositions and articles. Titles cannot begin with a lowercase letter.<br />
* '''Singular''': In general only create page titles that are in the singular, unless that term is always in a plural form in English or it is valid to use in an IMSMA context like Sub-Themes, Customise Views, localisation files, etc.<br />
* '''Acronyms''': Should be used in a page name if the subject is known primarily by its abbreviation and that abbreviation is primarily associated with the subject, otherwise avoid using Acronyms. All acronyms will be in the glossary.<br />
* '''Symbols''': Titles cannot contain certain restricted characters (e.g # < > [ ] | { } : ) or encoded characters (%, &#47). <br />
**Titles cannot contain 3 or more contiguous tildes (<nowiki>~~~</nowiki>), as strings of tildes are used to create editors' signatures on talk pages.<br />
**Titles should not include question marks.<br />
* '''Spaces''': MediaWiki treats Spaces ( ) and underscores (_) are equivalently. Underscores are used in URL and Spaces in displayed titles, there is no need to add underscore in the page titles.<br />
* '''Formatting''': It is not possible for a title as stored in the database to contain formatting, such as italics or bolding. The double or triple apostrophes normally used to produce these effects in wikitext are treated just as groups of apostrophes if they appear in titles but avoid apostrophes and quotes unless absolutely required.<br />
* '''Images''': Titles cannot contain images.<br />
<br />
== Section headings ==<br />
Equal signs are used to mark the enclosed text as a section heading: <nowiki>==Title==</nowiki> for a primary section; <nowiki>===Title===</nowiki> for the next level (a subsection); and so on to the lowest-level subsection, with <nowiki>=====Title=====</nowiki>. (The highest heading level technically possible is =Title=; but do not use it in pages, because it is reserved for the automatically generated top-level heading at the top of the page containing the title of the whole page.) <br />
The heading must be typed on a separate line. Include one blank line above the heading, and optionally one blank line below it, for readability in the edit window. <br />
<br />
== Readability ==<br />
An article longer than one or two pages when printed should be divided into sections to ease navigation.<br />
Articles that cover particularly technical subjects should, in general, be shorter than articles on less technical subjects.<br />
<br />
== Talk pages ==<br />
Talk pages are used to discuss the development of their corresponding Page. The discussions are hence not intended to be generic on the topic of the Page, but centred on edits and structure of the page.<br />
<br />
== User talk pages ==<br />
While the purpose of talk pages is to discuss the content of pages, the purpose of user talk pages is to draw the attention or discuss the edits of a user. IMSMA Wiki is not a social networking site, and all discussion should ultimately be directed solely toward the improvement of the wiki. As opposed to the case with the Main name space, users may freely remove comments from their own talk pages.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Images&diff=10217Images2013-09-09T07:44:12Z<p>Daniel: Cleaned up</p>
<hr />
<div>__NOTOC__<br />
'''Images''' uploaded should be [[print screen]]s from the [[current IMSMA version]]. Upload [[high resolution]] print screens. <br />
<br />
==General rules==<br />
* Use the image description page to describe an image and possibly its copyright status.<br />
* Use a clear, detailed title. Note that if any image with the same title has already been uploaded, it will be replaced with your new one.<br />
* Upload a high-resolution version of your image whenever possible, and use the automatic thumbnailing option of the MediaWiki image markup to scale down the image. MediaWiki accepts images up to 100 MB in size. Do not scale down the image yourself, as scaled-down images may be of limited use in the future.<br />
* Crop the image to highlight the relevant subject.<br />
* If you create an image that contains text, please also upload a version without any text. It will be useful in the future to translate the image into other languages.<br />
* Try not to use color alone to convey information, as it is inaccessible in many situations.<br />
* Use JPEG format for photographic images and TV or movie screenshots; SVG format for icons, logos, drawings, maps, flags, and such; PNG format for software screenshots and when only a raster image is available; GIF format for inline animations; and Ogg/Theora for video.<br />
* In general, there is no need to specify thumbnail size. Users can select their ideal size in preferences.<br />
<br />
== Copyright and licensing ==<br />
Before you upload an image, make sure that the image falls in one of the three categories:<br />
# '''Own work''': You own all rights to the image, usually meaning that you created it entirely yourself.<br />
# '''Freely licensed''': You can prove that the copyright holder has released the image under an acceptable free license. Note that images that are licensed for use only on the [[GICHD]] [[IMSMA wiki]], or only for non-commercial or educational use, or under a license that doesn't allow for the creation of modified/derived works, are unsuitable. <br />
# '''Public domain''': You can prove that the image is in the [[public domain]], i.e. free of all copyrights. <br />
<br />
== Image titles and file names ==<br />
Descriptive file names are useful. Check whether there are already similar images in IMSMA Wiki. Then decide whether your image should replace one (in each page that uses it) or be additional. In the first case give it exactly the same name, otherwise a suitable other name. Avoid special characters in filenames or excessively long filenames, though, as that might make it difficult for some users to download the files onto their machines. Note that names are case sensitive, "Test.PNG" is considered different from "Test.png". For uniformity, lower case file name extensions are recommended.<br />
<br />
== Placement ==<br />
* '''Image galleries''': Images are typically interspersed individually throughout a page near the relevant text. However, the use of a gallery may be appropriate in some pages if a collection of images can illustrate aspects of a subject that cannot be easily or adequately described by text or individual images. Images in a gallery should be suitably captioned to explain their relevance both to the article subject and to the theme of the gallery, and the gallery should be appropriately titled (unless the theme of the gallery is clear from the context of the article). Note that galleries will be small if the wiki is printed. See the [https://en.wikipedia.org/wiki/Help:Gallery_tag Wikipedia help file for galleries].<br />
<gallery><br />
File:User Items.png|Example image gallery from the IMSMA [[Core Design Concepts]]<br />
File:User Browse.png<br />
File:Field Report Template Designer (QRG).png<br />
</gallery><br />
* '''Image queuing''': Articles may get ugly and difficult to read if there are too many images onto a page with relatively little text. They may even overlap. Avoid adding images after each other. Use a gallery, if this is required.<br />
<br />
== Format ==<br />
* '''Drawings, icons, maps, flags''': are preferably uploaded in [[SVG]] format as vector images. Images with large, simple, and continuous blocks of colour which are not available as SVG should be in PNG format.<br />
* '''Software screenshots''': should be in [[PNG]] format.<br />
* '''Photos and scanned images''': should be in [[JPEG]] format.<br />
* '''Inline animations''': should be in animated [[GIF]] format.<br />
* '''Video''': should be in [[Ogg]]/[[Theora]] format.<br />
<br />
== Size ==<br />
* '''Uploaded image size''': Uploaded files must be smaller than 100 megabytes. The MediaWiki software can resize images automatically, so it is rarely necessary to resize images yourself.<br />
* '''Displayed image size''': Images beside the text should generally use a caption and the "thumb" (thumbnail) option; the default results in a display ''220 pixels wide'', except for those logged-in users who have set a different default in their user preferences. Where size forcing is appropriate, larger images should generally be a maximum of ''500 pixels tall'' and ''400 pixels wide'', so that they can comfortably be displayed on the smallest displays in common use. Since MediaWiki dynamically scales inline images there is no need to reduce file size via scaling or quality reduction when uploading images, although compressing PNGs may be useful. Lead images should usually be no wider than ''"upright=1.35" or "300px"''.<br />
<br />
{{Policies}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Core_Design_Concepts&diff=10026Core Design Concepts2013-08-22T12:03:18Z<p>Daniel: Major cleanup</p>
<hr />
<div>[[File:User Window FINAL.png|frame|alt=Elements of the main IMSMA user interface|The [[IMSMA Navigation Window]] displays at the launch of the system.]]<br />
The '''core design concepts''' of IMSMA are the fundamental ideas and values that have driven the development. <br />
<br />
==Intuitive==<br />
Designed with the end user in mind, the IMSMA Navigation Window provides immediate access to the the most commonly used tools including data entry, data validation, data search and reporting. A user can interact with elements of any of the panes and access additional details. The user can browse for more details including past information leading up to the current situation.<br />
<gallery><br />
File:User Items.png|Example how the map pane is continously connected to the other panes<br />
File:User Browse.png|The [[Items Pane]] stores information about mine action objects (dark gray below) and mine action activities (light gray). These are locations, tasks, lands, activities, accidents, victims, education activities and quality management activities.<br />
File:Field Report Template Designer (QRG).png|Interface for creating or editing forms<br />
</gallery><br />
<br />
==Flexible==__NOEDITSECTION__<br />
IMSMA<sup>NG</sup> was designed to be adapted to the reality surrounding it. It provides customisation tools that enable an IMSMA administrator mine action programme to adjust the information management system to meet the needs of the programme. <br />
<br />
===Adaptable data collection forms===__NOEDITSECTION__<br />
The [[Access the Data Entry Form Template Designer Window|Data Entry Form Template Design]] is a tool that allows for the creation of survey ''forms'' or any other form needed to record data on mine action objects and activities. The IMSMA<sup>NG</sup> forms can be created to look like the actual survey forms used in the field for data collection.<br />
<br />
===Report Designer===__NOEDITSECTION__<br />
The report designer is a graphic tool for creating Report Templates. Report templates are saved reports that can be run on the dataset by any user to give statistics or tables of information.<br />
<gallery><br />
File:Report Templates.png|Report Templates<br />
File:Graphic Display of Data.png|Graphic Display of Data<br />
File:Report Customization.png|Report Customization<br />
</gallery><br />
{{NavBox What is IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=The_Making_of_IMSMA&diff=10025The Making of IMSMA2013-08-22T10:53:34Z<p>Daniel: Demoted and renamed section</p>
<hr />
<div>'''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 Inc.]]<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. ([[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 organizations 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 [[impact scoring tool]] and the possibility of recording [[victim]]s and [[accident]]s separately. User feedback and lessons learnt are constantly evaluated and compiled by the [[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 Systems refers to older IMSMA versions (V1.x to V3.x) deployed in the field before IMSMA NG.<br />
Support is still being provided to installations that were performed by the GICHD, and which are currently in use for field operations.<br />
New installations can only be done with IMSMA NG, due to the close dependence of the Legacy Systems on Microsoft Office Suite and Windows [[operating system]]s. Read more on [[Upgrading to IMSMA NG]].<br />
Legacy Systems requires a highly standardised and linear [[workflow]]. The workflow is started by the [[Impact Survey]] or other [[Level 1 Survey]], which can produce [[mined area]] reports. [[Technical Survey]] or [[Level 2 Survey]] follows. This produces a [[minefield]] which is addressed by a [[clearance]] which may have associated [[progress report]]s. The process is concluded with a [[Completion report]].<br />
===IMSMA V3===__NOEDITSECTION__<br />
[[IMSMA V3]] was released in 2002 and followed by regular updates over the next couple of years. It presented a complete new software architecture and each update contributed substantially with new added functionalities and greater flexibility. This was a first attempt to move from the original repository database into a more operational management tool for the mine action programmes. The task tracking tool allowed information managers to account for the work accomplished by each organization. <br />
In addition, IMSMA V3 started embracing professional database platforms such as [[Microsoft SQL Server]] for its technical development. This software improved numerous aspects, from data handling being facilitated through the design of database queries, to installations into a networked environment, with an increased number of simultaneous users.<br />
<br />
===IMSMA v.1===__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 standardized 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. IMSMA v.2.2 was said to be “significantly better” as it provided among others, a plug-in to ArcVIEW allowing to view information on a map. It was with this newly developed version that IMSMA was adopted by the UN on an international level as the standard for humanitarian demining information.<br />
<br />
{{NavBox What is IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Summary_Window&diff=10024Summary Window2013-08-21T16:38:20Z<p>Daniel: </p>
<hr />
<div>__FORCETOC__<br />
{{TOC right}}<br />
<br />
{| style="border-top:2px solid lightgray; border-bottom:2px solid lightgray; margin:10px;"<br />
|align="left" style="padding: 5px 10px 5px 10px"| All users will have permission to view the summary windows.<br />
|}<br />
<br />
{{HowTo's<br />
|[[Export a Data Entry Form from the Summary View|Export a Data Entry Form]]<br />
|[[Add a Data Entry Form from the Summary View|Add a Data Entry Form]]<br />
|[[Update the Data in the Summary View]]<br />
|[[View a Data Entry Form from the Summary View|View a Data Entry Form]]<br />
|[[Print an Item from the Summary View|Print an Item]]<br />
|[[Unapprove a Data Entry Form from the Summary View|Unapprove a Data Entry Form]]<br />
|[[Remove a Link Between Items|Remove a Link Between Items]]<br />
|[[Customise Views | Customise Summaries]]<br />
}}<br />
<br />
The '''summary window''' display the most recent set of attribute data for an item. This includes data entry forms, geospatial data, associated attachments, and related item records. <br />
<br />
There are several different ways to access the summary windows:<br />
*Select the icon on the map so that the blue circle displays on the icon. Once the blue circle is displayed on the icon, double-click the icon on the IMSMA Navigation window’s map pane.<br />
*Double-click the item record’s row from the IMSMA Navigation window’s items pane. <br />
*Select the icon on the map or the item record’s row from the items pane and click the [[Image:InfoPageIcon.png | Identify Selection]] button. From the Identify Selection window, select the item record and click the [[Image:SunglassesIcon.png | Summary]] button.<br />
The attributes displayed in the summary window for each item will vary and are listed in the item-specific sections that follow.<br />
Most of the buttons for the summary window are located in the top, right corner of the window. In addition to these buttons, the '''Done''' button in the bottom, right corner of the window closes the summary window. <br />
<br />
{| class="wikitable" width="600"<br />
|-<br />
| align="center" colspan="2" | '''Summary Buttons'''<br />
|-<br />
| width="125pt" | '''Button'''<br />
| width="475pt" | '''Description'''<br />
|-<br />
| [[Image:BareAddButton.png | Add]] || Allows you to add a new item reconciled to the existing item's location.<br />
|-<br />
| [[Image:BareEditButton.png | Edit]] || Allows you to update the existing data in the item summary window.<br />
|-<br />
| [[Image:BareDeleteButton.png | Delete]] || Allows you to delete the item summary from the system. Note that any data entry forms associated with the item are not unapproved, but they can only be located by searching for "deleted" type data entry forms.<br />
|-<br />
| [[Image:FieldReportIcon.png | Data Entry Form]] || Lists the data entry forms that are related to the item.<br />
|-<br />
| [[Image:PrinterIcon.png | Print]] || Displays a printable view of the item.<br />
|-<br />
| [[Image:ShadesIcon.png | View On Map]] || Displays the item icon on the map.<br />
|-<br />
| [[Image:AttachmentsButton.png | Attachments]] || Allows you to manage attached files.<br />
|-<br />
| [[Image:YellowManIcon.png | Locatin Summary]] || Displays the location associated with the item. This button is not available from the Location Summary window.<br />
|-<br />
| [[Image:uAIBtn01.png | Unlink]] || Allows you to remove the link between two or more items.<br />
|}<br />
<br />
{{NavBox HowTo Viewing and Browsing}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=User_talk:Dionysia&diff=9891User talk:Dionysia2013-07-26T14:55:08Z<p>Daniel: </p>
<hr />
<div>== Template:Good Article from Wikipedia ==<br />
We will need a set of boiler template for a number of issues with articles eg Cleanup needed, Need to be expanded, Need to be updated to new version...<br />
It would also be useful with a process to identify "Good articles" --[[User:Daniel|Daniel]] 16:45, 26 July 2013 (CEST)<br />
:Already talked with Rana for this: http://en.wikipedia.org/wiki/Template:Good_article<br />
::Great!--[[User:Daniel|Daniel]] 16:55, 26 July 2013 (CEST)</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=9890Main Page2013-07-26T14:53:28Z<p>Daniel: Wikified specifications</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">IMSMA<sup>NG</sup> is an information management system designed to support the complex information management needs of the mine action community. Core elements of IMSMA<sup>NG</sup> include a MySQL database for storing and tracking mine action information and the various relationships among the data, a geographic information system (GIS) for analyzing and displaying geospatial information on maps and a reporting tool for generating reports of the data stored in the system. Its client-server architecture enables stand-alone installations to support small programmes with one or two users as well as networked installations for large programmes with 50 or more users distributed across multiple sites and organisations. Additionally, IMSMA<sup>NG</sup> can be paired with several supporting components that directly interact with the IMSMA<sup>NG</sup> system.<br />
<br />
Designed with flexibility to support a range of uses, IMSMA<sup>NG</sup> can also be customised by individual programmes to suit their changing information management needs. This includes defining the type of mine action data to store in IMSMA<sup>NG</sup> and the relationships among the types, the forms used to enter the data into the system and the workflows that match the current or desired information model. So, significant attention must be paid when setting up and customising IMSMA<sup>NG</sup> to support a programme’s information management needs and to get the most out of the system.''</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-dyk-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including Arabic, English, French, Khmer, Russian, Spanish and Thai</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* [[Postgres]] Database <br />
* [[i-Report]] reporting Engine<br />
* Utilizes Mine Action XML ([[maXML]])<br />
* Runs on [[Windows 7]], [[Windows Vista]], [[Windows XP]], [[Windows 2000]], [[Windows Server 2003]] and [[Windows Server 2008]]</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=User_talk:Dionysia&diff=9888User talk:Dionysia2013-07-26T14:45:51Z<p>Daniel: Created page with "We will need a set of boiler template for a number of issues with articles eg Cleanup needed, Need to be expanded, Need to be updated to new version... It would also be useful..."</p>
<hr />
<div>We will need a set of boiler template for a number of issues with articles eg Cleanup needed, Need to be expanded, Need to be updated to new version...<br />
It would also be useful with a process to identify "Good articles" --[[User:Daniel|Daniel]] 16:45, 26 July 2013 (CEST)</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Glossary&diff=9887Glossary2013-07-26T14:39:42Z<p>Daniel: Trying to add a couple of terms</p>
<hr />
<div>{{compact ToC}}<br />
<br />
<br />
==A==__NOEDITSECTION__<br />
<br />
==B==__NOEDITSECTION__<br />
<br />
==C==__NOEDITSECTION__<br />
<br />
==D==__NOEDITSECTION__<br />
<br />
==E==__NOEDITSECTION__<br />
<br />
==F==__NOEDITSECTION__<br />
;FGM: The company contracted for IMSMA software development<br />
<br />
==G==__NOEDITSECTION__<br />
;GICHD: Geneva International Centre for Humanitarian Demining<br />
<br />
==H==__NOEDITSECTION__<br />
<br />
==I==__NOEDITSECTION__<br />
;IMSMA: Information Management System for Mine Action<br />
<br />
==J==__NOEDITSECTION__<br />
<br />
==K==__NOEDITSECTION__<br />
<br />
==L==__NOEDITSECTION__<br />
<br />
==M==__NOEDITSECTION__<br />
<br />
==N==__NOEDITSECTION__<br />
;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 />
<br />
;NTS:Non-Technical Survey<br />
<br />
==O==__NOEDITSECTION__<br />
<br />
==P==__NOEDITSECTION__<br />
<br />
==Q==__NOEDITSECTION__<br />
<br />
==R==__NOEDITSECTION__<br />
<br />
==S==__NOEDITSECTION__<br />
<br />
==T==__NOEDITSECTION__<br />
<br />
==U==__NOEDITSECTION__<br />
<br />
==V==__NOEDITSECTION__<br />
;View Window: A View Window displays when you open an object from the IMSMA Navigation window. The view shows all current view data, including field reports, of that object. You can customise elements of a view to reflect the data that is collected in your field reports.<br />
<br />
==W==__NOEDITSECTION__<br />
<br />
==X==__NOEDITSECTION__<br />
<br />
==Y==__NOEDITSECTION__<br />
<br />
==Z==__NOEDITSECTION__<br />
<br><br />
{{compactTOC}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=The_Making_of_IMSMA&diff=9886The Making of IMSMA2013-07-26T14:37:55Z<p>Daniel: Spelling</p>
<hr />
<div>'''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 Inc.]]<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== <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. ([[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 organizations 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 [[impact scoring tool]] and the possibility of recording [[victim]]s and [[accident]]s separately. User feedback and lessons learnt are constantly evaluated and compiled by the [[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==<br />
[[Glossary|<abbr title="Information Management System for Mine Action">IMSMA</abbr>]] Legacy Systems refers to older IMSMA versions (V1.x to V3.x) deployed in the field before IMSMA NG.<br />
Support is still being provided to installations that were performed by the GICHD, and which are currently in use for field operations.<br />
New installations can only be done with IMSMA NG, due to the close dependence of the Legacy Systems on Microsoft Office Suite and Windows [[operating system]]s. Read more on [[Upgrading to IMSMA NG]].<br />
Legacy Systems requires a highly standardised and linear [[workflow]]. The workflow is started by the [[Impact Survey]] or other [[Level 1 Survey]], which can produce [[mined area]] reports. [[Technical Survey]] or [[Level 2 Survey]] follows. This produces a [[minefield]] which is addressed by a [[clearance]] which may have associated [[progress report]]s. The process is concluded with a [[Completion report]].<br />
===IMSMA V3===<br />
[[IMSMA V3]] was released in 2002 and followed by regular updates over the next couple of years. It presented a complete new software architecture and each update contributed substantially with new added functionalities and greater flexibility. This was a first attempt to move from the original repository database into a more operational management tool for the mine action programmes. The task tracking tool allowed information managers to account for the work accomplished by each organization. <br />
In addition, IMSMA V3 started embracing professional database platforms such as [[Microsoft SQL Server]] for its technical development. This software improved numerous aspects, from data handling being facilitated through the design of database queries, to installations into a networked environment, with an increased number of simultaneous users.<br />
<br />
==First deployments==<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 standardized 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. IMSMA v.2.2 was said to be “significantly better” as it provided among others, a plug-in to ArcVIEW allowing to view information on a map. It was with this newly developed version that IMSMA was adopted by the UN on an international level as the standard for humanitarian demining information.<br />
<br />
{{NavBox What is IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=The_Making_of_IMSMA&diff=9885The Making of IMSMA2013-07-26T14:36:53Z<p>Daniel: Cleanup</p>
<hr />
<div>''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 Inc.]]<br />
Interoperability, flexibility and user-friendliness were three of the key words that laid down the foundation for the next generation of IMSMA – IMSMANG. 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== <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. ([[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 organizations 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 [[impact scoring tool]] and the possibility of recording [[victim]]s and [[accident]]s separately. User feedback and lessons learnt are constantly evaluated and compiled by the [[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==<br />
[[Glossary|<abbr title="Information Management System for Mine Action">IMSMA</abbr>]] Legacy Systems refers to older IMSMA versions (V1.x to V3.x) deployed in the field before IMSMA NG.<br />
Support is still being provided to installations that were performed by the GICHD, and which are currently in use for field operations.<br />
New installations can only be done with IMSMA NG, due to the close dependence of the Legacy Systems on Microsoft Office Suite and Windows [[operating system]]s. Read more on [[Upgrading to IMSMA NG]].<br />
Legacy Systems requires a highly standardised and linear [[workflow]]. The workflow is started by the [[Impact Survey]] or other [[Level 1 Survey]], which can produce [[mined area]] reports. [[Technical Survey]] or [[Level 2 Survey]] follows. This produces a [[minefield]] which is addressed by a [[clearance]] which may have associated [[progress report]]s. The process is concluded with a [[Completion report]].<br />
===IMSMA V3===<br />
[[IMSMA V3]] was released in 2002 and followed by regular updates over the next couple of years. It presented a complete new software architecture and each update contributed substantially with new added functionalities and greater flexibility. This was a first attempt to move from the original repository database into a more operational management tool for the mine action programmes. The task tracking tool allowed information managers to account for the work accomplished by each organization. <br />
In addition, IMSMA V3 started embracing professional database platforms such as [[Microsoft SQL Server]] for its technical development. This software improved numerous aspects, from data handling being facilitated through the design of database queries, to installations into a networked environment, with an increased number of simultaneous users.<br />
<br />
==First deployments==<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 standardized 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. IMSMA v.2.2 was said to be “significantly better” as it provided among others, a plug-in to ArcVIEW allowing to view information on a map. It was with this newly developed version that IMSMA was adopted by the UN on an international level as the standard for humanitarian demining information.<br />
<br />
{{NavBox What is IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=9883Main Page2013-07-26T14:10:19Z<p>Daniel: Added more text on how to acquire</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">IMSMA<sup>NG</sup> is an information management system designed to support the complex information management needs of the mine action community. Core elements of IMSMA<sup>NG</sup> include a MySQL database for storing and tracking mine action information and the various relationships among the data, a geographic information system (GIS) for analyzing and displaying geospatial information on maps and a reporting tool for generating reports of the data stored in the system. Its client-server architecture enables stand-alone installations to support small programmes with one or two users as well as networked installations for large programmes with 50 or more users distributed across multiple sites and organisations. Additionally, IMSMA<sup>NG</sup> can be paired with several supporting components that directly interact with the IMSMA<sup>NG</sup> system.<br />
<br />
Designed with flexibility to support a range of uses, IMSMA<sup>NG</sup> can also be customised by individual programmes to suit their changing information management needs. This includes defining the type of mine action data to store in IMSMA<sup>NG</sup> and the relationships among the types, the forms used to enter the data into the system and the workflows that match the current or desired information model. So, significant attention must be paid when setting up and customising IMSMA<sup>NG</sup> to support a programme’s information management needs and to get the most out of the system.''</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-dyk-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including Arabic, English, French, Khmer, Russian, Spanish and Thai</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* Postgres Database <br />
* i-Report reporting Engine<br />
* Utilizes Mine Action XML (maXML)<br />
* Runs on Windows 7, Vista, XP, 2000, Server 2003 and Server 2008</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">IMSMA is provided for free. Full details on how to [[Acquiring a copy of IMSMA|acquire a copy of IMSMA]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Main_Page&diff=9882Main Page2013-07-26T14:08:04Z<p>Daniel: Wikified ArcGIS</p>
<hr />
<div>{{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}}<br />
<!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; 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|{{NUMBEROFARTICLES}}]] articles in English</div><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|Using IMSMA]]<br />
* [[Portal:IMSMA Administration|IMSMA Administration]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[Portal:Remote_Entry|Remote Entry]]<br />
* [[Portal:Business Intelligence|Business Intelligence]]<br />
* [[Portal:Technical_Notes|Technical Notes]]<br />
|}<br />
<br />
__NoTOC__<br />
<!-- Template Box --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<br />
<!-- WHAT IS IMSMA --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">What is IMSMA?</h2><br />
|-<br />
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">IMSMA<sup>NG</sup> is an information management system designed to support the complex information management needs of the mine action community. Core elements of IMSMA<sup>NG</sup> include a MySQL database for storing and tracking mine action information and the various relationships among the data, a geographic information system (GIS) for analyzing and displaying geospatial information on maps and a reporting tool for generating reports of the data stored in the system. Its client-server architecture enables stand-alone installations to support small programmes with one or two users as well as networked installations for large programmes with 50 or more users distributed across multiple sites and organisations. Additionally, IMSMA<sup>NG</sup> can be paired with several supporting components that directly interact with the IMSMA<sup>NG</sup> system.<br />
<br />
Designed with flexibility to support a range of uses, IMSMA<sup>NG</sup> can also be customised by individual programmes to suit their changing information management needs. This includes defining the type of mine action data to store in IMSMA<sup>NG</sup> and the relationships among the types, the forms used to enter the data into the system and the workflows that match the current or desired information model. So, significant attention must be paid when setting up and customising IMSMA<sup>NG</sup> to support a programme’s information management needs and to get the most out of the system.''</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-dyk-h2" style="margin:3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:left; color:#000; padding:0.2em 0.4em;">Did you know...</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-dyk">IMSMA is deployed in more than '''1,200''' installations in '''57''' 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 organizations 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" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
| style="padding:2px;" | <h2 id="mp-itn-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Features</h2><br />
|-<br />
| style="color:#000; padding:2px 5px;" | <div id="mp-itn"><br />
* A decision-support system with embedded GIS <br />
* Extremely low cost to field <br />
* Currently translated into multiple languages including Arabic, English, French, Khmer, Russian, Spanish and Thai</div><br />
|-<br />
| style="padding:2px;" | <h2 id="mp-otd-h2" style="margin:3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:left; color:#000; padding:0.2em 0.4em;">Specifications</h2><br />
|-<br />
| style="color:#000; padding:2px 5px 5px;" | <div id="mp-otd"><br />
* Java/J2EE client-server application <br />
* [[ArcGIS]] Engine <br />
* Postgres Database <br />
* i-Report reporting Engine<br />
* Utilizes Mine Action XML (maXML)<br />
* Runs on Windows 7, Vista, XP, 2000, Server 2003 and Server 2008</div><br />
|}<br />
|}<br />
<br />
<!-- ACQUIRE A COPY --><br />
{| id="mp-lower" style="margin:4px 0 0 0; width:100%; background:none; border-spacing: 0px;"<br />
| class="MainPageBG" style="width:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000;" |<br />
{| id="mp-bottom" style="width:100%; vertical-align:top; background:#faf5ff; color:#000;"<br />
| style="padding:2px;" | <h2 id="mp-tfp-h2" style="margin:3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #afa3bf; text-align:left; color:#000; padding:0.2em 0.4em">Acquiring a copy&ensp;<span style="font-size:85%; font-weight:normal;"></span></h2><br />
|-<br />
| style="color:#000; padding:2px;" | <div id="mp-tfp">See more details [[Acquiring_a_copy_of_IMSMA|here]]</div><br />
|}<br />
|}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Getting_IMSMA_systems_Installation_Package&diff=9879Getting IMSMA systems Installation Package2013-07-26T14:00:37Z<p>Daniel: Cleanup</p>
<hr />
<div>{{HowTo's<br />
|[[Getting Training - MIQ]]<br />
}}<br />
<br />
'''Acquiring a copy of IMSMA''' can be done by <br />
*mine action national authorities or organisations filling this role for a specific area or region <br />
*other organisations in support of operations in a mine-affected country <br />
<br />
==Contacts==<br />
National authorities interested in obtaining IMSMA should contact the GICHD directly.Other organisations should contact the respective national mine action authority in the country or location where the proposed use would take place. If you are unable to contact an IMSMA distribution authority in your particular area of interest, please contact the IMSMA Support staff for further information.<br />
<br />
==Costs==<br />
The System is distributed and installed free of charge to national authorities or organisations filling this role.<br />
Any other organisation interested in obtaining IMSMA should approach the Information Management team directly.<br />
<br />
==Distribution==<br />
The GICHD strongly encourages the widest possible distribution of IMSMA from each of the national operating IMSMA installations to government agencies, international organisations, NGOs and field operators engaged in mine action or other humanitarian activities involving mines and other ERW.<br />
A distribution plan centred on the national authorities helps to<br />
*ensure that all users have access to the most up-to-date data, maps and software available in their specific working site <br />
*support national authorities in their extension processes of IMSMA services <br />
*provide support and services to the system tailored to the local needs<br />
*set up and administer national distribution points <br />
*manage and record system installations<br />
<br />
==Limitations==<br />
Potential and current users of the System should be aware that IMSMA is a licensed, trademarked and copyrighted product of the GICHD and is not freeware or shareware. Installation or use of the software constitutes acceptance of the licence agreement. Copies of the system not obtained from the GICHD or through one of its distribution partners will not be supported by the GICHD and are a violation of international copyright.<br />
The software contains certain components of ArcEngine, commercially available of US origin, and generously donated by ESRI. Distribution of these components is subject to US laws governing technology exports and licensing. Requests received by IMSMA’s local distribution partners or the GICHD for the distribution or use of the IMSMA software will need to demonstrate compliance with these regulations before installation of the software can begin.<br />
Distribution or use of the system may also be restricted in the case of projects conducted on a commercial basis or in conjunction with for profit ventures. This restriction is the result of the Centre’s use of public funds in the development and testing of the system.<br />
<br />
{{NavBox Getting started with IMSMA}}</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=User_talk:Alnaucler&diff=9878User talk:Alnaucler2013-07-26T13:56:50Z<p>Daniel: First talk page message</p>
<hr />
<div>Testing a message...<br />
--[[User:Daniel|Daniel]] 15:56, 26 July 2013 (CEST)</div>Danielhttp://mwiki.gichd.org:8090/mediawiki/index.php?title=Talk:Main_Page&diff=7745Talk:Main Page2013-04-23T17:24:24Z<p>Daniel: Created page with "This is awesome :) --~~~~"</p>
<hr />
<div>This is awesome :)<br />
--[[User:Daniel|Daniel]] 19:24, 23 April 2013 (CEST)</div>Daniel