Information Exchange - Revision history

Alnaucler at 11:08, 4 May 2021

2021-05-04T11:08:38Z

← Older revision		Revision as of 13:08, 4 May 2021
Line 18:		Line 18:
	* producing maps with [[Connecting to IMSMA Staging area from ArcGIS \| external GIS]] software		* producing maps with [[Connecting to IMSMA Staging area from ArcGIS \| external GIS]] software
	* producing reports with [[Use iReport \| iReport]] and [[Connecting to IMSMA Staging area from Excel \| Excel]]		* producing reports with [[Use iReport \| iReport]] and [[Connecting to IMSMA Staging area from Excel \| Excel]]
	* producting online reports and dashboards with [[MINT]]
	* publish information to websites via the [[IMSMA Staging Area]].		* publish information to websites via the [[IMSMA Staging Area]].

Line 58:		Line 57:
	:* IMSMA backup		:* IMSMA backup
	:* Staging area database		:* Staging area database
	~~:* MINT~~
	:* website		:* website

Alnaucler at 14:23, 29 May 2017

2017-05-29T14:23:53Z

← Older revision		Revision as of 16:23, 29 May 2017
Line 109:		Line 109:
	By collecting feedback on these points, information managers can help ensure that data/information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.		By collecting feedback on these points, information managers can help ensure that data/information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.

	{{NavBox ~~Getting started with~~ IMSMA}}		{{NavBox IMSMA NG Administration}}
	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 13:42, 26 May 2017

2017-05-26T13:42:11Z

← Older revision		Revision as of 15:42, 26 May 2017
Line 55:		Line 55:
	:* Excel		:* Excel
	:* shape files		:* shape files
	:* ~~maXML~~		:* xml
	:* IMSMA backup		:* IMSMA backup
	:* Staging area database		:* Staging area database

Dionysia at 13:07, 13 November 2015

2015-11-13T13:07:02Z

← Older revision		Revision as of 15:07, 13 November 2015
Line 17:		Line 17:
	{{IMSMANG}} supports several methods for exchanging '''information''' including		{{IMSMANG}} supports several methods for exchanging '''information''' including
	* producing maps with [[Connecting to IMSMA Staging area from ArcGIS \| external GIS]] software		* producing maps with [[Connecting to IMSMA Staging area from ArcGIS \| external GIS]] software
	* producing reports with [[Use ~~i-Report~~ \| iReport]] and [[Connecting to IMSMA Staging area from Excel \| Excel]]		* producing reports with [[Use iReport \| iReport]] and [[Connecting to IMSMA Staging area from Excel \| Excel]]
	* producting online reports and dashboards with [[MINT]]		* producting online reports and dashboards with [[MINT]]
	* publish information to websites via the [[IMSMA Staging Area]].		* publish information to websites via the [[IMSMA Staging Area]].

Alnaucler at 10:05, 9 July 2015

2015-07-09T10:05:29Z

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

	{{NavBox Getting started with IMSMA}}		{{NavBox Getting started with IMSMA}}
	[[Category:~~DSA~~]]		[[Category:NAA]]

Alnaucler at 17:39, 3 April 2015

2015-04-03T17:39:52Z

← Older revision		Revision as of 19:39, 3 April 2015
Line 3:		Line 3:

	{{IMSMANG}} supports several patterns for exchanging '''data''' including		{{IMSMANG}} supports several patterns for exchanging '''data''' including
	* ~~multilateral~~ exchange		* one-direction exchange
			* two-direction exchange
	* peer-to-peer exchange		* peer-to-peer exchange
	* ~~one-direction exchange~~		* combinations of the above.
	* two-direction exchange.

	{{HowTo's		{{HowTo's

Alnaucler at 16:48, 3 April 2015

2015-04-03T16:48:13Z

← Older revision		Revision as of 18:48, 3 April 2015
Line 1:		Line 1:
	~~{{Rewrite\| This page is under construction and needs illustrations & links/references to other pages}}~~
	{{TOC right}}		{{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).		{{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).
Line 8:		Line 7:
	* one-direction exchange		* one-direction exchange
	* two-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.		The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners.

Line 31:		Line 36:
	\| '' Example of information exchange between stakeholders''		\| '' Example of information exchange between stakeholders''
	\|}		\|}
	~~</div>~~
	It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents with different periodicity.		It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents and with different periodicity.

	The following points need to be taken in consideration when planning exchange:		The following points need to be taken in consideration when planning exchange:
Line 57:		Line 62:

	==Workflows==__NOEDITSECTION__		==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?		* who does what?
	* how often?		* how often?
Line 63:		Line 69:
	* how and who corrects mistakes?		* how and who corrects mistakes?
	* who deletes data?		* who deletes data?
	* how decides final ID of ~~items?~~
			A process map of each exchange workflow is a good complement to the detailed written documentation of the workflow.

	==IMSMA specific rules==__NOEDITSECTION__		==IMSMA specific rules==__NOEDITSECTION__
			Data exchange workflows to the national database should include:
	* how to decide which Location to use?		* how to decide which Location to use?
	* which items should have links to what?		* which items should have links to what?
	* nice-to-have - desired - required data fields		* 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.}}		{{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__		===Ensuring Correct Roles and Permissions are Assigned===__NOEDITSECTION__
	Establishing correct roles and permissions is a key factor in managing and maintaining data exchange ~~within~~ {{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.		Establishing correct [[Defining Roles, Permissions and Users \| roles and permissions]] in {{IMSMANG}} is a key factor in managing and maintaining data exchange 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 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:		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 Central Mine Action Authority has exclusive control over
			:* user accounts and roles
			:* Data Entry Form templates
			:* Data Inventory Manager and
			:* Auxiliary data.
	* Ensure that the implementing partners have Data Entry, Approval and export/import Data Entry Forms permissions.		* 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 establishing a set of limited permissions for the implementing partners, information managers can prevent the accidental or intentional creation of new data elements 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 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.		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__		==Collecting Regular Feedback==__NOEDITSECTION__

Alnaucler at 16:09, 3 April 2015

2015-04-03T16:09:37Z

@@ Line 40: / Line 40: @@
 * who is the receiver?
 * what will the receiver use the data/information for?
 * will the receiver share the data/information in his turn?
 * how often?
@@ Line 51: / Line 55: @@
 :* MINT
 :* website
 ==Workflows==__NOEDITSECTION__
@@ Line 91: / Line 82: @@
 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 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.
 {{NavBox Getting started with IMSMA}}
 [[Category:DSA]]

Alnaucler at 16:02, 3 April 2015

2015-04-03T16:02:45Z

← Older revision		Revision as of 18:02, 3 April 2015
Line 23:		Line 23:

	==Plan Data/Information Exchange==__NOEDITSECTION__		==Plan Data/Information Exchange==__NOEDITSECTION__
	[[Image:Understanding Configuration Options - One way.png\|~~450px~~\|center\|]]		{\| class="wikitable"
	~~<div align="~~center">		\|-
	'' One way exchange plan only covering operators and national database ''		\| [[Image:Understanding Configuration Options - One way.png\|300px\|center\|]]
			\| [[Image:Information exchange.png\|300px\|center\|]]
			\|-
			\| '' One way exchange plan only covering operators and national database ''
			\| '' Example of information exchange between stakeholders''
			\|}
	</div>		</div>
	It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents with different periodicity.		It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents with different periodicity.

Alnaucler at 15:40, 3 April 2015

2015-04-03T15:40:52Z

← Older revision		Revision as of 17:40, 3 April 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}}
	{{TOC right}}		{{TOC right}}
	{{IMSMANG}} is designed to support 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).		{{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).

	{{IMSMANG}} supports ~~nearly any conceivable~~ patterns for exchanging '''data''' including		{{IMSMANG}} supports several patterns for exchanging '''data''' including
	* multilateral exchange		* multilateral exchange
	* peer-to-peer exchange		* peer-to-peer exchange
Line 10:		Line 10:
	The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners.		The most common pattern is two-direction exchange between a Central Mine Action Authority and implementing partners.

	{{IMSMANG}} supports ~~nearly any conceivable patterns~~ for exchanging '''information''' including		{{IMSMANG}} supports several methods for exchanging '''information''' including
	* producing maps with external GIS software		* producing maps with [[Connecting to IMSMA Staging area from ArcGIS \| external GIS]] software
	* producing reports with iReport and Excel		* producing reports with [[Use i-Report \| iReport]] and [[Connecting to IMSMA Staging area from Excel \| Excel]]
	* producting online reports and dashboards with MINT		* producting online reports and dashboards with [[MINT]]
	* publish information to websites via the Staging ~~area~~.		* publish information to websites via the [[IMSMA Staging Area]].

	[[Image:Data Information Organisation.png\|650px\|center]]		[[Image:Data Information Organisation.png\|650px\|center]]
Line 27:		Line 27:
	'' One way exchange plan only covering operators and national database ''		'' One way exchange plan only covering operators and national database ''
	</div>		</div>
	It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents at different periodicity.		It is easy for information managers at national level only to concentrate on how to exchange data that should be imported into the national {{IMSMANG}} database and forget that it should be a '''two'''-directional exchange and that '''all''' implementation partners, stakeholders and departments of the own organisation have different data/information needs and '''all''' of them have to create reports to several other receivers with different contents with different periodicity.

	The following points to be taken in consideration when planning exchange:		The following points need to be taken in consideration when planning exchange:
	* why is the data/information shared?		* why is the data/information shared?
	* what are the consequences if data/information are not shared on time?		* what are the consequences if data/information are not shared on time?
	* what data/information need/could be shared?		* what data/information need/could be shared?
	* ~~how~~ is the receiver?		* who is the receiver?
	* what will the receiver use the data/information for?		* what will the receiver use the data/information for?
	* will the receiver share the data/information in his turn?		* will the receiver share the data/information in his turn?
Line 45:		Line 45:
	:* Staging area database		:* Staging area database
	:* MINT		:* MINT
			:* website

	==Collecting Regular Feedback==__NOEDITSECTION__		==Collecting Regular Feedback==__NOEDITSECTION__
	In any information exchange activity, it is important to have regular ~~sessions~~ or meetings to collect feedback and discuss issues or improvements to the information exchange process. One recommendation is to establish a feedback forum where implementing partners and stakeholders can address data quality issues and make adjustments to the information exchange process. Topics to address in such a forum include:		In any data/information exchange activity, it is important to have regular follow-up or meetings to collect feedback and discuss issues or improvements to the data/information exchange process. One recommendation is to establish a feedback forum where implementing partners and stakeholders can address data quality issues and make adjustments to the data/information exchange process. Topics to address in such a forum include:

	* frequency of data exchange		* frequency of data/information exchange
	* standardisation of reports and searches included in the central dataset		* standardisation of reports and searches to be included in the central dataset
	* permissions and role changes		* permissions and role changes
	* creation or modification of Auxiliary data		* creation or modification of Auxiliary data
	* which data to collect		* which data to collect
	* changes of templates		* changes of templates
			* output products like reports, statistics, maps

	By collecting feedback on these ~~issues~~, information managers can help ensure that information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.		By collecting feedback on these points, information managers can help ensure that data/information exchange works as expected and set up a quality assurance mechanism to prevent data quality issues from affecting the Mine Action Programme.

	==Workflows==__NOEDITSECTION__		==Workflows==__NOEDITSECTION__