NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
{{TOC 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).
* one-direction exchange
* two-direction exchange.
{{HowTo's
| [[Information Exchange Models]]
| Centralised Data Entry
| [[Setting-up Decentralised Information Exchange | Decentralised Data Entry]]
}}
The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners.
| '' Example of information exchange between stakeholders''
|}
The following points need to be taken in consideration when planning exchange:
==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?
* how and who corrects mistakes?
* who deletes data?
==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 within 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 roles and user accounts created, information managers can distribute the {{IMSMANG}} dataset to implementing partners knowing that key data controls are in place.
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, the :* Data Inventory Manager and :* Auxiliary data.
* Ensure that the implementing partners have Data Entry, Approval and export/import Data Entry Forms permissions.
By establishing a set of limited permissions for the implementing partners, information managers can prevent the accidental or intentional creation of new data elements not available in the national database that will affect the ability of the Central Mine Action Authority to import Data Entry Forms and cause the national dataset to become fractured.
By limiting Auxiliary data permissions to the Central Mine Action Authority, information managers can prevent complications when importing Data Entry Forms. Because Data Entry Forms refers to Auxiliary data, it is important that each country have one common set of [[Standardising Auxiliary Data | Auxiliary data ]] to facilitate exchange. If the Auxiliary data is not properly synchronised, the exchange of Data Entry Forms can result in import issues which must be manually resolved. While {{IMSMANG}} provides an interface for resolving these kinds of issues, it is recommended to reduce the occurrence of these issues by limiting any creation of Auxiliary data to the Central Mine Action Authority who can then distribute an updated dataset as necessary.
==Collecting Regular Feedback==__NOEDITSECTION__