Difference between revisions of "Importing and Exporting"

From IMSMA Wiki
Jump to: navigation, search
 
(37 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
__NOEDITSECTION__
 
__NOEDITSECTION__
 
{{HowTo's
 
{{HowTo's
|[[HowTo:Import Field Reports|Import Field Reports]]
+
|[[Import a Data Entry Form from a xml File]]
|[[HowTo:Export Approved Field Reports|Export Approved Field Reports]]
+
|[[Search for Exporting Data Entry Form | Export Data Entry Form from Advanced Search]]
|[[HowTo:Import Translations|Import Translations]]
+
|[[Export Data Entry Form from Workbench]]
|[[HowTo:Export Translations|Export Translations]]
+
|[[Import the Translations|Import Translations]]
|[[HowTo:Export Auxiliary Data|Export Auxiliary Data]]
+
|[[Export the Translations|Export Translations]]
 +
|[[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 system.
+
{{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__
 +
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]].
  
==Field Reports==
+
Data Entry Forms may be exported and imported in '''xml''' format.
The primary mechanism IMSMANG uses for sharing information is the field report. As discussed in Chapter 1, field reports contain the vast majority of IMSMANG data and are the sole repository for entering operational information into the system. So, exporting and importing field reports let information managers easily share information between IMSMANG systems and other IMSMANG tools such as IMSMANG Remote Entry and IMSMA Mobile. 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.
 
  
Field report information may be exported and imported in either of two formats, maXML and MDML. Table provides an overview of the formats including the type of information sharing they support.
+
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.
  
Table 16. Comparison of MDML and maXML
+
==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.
  
Item MDML maXML
+
==Auxiliary Data==__NOEDITSECTION__
Name Mobile Data Markup Language Mine Action Extensible Markup Language
+
{{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.
  
Uses Exchange of field reports with IMSMA Mobile and IMSMANG Remote Entry
+
{{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]].  }}
  
Exchange of unapproved field reports for quality assurance or data entry
+
==Map Exports==__NOEDITSECTION__
Exchange of complete field report data including reconciliation and links
+
The map is possible to export in two formats; pdf or apm (ESRI Arc Pad Map).
  
Exchange of approved or unapproved field reports between IMSMANG systems
+
==Non-Exportable Data==__NOEDITSECTION__
 +
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.
  
Source Export from individual field reports, the Workbench, Search or the File menu
+
{{NavBox IMSMA NG Administration}}
Export from individual field reports, the Workbench, Search or the File menu
 
Reconciliation and Links No links or reconciliation information included
 
Includes reconciliation and link information if available
 
Import To the Workbench To the Workbench or automatic approval
 
Templates Uses MTML templates (IMSMA Mobile) or FFML templates (IMSMA RE); can select any field report template on import FFML templates only. Requires publishing of correct field report template prior to import; can import CDFs using templates.
 
  
When importing XML field reports 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 field report and must be resolved before the field report 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 field reports. This functionality is designed to permit imports to continue even if some of the linked data is missing.
+
[[Category:NAA]]
 
 
==Translations==
 
In addition to field reports, the translated terms of data elements 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.
 
 
 
==Auxiliary Data and Map Exports==
 
IMSMANG supports the export of base tables (or auxiliary data) and maps for certain external purposes. It is important to note that these exports are one-way and that the information cannot be imported back into an IMSMANG system. These exports are designed to provide external tools such as IMSMANG Remote Entry and IMSMA Mobile the information required to support field report data entry. These include typical auxiliary information such as ordnance, organisations, places and country structure information. Base tables are exported in maXML format.
 
 
 
Maps in IMSMANG can also be exported for use in IMSMA Mobile, ArcPad and the IMSMA Mobile application. These exports contain both base layers and IMSMANG data layers. Like base table exports, map exports are unidirectional and cannot be imported into an IMSMANG system.
 
 
 
==Non-Exportable Data==
 
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 current view templates. This data can, however, be shared via backup files.
 

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.