Importing and Exporting - Revision history

Alnaucler at 12:43, 16 June 2017

2017-06-16T12:43:39Z

← Older revision		Revision as of 14:43, 16 June 2017
Line 34:		Line 34:
	==Non-Exportable Data==__NOEDITSECTION__		==Non-Exportable Data==__NOEDITSECTION__
	Certain data within {{IMSMANG}} , particularly the administrative data, is not exportable to any external format. These include:		Certain data within {{IMSMANG}} , particularly the administrative data, is not exportable to any external format. These include:
	* [[~~Access the~~ Saved Searches Window \| Saved searches]],		* [[Saved Searches Window \| Saved searches]],
	* [[Using the Impact Scoring Tool in IMSMANG \| Impact scoring schemes]]		* [[Using the Impact Scoring Tool in IMSMANG \| Impact scoring schemes]]
	* [[Defining Roles, Permissions and Users \| Permissions]]		* [[Defining Roles, Permissions and Users \| Permissions]]

Alnaucler at 14:19, 29 May 2017

2017-05-29T14:19:36Z

← Older revision		Revision as of 16:19, 29 May 2017
Line 44:		Line 44:
	It is possible to import data from other sources or the Auxiliary data as mentioned above by using importing scripts. Contact your [[Information Management Team \| GICHD IM advisor]] if you have questions about import scripts.		It is possible to import data from other sources or the Auxiliary data as mentioned above by using importing scripts. Contact your [[Information Management Team \| GICHD IM advisor]] if you have questions about import scripts.

	{{NavBox ~~Getting started with~~ IMSMA}}		{{NavBox IMSMA NG Administration}}

	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 08:42, 29 May 2017

2017-05-29T08:42:16Z

← Older revision		Revision as of 10:42, 29 May 2017
Line 2:		Line 2:
	__NOEDITSECTION__		__NOEDITSECTION__
	{{HowTo's		{{HowTo's
			\|[[Import a Data Entry Form from a xml File]]
	\|[[Search for Exporting Data Entry Form \| Export Data Entry Form from Advanced Search]]		\|[[Search for Exporting Data Entry Form \| Export Data Entry Form from Advanced Search]]
	\|[[Export Data Entry Form from Workbench]]		\|[[Export Data Entry Form from Workbench]]
Line 16:		Line 17:
	Data Entry Forms may be exported and imported in '''xml''' format.		Data Entry Forms may be exported and imported in '''xml''' format.

	When importing Data Entry Forms in xml format into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ''import issues'' are tracked on each Data Entry Form and must be resolved before the Data Entry Form can be [[Approve Data Entry Forms from the Workbench \| approved]] from the [[Access and Use the Workbench Window \| Workbench]]. Typically, import issues are the result of references to Data Entry Form Template, Locations or Auxiliary data such as Places, Organisations, Ordnance or Country Structure elements that do not exist in the importing database. These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. This functionality is designed to permit imports to continue even if some of the linked data is missing.		When [[Import a Data Entry Form from a xml File \| importing Data Entry Forms]] in xml format into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ''import issues'' are tracked on each Data Entry Form and must be resolved before the Data Entry Form can be [[Approve Data Entry Forms from the Workbench \| approved]] from the [[Access and Use the Workbench Window \| Workbench]]. Typically, import issues are the result of references to Data Entry Form Template, Locations or Auxiliary data such as Places, Organisations, Ordnance or Country Structure elements that do not exist in the importing database. These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. This functionality is designed to permit imports to continue even if some of the linked data is missing.

	==Translations==__NOEDITSECTION__		==Translations==__NOEDITSECTION__

Alnaucler at 21:05, 26 May 2017

2017-05-26T21:05:45Z

← Older revision		Revision as of 23:05, 26 May 2017
Line 2:		Line 2:
	__NOEDITSECTION__		__NOEDITSECTION__
	{{HowTo's		{{HowTo's
	\|[[Search for Exporting Data Entry Form \| Export Data Entry from Advanced Search]]		\|[[Search for Exporting Data Entry Form \| Export Data Entry Form from Advanced Search]]
	\|[[Export Data Entry Form from Workbench]]		\|[[Export Data Entry Form from Workbench]]
	\|[[Import the Translations\|Import Translations]]		\|[[Import the Translations\|Import Translations]]

Alnaucler at 21:04, 26 May 2017

2017-05-26T21:04:59Z

← Older revision		Revision as of 23:04, 26 May 2017
Line 2:		Line 2:
	__NOEDITSECTION__		__NOEDITSECTION__
	{{HowTo's		{{HowTo's
	\|[[Search for Exporting Data Entry Form]]		\|[[Search for Exporting Data Entry Form \| Export Data Entry from Advanced Search]]
	\|[[Export Data Entry Form from Workbench]]		\|[[Export Data Entry Form from Workbench]]
	\|[[Import the Translations\|Import Translations]]		\|[[Import the Translations\|Import Translations]]

Alnaucler at 17:29, 26 May 2017

2017-05-26T17:29:25Z

← Older revision		Revision as of 19:29, 26 May 2017
Line 2:		Line 2:
	__NOEDITSECTION__		__NOEDITSECTION__
	{{HowTo's		{{HowTo's
	\|[[~~Export~~ Data Entry Form ~~from Workbench~~\|Export Data Entry ~~Forms~~]]		\|[[Search for Exporting Data Entry Form]]
			\|[[Export Data Entry Form from Workbench]]
	\|[[Import the Translations\|Import Translations]]		\|[[Import the Translations\|Import Translations]]
	\|[[Export the Translations\|Export Translations]]		\|[[Export the Translations\|Export Translations]]
	\|[[Export Auxiliary Data\|Export Auxiliary Data]]		\|[[Export Auxiliary Data\|Export Auxiliary Data]]
			\|[[Import XLS data \| Import of data from other sources]]
	}}		}}
	{{IMSMANG}} provides extensive data export/import capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, Information Managers can exchange data directly with other {{IMSMANG}} installations and export data for use in external tools.		{{IMSMANG}} provides extensive data export/import capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, Information Managers can exchange data directly with other {{IMSMANG}} installations and export data for use in external tools.
Line 37:		Line 39:
	* [[Designing Summary Templates \| Summary templates]].		* [[Designing Summary Templates \| Summary templates]].
	Contact your [[Information Management Team \| GICHD IM advisor]] if you need to export any of these.		Contact your [[Information Management Team \| GICHD IM advisor]] if you need to export any of these.

			==Import of data from other sources==__NOEDITSECTION__
			It is possible to import data from other sources or the Auxiliary data as mentioned above by using importing scripts. Contact your [[Information Management Team \| GICHD IM advisor]] if you have questions about import scripts.

	{{NavBox Getting started with IMSMA}}		{{NavBox Getting started with IMSMA}}

	[[Category:NAA]]		[[Category:NAA]]

Alnaucler at 13:37, 26 May 2017

2017-05-26T13:37:50Z

← Older revision		Revision as of 15:37, 26 May 2017
Line 2:		Line 2:
	__NOEDITSECTION__		__NOEDITSECTION__
	{{HowTo's		{{HowTo's
	\|[[Export a Data Entry Form ~~to a MaXML File~~\|Export Data Entry Forms]]		\|[[Export Data Entry Form from Workbench\|Export Data Entry Forms]]
	\|[[Import the Translations\|Import Translations]]		\|[[Import the Translations\|Import Translations]]
	\|[[Export the Translations\|Export Translations]]		\|[[Export the Translations\|Export Translations]]
	\|[[Export Auxiliary Data\|Export Auxiliary Data]]		\|[[Export Auxiliary Data\|Export Auxiliary Data]]
	}}		}}
	{{IMSMANG}} provides extensive data export/import capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, Information Managers can exchange data directly with other {{IMSMANG}} installations, export data for use in external tools ~~and share data with other maXML-compliant systems~~.		{{IMSMANG}} provides extensive data export/import capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, Information Managers can exchange data directly with other {{IMSMANG}} installations and export data for use in external tools.

	==Data Entry Forms==__NOEDITSECTION__		==Data Entry Forms==__NOEDITSECTION__
	The primary mechanism {{IMSMANG}} uses for sharing information is the Data Entry Forms. Data Entry Forms contain the vast majority of {{IMSMANG}} data and are the sole repository for entering operational information into the database. So, exporting and importing Data Entry Forms let Information Managers easily share information between {{IMSMANG}} installations and other {{IMSMANG}} tools such as [[Portal:Remote Entry \| IMSMA Remote Entry]].		The primary mechanism {{IMSMANG}} uses for sharing information is the Data Entry Forms. Data Entry Forms contain the vast majority of {{IMSMANG}} data and are the sole repository for entering operational information into the database. So, exporting and importing Data Entry Forms let Information Managers easily share information between {{IMSMANG}} installations and other {{IMSMANG}} tools such as [[Portal:Remote Entry \| IMSMA Remote Entry]].

	Data Entry Forms may be exported and imported in '''~~maXML~~''' format.		Data Entry Forms may be exported and imported in '''xml''' format.

	When importing ~~XML~~ Data Entry Forms into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ''import issues'' are tracked on each Data Entry Form and must be resolved before the Data Entry Form can be [[Approve Data Entry Forms from the Workbench \| approved]] from the [[Access and Use the Workbench Window \| Workbench]]. Typically, import issues are the result of references to Data Entry Form Template, Locations or Auxiliary data such as Places, Organisations, Ordnance or Country Structure elements that do not exist in the importing database. These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. This functionality is designed to permit imports to continue even if some of the linked data is missing.		When importing Data Entry Forms in xml format into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ''import issues'' are tracked on each Data Entry Form and must be resolved before the Data Entry Form can be [[Approve Data Entry Forms from the Workbench \| approved]] from the [[Access and Use the Workbench Window \| Workbench]]. Typically, import issues are the result of references to Data Entry Form Template, Locations or Auxiliary data such as Places, Organisations, Ordnance or Country Structure elements that do not exist in the importing database. These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. This functionality is designed to permit imports to continue even if some of the linked data is missing.

	==Translations==__NOEDITSECTION__		==Translations==__NOEDITSECTION__

Alnaucler at 14:10, 7 October 2016

2016-10-07T14:10:19Z

← Older revision		Revision as of 16:10, 7 October 2016
Line 24:		Line 24:
	* csv, for use in e.g. in Excel.		* csv, for use in e.g. in Excel.

	Note that neither xml or csv/xls '''cannot''' be imported back into an {{IMSMANG}} system without the help of a [[Information Management Team \| GICHD IM advisor]].		{{Warning \| Note that neither xml or csv/xls '''cannot''' be imported back into an {{IMSMANG}} system without the help of a [[Information Management Team \| GICHD IM advisor]]. }}

	==Map Exports==__NOEDITSECTION__		==Map Exports==__NOEDITSECTION__

Alnaucler at 10:46, 21 September 2016

2016-09-21T10:46:55Z

← Older revision		Revision as of 12:46, 21 September 2016
Line 19:		Line 19:
	In addition to Data Entry Forms, the translations of enumeration values can be exported and imported into {{IMSMANG}}. Using this functionality, Information Managers can export translations that already exists for a language or create a completely new translation file so it may be edited with Rosetta-J instead of translating one by one in the Data Inventory Manager.		In addition to Data Entry Forms, the translations of enumeration values can be exported and imported into {{IMSMANG}}. Using this functionality, Information Managers can export translations that already exists for a language or create a completely new translation file so it may be edited with Rosetta-J instead of translating one by one in the Data Inventory Manager.

	==Auxiliary Data ~~and Map Exports~~==__NOEDITSECTION__		==Auxiliary Data==__NOEDITSECTION__
	{{IMSMANG}} supports the export of Auxiliary data ~~but this information~~ '''cannot''' be imported back into an {{IMSMANG}} system~~. The exported xml files are for external tools such as~~ [[~~Portal:Remote Entry~~ \|~~IMSMA Remote Entry~~]].		{{IMSMANG}} supports the export of Auxiliary data in two different formats:
			* xml, for external tools such as [[Portal:Remote Entry \|IMSMA Remote Entry]]
			* csv, for use in e.g. in Excel.

			Note that neither xml or csv/xls '''cannot''' be imported back into an {{IMSMANG}} system without the help of a [[Information Management Team \| GICHD IM advisor]].

			==Map Exports==__NOEDITSECTION__
	The map is possible to export in two formats; pdf or apm (ESRI Arc Pad Map).		The map is possible to export in two formats; pdf or apm (ESRI Arc Pad Map).

Line 34:		Line 40:
	{{NavBox Getting started with IMSMA}}		{{NavBox Getting started with IMSMA}}

	[[Category:~~COO~~]]		[[Category:NAA]]

Alnaucler at 08:09, 17 August 2016

2016-08-17T08:09:04Z

← Older revision		Revision as of 10:09, 17 August 2016
Line 7:		Line 7:
	\|[[Export Auxiliary Data\|Export Auxiliary Data]]		\|[[Export Auxiliary Data\|Export Auxiliary Data]]
	}}		}}
	{{IMSMANG}} provides extensive data import ~~and export~~ capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, ~~information managers~~ can exchange data directly with other {{IMSMANG}} ~~systems~~, export data for use in external tools and share data with other ~~XML~~-compliant systems.		{{IMSMANG}} provides extensive data export/import capabilities and formats designed to support a variety of purposes and needs. Using {{IMSMANG}}’s import and export functions, Information Managers can exchange data directly with other {{IMSMANG}} installations, export data for use in external tools and share data with other maXML-compliant systems.

	==Data Entry Forms==__NOEDITSECTION__		==Data Entry Forms==__NOEDITSECTION__
	The primary mechanism {{IMSMANG}} uses for sharing information is the ~~data entry form~~. Data ~~entry forms~~ contain the vast majority of {{IMSMANG}} data and are the sole repository for entering operational information into the ~~system~~. So, exporting and importing ~~data entry forms~~ let ~~information managers~~ easily share information between {{IMSMANG}} ~~systems~~ and other {{IMSMANG}} tools such as IMSMA Remote Entry~~. Information managers can share large or small amounts of data directly with other {{IMSMANG}} users whether they are working together in the same programme or in separate countries~~.		The primary mechanism {{IMSMANG}} uses for sharing information is the Data Entry Forms. Data Entry Forms contain the vast majority of {{IMSMANG}} data and are the sole repository for entering operational information into the database. So, exporting and importing Data Entry Forms let Information Managers easily share information between {{IMSMANG}} installations and other {{IMSMANG}} tools such as [[Portal:Remote Entry \| IMSMA Remote Entry]].

	Data ~~entry forms information~~ may be exported and imported in maXML format.		Data Entry Forms may be exported and imported in '''maXML''' format.

	When importing XML ~~data entry forms~~ into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ~~“import issues”~~ are tracked on each ~~data entry form~~ and must be resolved before the ~~data entry form~~ can be approved. Typically, import issues are the result of references to ~~auxiliary~~ data such as ~~places~~, ~~organisations~~, ~~ordnance~~ or ~~country structure~~ elements that do not exist in the importing ~~system~~. These issues can be resolved easily by creating the necessary auxiliary data and ~~re-importing~~ the ~~data entry forms~~. This functionality is designed to permit imports to continue even if some of the linked data is missing.		When importing XML Data Entry Forms into {{IMSMANG}} , there are occasionally problems with the data that cause the data to not be fully imported. These ''import issues'' are tracked on each Data Entry Form and must be resolved before the Data Entry Form can be [[Approve Data Entry Forms from the Workbench \| approved]] from the [[Access and Use the Workbench Window \| Workbench]]. Typically, import issues are the result of references to Data Entry Form Template, Locations or Auxiliary data such as Places, Organisations, Ordnance or Country Structure elements that do not exist in the importing database. These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. This functionality is designed to permit imports to continue even if some of the linked data is missing.

	==Translations==__NOEDITSECTION__		==Translations==__NOEDITSECTION__
	In addition to Data Entry Forms, the translations of enumeration values can be exported and imported into {{IMSMANG}}. Using this functionality, ~~information managers~~ can export translations that already exists for a language or create a completely new translation file so it may be edited with Rosetta-J instead of translating one by one in the Data Inventory Manager.		In addition to Data Entry Forms, the translations of enumeration values can be exported and imported into {{IMSMANG}}. Using this functionality, Information Managers can export translations that already exists for a language or create a completely new translation file so it may be edited with Rosetta-J instead of translating one by one in the Data Inventory Manager.

	==Auxiliary Data and Map Exports==__NOEDITSECTION__		==Auxiliary Data and Map Exports==__NOEDITSECTION__