NoPublic, bureaucrat, administrator
6,632
edits
Changes
no edit summary
{{Rewrite| This page is under construction and needs illustrations & links/references to other pages}}
==Model 1==__NOEDITSECTION__
maXML to National database and backup back
'''Pros'''
* Central control of user and roles
* Central control of Auxiliary data
* All implementing partners have the ''full'' picture
'''Cons'''
* Data Entry Forms created since maXML was imported into national database are lost
* Locally created database objects like saved searches, user preferences, templates and SQL views are lost(*)
==Model 2==__NOEDITSECTION__
maXML to National database and maXML back
'''Pros'''
* Data Entry Forms created since maXML was imported into national database are not lost lost
* Locally created database objects like saved searches, user preferences, templates and SQL views are not lost
'''Cons'''
* In order for all implementing partners to get the ''full'' picture they must import maXML which takes longer time time than restoring database
* Import Auxiliary data workaround possible but more vulnerable
Highlight the 3 different import options
The maXML files may '''not''' contain records already sent to national database (up direction)
The maXML files may '''not''' contain records sent by implementing partner to national database (down direction)
Import from folder
Implementing partner should be allowed to approve their own reports
NG or IRE?
==Sending Backups to Reset to a Common Dataset==__NOEDITSECTION__
One way to ensure that each implementing partner is working from a common dataset is to distribute a full backup of the {{IMSMANG}} dataset on a regular basis. The key is to distribute an official national dataset 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, implementing partners can maintain a common set of national statistics and the dataset reflects the decisions made by the Central Mine Action Authority to resolve errors or issues in importing and exchanging Data Entry Forms.
* Request that any customisation or other non-exportable elements that are important for implementing partners to be created in the national database prior to distribution so they do not need to be recreated each time a new backup is distributed.
{{NavBox Manage Information Exchange}}[[Category:DSANAA]]
