Information Exchange Models - Revision history

Alnaucler at 17:45, 26 May 2017

2017-05-26T17:45:20Z

← Older revision		Revision as of 19:45, 26 May 2017
Line 43:		Line 43:
	* 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.		* 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 Information ~~Exchange~~}}		{{NavBox Manage Information}}
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 10:05, 9 July 2015

2015-07-09T10:05:53Z

← Older revision		Revision as of 12:05, 9 July 2015
Line 44:		Line 44:

	{{NavBox Information Exchange}}		{{NavBox Information Exchange}}
	[[Category:~~DSA~~]]		[[Category:NAA]]

Alnaucler at 15:22, 22 March 2015

2015-03-22T15:22:03Z

← Older revision		Revision as of 17:22, 22 March 2015
Line 1:		Line 1:
	{{Rewrite\| This page is under construction and needs illustrations & links/references to other pages}}		{{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__		==Sending Backups to Reset to a Common Dataset==__NOEDITSECTION__

Alnaucler at 11:54, 22 March 2015

2015-03-22T11:54:23Z

← Older revision		Revision as of 13:54, 22 March 2015
Line 1:		Line 1:
			{{Rewrite\| This page is under construction and needs illustrations & links/references to other pages}}

	==Sending Backups to Reset to a Common Dataset==__NOEDITSECTION__		==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.		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.

Alnaucler: Created page with "==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 bac..."

2015-03-22T11:51:28Z

Created page with "==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 bac..."

New page

==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.

It is important to understand, however, that the restoration of a backup file '''overwrites''' the data in the implementing partner's database including any Data Entry Forms that have not been sent to the Central Mine Action Authority yet, locally created searches and reports. So, the recipient implementing partners should consider the following recommendations:

* Make a complete backup prior to restoring the Central Mine Action Authority’s backup.
* Export all Data Entry Forms that have been entered since the last exchange with the Central Mine Action Authority before restoring a backup.
* Restore only the {{IMSMANG}} database and GIS database.
* Have a local copy of templates and Saved searches so they may be re-published and re-created in {{IMSMANG}}.
* 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 Information Exchange}}
[[Category:DSA]]

Information Exchange Models - Revision history

Alnaucler at 17:45, 26 May 2017

Alnaucler at 10:05, 9 July 2015

Alnaucler at 15:22, 22 March 2015

Alnaucler at 11:54, 22 March 2015

Alnaucler: Created page with "==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 bac..."

Alnaucler: Created page with "==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 bac..."