Changes

Information Exchange

4,492 bytes added, 13:08, 4 May 2021

no edit summary

{{Rewrite| This page is under constructionTOC right}} {{IMSMANG}} is designed to support data/information exchange with many IMSMA users and Mine Action stakeholders at numerous sites. These users can include implementing partners, Regional Mine Action Centers and other authorities (e.g. Ministry of Health).

{{IMSMANG}} supports nearly any conceivable several patterns for exchanging '''data''' including * multilateral one-direction exchange* two-direction exchange

* peer-to-peer exchange

* onecombinations of the above. {{HowTo's| [[Information Exchange Models]]| Centralised Data Entry| [[Setting-direction exchangeup Decentralised Information Exchange | Decentralised Data Entry]]* two-direction exchange.}}

The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners.

{{IMSMANG}} supports nearly any conceivable patterns several methods for exchanging '''information''' including * producing maps with [[Connecting to IMSMA Staging area from ArcGIS | external GIS ]] software* producing reports with [[Use iReport | iReport ]] and [[Connecting to IMSMA Staging area from Excel| Excel]]* producting online publish information to websites via the [[IMSMA Staging Area]]. [[Image:Data Information Organisation.png|650px|center]]<div align="center">'' Who needs what''</div>An important part of establishing data/information exchange is to plan and document the data/informations exchange flows including the different steps in the workflows so a sustainable and smooth exchanges and high-quality information are obtained. ==Plan Data/Information Exchange==__NOEDITSECTION__{| class="wikitable"|-| [[Image:Understanding Configuration Options - One way.png|300px|center|]]| [[Image:Information exchange.png|300px|center|]]|- | '' One way exchange plan only covering operators and national database ''| '' Example of information exchange between stakeholders''|} It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents and dashboards with MINTdifferent periodicity. The following points need to be taken in consideration when planning exchange:* why is the data/information shared? * what are the consequences if data/information are not shared on time?* what data/information need/could be shared?* who is the receiver?* publish what will the receiver use the data/information for?:* show contamination impact:* input to websites via operational planning:* show the outcome of Mine Action:* other purposes* will the receiver share the data/information in his turn?* how often? * in which format?:* paper/pdf:* Excel:* shape files:* xml:* IMSMA backup:* Staging areadatabase:* website ==Workflows==__NOEDITSECTION__ When the plan for data/information exchange is outlined it is very important to document the different exchanges so it is clear to all stakeholders in each data/information exchange workflow:* who does what?* how often?* who is responsible for data quality?* who solves data conflicts including duplicates?* how and who corrects mistakes?* who deletes data? A process map of each exchange workflow is a good complement to the detailed written documentation of the workflow.  ==IMSMA specific rules==__NOEDITSECTION__ Data exchange workflows to the national database should include:* how to decide which Location to use?* which items should have links to what?* nice-to-have - desired - required data fields* who decides final ID of items? {{Note | When data is shared between implementing partners and National Mine Action Authority it is important that IDs are '''not''' changed. E.g. Progress report created by implementing partner with ID ''PR-NPA-CHA-15/1'' should still have the same ID after import and approval in the national database.}} ===Ensuring Correct Roles and Permissions are Assigned===__NOEDITSECTION__Establishing correct [[Defining Roles, Permissions and Users | roles and permissions]] in {{IMSMANG}} is a key factor in managing and maintaining data exchange with {{IMSMANG}}. Using the permissions structure, the information manager can carefully control access to key functions that affect data exchange including Data Entry Form templates, Custom Defined Fields, Auxiliary data and Data Entry Form approval. When permissions are correctly established and user accounts created, information managers can distribute the {{IMSMANG}} dataset to implementing partners knowing that key data controls are in place.

An important part of establishing These are the recommended role permissions:* Ensure that the Central Mine Action Authority has exclusive control over :* user accounts and roles:* Data Entry Form templates:* Data Inventory Manager and :* Auxiliary data/information exchange is to plan and document .* Ensure that the workflows so smooth data exchange implementing partners have Data Entry, Approval and high-quality information is obtainedexport/import Data Entry Forms permissions.

==Ensuring Correct Roles and Permissions are Assigned==__NOEDITSECTION__Establishing correct roles and By establishing a set of limited permissions is a key factor in managing and maintaining data exchange within {{IMSMANG}}. Using for the permissions structureimplementing partners, the information manager managers can carefully control access to key functions prevent the accidental or intentional creation of new data elements that will affect data exchange including the ability of the Central Mine Action Authority to import Data Entry Form templates, Custom Defined Fields, Auxiliary data Forms and Data Entry Form approval. When permissions are correctly established and roles and user accounts created, information managers can distribute cause the {{IMSMANG}} national dataset to implementing partners knowing that key data controls are in placebecome fractured.

Using the example of By limiting Auxiliary data permissions to the Central Mine Action Authority and regional sites, information managers can prevent complications when importing Data Entry Forms. Because Data Entry Forms refers to Auxiliary data, it is important that each country have one common set of [[Standardising Auxiliary Data | Auxiliary data]] to facilitate exchange. If the following principles Auxiliary data is not properly synchronised, the exchange of Data Entry Forms can result in import issues which must be manually resolved. While {{IMSMANG}} provides an interface for user account resolving these kinds of issues, it is recommended to reduce the occurrence of these issues by limiting any creation and permissions should be considered:of Auxiliary data to the Central Mine Action Authority who can then distribute an updated dataset as necessary.

* '''Central Mine Action Authority''': Ensure Central Mine Action Authority has exclusive control over user accounts and roles, Data Entry Form templates, the Data Inventory Manager and auxiliary data.==Collecting Regular Feedback==__NOEDITSECTION__* '''Regional Sites''': Ensure that regional sites have In any data entry/information exchange activity, approval it is important to have regular follow-up or meetings to collect feedback and importdiscuss issues or improvements to the data/export permissionsinformation exchange process. Remove permissions for user accounts One recommendation is to establish a feedback forum where implementing partners and roles stakeholders can address data quality issues and auxiliary make adjustments to the data/information exchange process.Topics to address in such a forum include:

By establishing a set * frequency of limited permissions for the regional sites, data/information managers can prevent exchange* standardisation of reports and searches to be included in the accidental central dataset* permissions and role changes* creation or intentional creation modification of new Auxiliary data* which data elements not available at the Central Mine Action Authority that could affect the ability to collect* changes of the Central Mine Action Authority to import Data Entry Forms and cause the dataset to become fractured.templates* output products like reports, statistics, maps

{{NavBox Getting started with IMSMA}}By collecting feedback on these points, information managers can help ensure that data/information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.

{{NavBox IMSMA NG Administration}}[[Category:DSANAA]]

• ← Older edit

Alnaucler

NoPublic, bureaucrat, administrator

6,632

edits