Difference between revisions of "Importing and Exporting"

From IMSMA Wiki
Jump to: navigation, search
 
(10 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
__NOEDITSECTION__
 
__NOEDITSECTION__
 
{{HowTo's
 
{{HowTo's
|[[Export a Data Entry Form to a MaXML File|Export Data Entry Forms]]
+
|[[Import a Data Entry Form from a xml File]]
|[[Import the Translated Terms|Import Translations]]
+
|[[Search for Exporting Data Entry Form | Export Data Entry Form from Advanced Search]]
|[[Export and Translate the Terms|Export Translations]]
+
|[[Export Data Entry Form from Workbench]]
 +
|[[Import the Translations|Import 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 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 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 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 '''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 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 [[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__
In addition to data entry forms, the translated terms of data elements can be exported and imported into {{IMSMANG}} . Using this functionality, information managers can take any translations that have been created for {{IMSMANG}} data elements and export them to .properties files that can be edited in external tools (such as Rosetta-J) and either exchanged with other {{IMSMANG}} systems or reimported into the same {{IMSMANG}} system.
+
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 auxillary data and map data, but this information cannot be imported back into an {{IMSMANG}} system. Instead these exports provide external tools such as IMSMA Remote Entry with the information to support data entry form data entry. Auxiliary Data tend to include auxillary data such as ordnance or country structure information. Moreover, they should always be exported in a maXML format.
+
{{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.
 +
 
 +
{{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__
 +
The map is possible to export in two formats; pdf or apm (ESRI Arc Pad Map).
  
 
==Non-Exportable Data==__NOEDITSECTION__
 
==Non-Exportable Data==__NOEDITSECTION__
Certain data within {{IMSMANG}} , particularly the administrative data, is not exportable in any external format. These include saved searches, impact scoring schemes and users and roles. Also included in non-exportable data are tasks, work items, and summary templates. This data can, however, be shared via backup files.
+
Certain data within {{IMSMANG}} , particularly the administrative data, is not exportable to any external format. These include:
 +
* [[Saved Searches Window | Saved searches]],  
 +
* [[Using the Impact Scoring Tool in IMSMANG | Impact scoring schemes]]
 +
* [[Defining Roles, Permissions and Users | Permissions]]
 +
* [[Using the Tasking Tool in IMSMANG | Tasks and Work items]] and  
 +
* [[Designing Summary Templates | Summary templates]].
 +
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 IMSMA NG Administration}}
  
[[Category:COO]]
+
[[Category:NAA]]

Latest revision as of 13:43, 16 June 2017

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

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 IMSMA Remote Entry.

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 approved from the 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

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

IMSMANG supports the export of Auxiliary data in two different formats:

Warning.jpg Note that neither xml or csv/xls cannot be imported back into an IMSMANG system without the help of a GICHD IM advisor.

Map Exports

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

Non-Exportable Data

Certain data within IMSMANG , particularly the administrative data, is not exportable to any external format. These include:

Contact your GICHD IM advisor if you need to export any of these.

Import of data from other sources

It is possible to import data from other sources or the Auxiliary data as mentioned above by using importing scripts. Contact your GICHD IM advisor if you have questions about import scripts.