2,186
edits
Changes
no edit summary
Establishing IMSMA<sup>NG</sup> with the correct configuration in this complicated context of multiple users and asynchronous data exchange is important to trouble-free operations and high-quality information management. The first step in ensuring the correct configuration is to document the information management flows.
In the following example, mine action field reports Data Entry Forms are entered at each regional site for the ongoing operations in that region. Field reports Data Entry Forms are reconciled, linked and approved according to the regional operations needs. Using the export functionality, the regional sites export data on a regular basis (for example, monthly) and send it to the central authority. (Regional information managers can use the search functionality to export the field reports Data Entry Forms entered since the last data exchange.) The central authority then imports the maXML files from each site and resolves any issues with the imports as well as performs quality control. When the import is complete, the central authority compiles a set of national statistics and then distributes a complete dataset (in the form of a database backup) to each of the regional sites. The regional sites restore the dataset and then import any data entered since the last export was sent to the central authority. When the backup is restored, regular data entry and exchange can continue, based on a common dataset.
==Ensuring Correct Roles and Permissions are Assigned==
Establishing correct roles and permissions is a key factor in managing and maintaining data exchange within IMSMA<sup>NG</sup>. Using the permissions structure, the information manager can carefully control access to key functions that affect data exchange including field report Data Entry Form template creation, CDF creation, field report Data Entry Form approvals and auxiliary data creation. When permissions are correctly established and roles and user accounts created, information managers can freely distribute the IMSMA<sup>NG</sup> dataset to regional partners knowing that key data controls are in place.
Using the example of the central authority and regional sites, the following principles for user account creation and permissions should be considered:
* <b>Central Authority:</b> Ensure central authority has exclusive control over user accounts and roles, field report Data Entry Form templates, the Data Inventory Manager and auxiliary data.
* <b>Regional Sites:</b> Ensure that regional sites have data entry, approval and import/export permissions. Remove permissions for user accounts and roles and auxiliary data.
By establishing a set of limited permissions for the regional sites, information managers can prevent the accidental or intentional creation of new data elements not available at the central authority that could affect the ability of the central authority to import field reports Data Entry Forms and cause the dataset to become fractured.
==Creating New Auxiliary Data at the Central Authority Level==
By limiting auxiliary data permissions to the central authority, information managers can prevent complications when synchronising field reportsData Entry Forms. Because field reports Data Entry Forms often refer to auxiliary data (places, ordnance, organisations, etc.), it is important that each site have a common set of auxiliary data to facilitate exchange. If the auxiliary data is not properly synchronised, the exchange of field reports Data Entry Forms can result in import issues which must be manually resolved. While IMSMA<sup>NG</sup> 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 authority who can then distribute an updated dataset as necessary. Likewise, limiting the creation of field report Data Entry Form templates, data elements and country structure levels to the central authority improves the ease of information exchange.
==Sending Backups to Reset to a Common Dataset==
The easiest way to ensure that each site is working from a common dataset is to distribute a full backup of the IMSMA<sup>NG</sup> dataset to each site on a regular basis. This can occur weekly, monthly or quarterly, but the key is to distribute an official‖ dataset to each site regularly to ensure that auxiliary data is up to date and that any changes made to other parts of the dataset are distributed. In this way, organisations can maintain a common set of national statistics and the dataset reflects the decisions made by the central authority to resolve errors or issues in importing and exchanging field reportsData Entry Forms.
It is important to understand, however, that the restoration of a backup file overwrites the data at the regional site including any locally created searches and reports. So, the recipient sites should consider the following recommendations:
* Make a complete backup prior to restoring the central authority’s backup.
* Export all field reports Data Entry Forms that have been entered since the last exchange with the central authority before restoring a backup.* Restore only the IMSMA<sup>NG</sup> database and GIS database. This preserves local customisations of peripheral elements such as field report Data Entry Form templates and iReport templates, which can be reimported into IMSMA<sup>NG</sup>.
* Request that any searches or other non-exportable elements that are important for regional site use be created in the central authority’s dataset prior to distribution so they do not need to be recreated regionally each time a new backup is distributed.
