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__