Difference between revisions of "Importing and Exporting"

From IMSMA Wiki
Jump to: navigation, search
 
(43 intermediate revisions by 7 users not shown)
Line 1: Line 1:
===How to Export Approved Field Reports===
+
{{TOC right}}
<p>The export feature allows you to save field report(s) that meet criteria that you specify to a file. This file can then be imported into another IMSMA system so that field reports can be shared.</p>
+
__NOEDITSECTION__
<p>To export approved field report(s):</p>
+
{{HowTo's
<ol>
+
|[[Import a Data Entry Form from a xml File]]
<li>From the File menu, select Export.</li>
+
|[[Search for Exporting Data Entry Form | Export Data Entry Form from Advanced Search]]
<li>From the Export menu, select Field Reports.</li>
+
|[[Export Data Entry Form from Workbench]]
:The Field Report Export window displays ([[:Image:fig179.png|Figure 179]]).
+
|[[Import the Translations|Import Translations]]
</ol>
+
|[[Export the Translations|Export Translations]]
 +
|[[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.
  
[[Image:fig179.png|center|500px|''Figure 179. Field Report Export Window'']]
+
==Data Entry Forms==__NOEDITSECTION__
<div align="center">
+
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]].  
''Figure 179. Field Report Export Window''
 
</div>
 
  
<ol start="3">
+
Data Entry Forms may be exported and imported in '''xml''' format.
<li>Enter your name in the '''Exported by''' field or leave it blank.</li>
 
<li>Click the [[Image:StrucInfoIcon.png]] button to select the country structure for the field report(s) you would like to export.</li>
 
:The Country Structure Selection window displays.
 
<li>From the Country Structure Selection window:</li>
 
<ol start="a">
 
<li>Click the country structure on which you would like to generate the report.</li>
 
<li>Click the '''OK''' button.</li>
 
</ol>
 
<li>Select one of the following date options for the field report:</li>
 
*''Date Approved'' – Applies the date range to the date that the field report was approved.
 
*''Date Reported'' – Applies the date range to the date that the field report was reported.
 
*''Last Updated Date'' – Applies the date range to the date that the field report was last updated.
 
<li>Select the date range that a field report must fall within:</li>
 
<ol type="a">
 
<li>Click the [[Image:DateInfoIcon.png]] button beside the Begin Date field to select the starting date.</li>
 
<li>Click the [[Image:DateInfoIcon.png]] button beside the End Date field to select the ending date.</li>
 
</ol>
 
<li>Click the '''Export''' button.</li>
 
:The Field Report Export Summary window displays a list of the field reports that match the criteria ([[:Image:fig180.png|Figure 180]]).
 
  
[[Image:fig108.png|center|500px|''Figure 180. Field Report Export Summary Window'']]
+
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.
<div align="center">
 
''Figure 180. Field Report Export Summary Window''
 
</div>
 
  
{| style="border:2px solid lightgray; float:center; margin:10px;"
+
==Translations==__NOEDITSECTION__
|align="left" style="padding: 5px 10px 5px 10px"|[[Image:bulb2.png|25px|Represents a tip or note for using IMSMA Mobile.]]
+
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.
|align="left" style="padding: 5px 10px 5px 10px"| The greater the number of field reports that meet the criteria specified in the Field Report Export window, the longer it will take the Field Report Export Summary window to display.  
 
|}
 
  
<ol start="9">
+
==Auxiliary Data==__NOEDITSECTION__
<li>Do one of the following:</li>
+
{{IMSMANG}} supports the export of Auxiliary data in two different formats:
*To export the field report(s), click the '''OK''' button.
+
* xml, for external tools such as [[Portal:Remote Entry |IMSMA Remote Entry]]
:The Save window displays.
+
* csv, for use in e.g. in Excel.
*To cancel the export operation, click the '''Cancel''' button.
 
<li>From the Save window:</li>
 
<ol type="a">
 
<li>Navigate to the directory where you would like to save the file.</li>
 
<li>Enter the name of the file in the File Name field.</li>
 
<li>Click the '''Save''' button.</li>
 
:The field report(s) are saved to the file and directory that you specified. When the export has completed, the Export Complete window displays.
 
</ol>
 
<li>Click the '''OK''' button.</li>
 
:The Export Complete window closes. An .XML file of the exported field reports is created in the directory that you specified.
 
</ol>
 
  
===How to Import Field Reports===
+
{{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]]. }}
<p>The import feature allows you to import field reports from another IMSMA system into your IMSMA system.</p>
 
  
{| style="border:2px solid lightgray; float:center; margin:10px;"
+
==Map Exports==__NOEDITSECTION__
|align="left" style="padding: 5px 10px 5px 10px"|[[Image:bulb2.png|25px|Represents a tip or note for using IMSMA Mobile.]]
+
The map is possible to export in two formats; pdf or apm (ESRI Arc Pad Map).
|align="left" style="padding: 5px 10px 5px 10px"| Before you import field reports, ensure that:
 
*The field report templates, custom defined fields, and option selection values have been imported into the receiving IMSMA system.
 
*The field report template name is exactly the same as the field report template name used by the field report that you are importing.
 
*The country structure levels and areas exist in the system.
 
|}
 
  
<p>Data will only be imported for attributes represented on your field report template. For example, if the field report(s) that you are importing use a template with 50 attributes, but your template only contains 20 of the 50 attributes, data will only be imported for the 20 attributes.</p>
+
==Non-Exportable Data==__NOEDITSECTION__
<p>To import a field report:</p>
+
Certain data within {{IMSMANG}} , particularly the administrative data, is not exportable to any external format. These include:
<ol>
+
* [[Saved Searches Window | Saved searches]],
<li>From the File menu, select Import.</li>
+
* [[Using the Impact Scoring Tool in IMSMANG | Impact scoring schemes]]
<li>From the Import menu, select Field Reports.</li>
+
* [[Defining Roles, Permissions and Users | Permissions]]
:The Field Report Import window displays ([[:Image:fig181.png|Figure 181]]).  
+
* [[Using the Tasking Tool in IMSMANG | Tasks and Work items]] and
</ol>
+
* [[Designing Summary Templates | Summary templates]].  
 +
Contact your [[Information Management Team | GICHD IM advisor]] if you need to export any of these.
  
[[Image:fig181.png|center|500px|''Figure 181. Field Report Import window'']]
+
==Import of data from other sources==__NOEDITSECTION__
<div align="center">
+
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.
''Figure 181. Field Report Import window''
 
</div>
 
  
<ol start="3">
+
{{NavBox IMSMA NG Administration}}
<li>Click the '''Browse''' button.</li>
 
:The Open window displays.
 
<li>From the Open window:</li>
 
<ol type="a">
 
<li>Navigate to the directory where the file that you would like to import is located.</li>
 
<li>Select the file name.</li>
 
<li>Click the '''Open''' button.</li>
 
:In the Field Report Import window, the number of field reports and the number of objects associated with the reports are displayed in the XML Summary section of the window. The contents of the file are displayed in the Raw XML View section.
 
</ol>
 
</ol>
 
  
[[Image:fig182.png|center|500px|''Figure 182. Field Report Import window'']]
+
[[Category:NAA]]
<div align="center">
 
''Figure 182. Field Report Import window''
 
</div>
 
 
 
<ol start="5">
 
<li>Click the '''Import''' button.</li>
 
:The Field Report Import Options window displays.
 
<li>In the Field Report Import Options window, select one of the options listed in Table 52.</li>
 
:If you do not want to import the field reports, click the Cancel button.
 
</ol>
 
 
 
<center>
 
{| class="wikitable" width="500"
 
|-
 
| align="center" colspan="2" | '''Table 52. Description of Import Options'''
 
|-
 
| width="125pt" | '''If you choose to…'''
 
| width="375pt" | '''The field reports...'''
 
|-
 
| Approve all field reports || <p>With no import errors and complete reconciliation are imported and marked as Approved.</p>
 
<p>With import errors and/or incomplete reconciliation are imported, marked as Needs Approval, and added to the Workbench.</p>
 
|-
 
| Import only  || <p>Are imported, marked as Needs Approval, and added to the Workbench.</p>
 
|}
 
</center>
 
 
 
<ol start="7">
 
<li>Click the '''OK''' button.</li>
 
:The Information window displays a message stating that the field report import is complete.
 
<li>Click the '''Close''' button.</li>
 
<li>If you chose the '''Approve all field reports''' option, the Approval Results window displays.</li>
 
</ol>
 
 
 
[[Image:fig63.png|center|500px|''Figure 183. Approval Results Window'']]
 
<div align="center">
 
''Figure 183. Approval Results Window''
 
</div>
 
 
 
<p>Field reports that were approved appear in the Approved Field Reports section of the Approval Results window. The Approval Date column lists the date and time the reports were approved.</p>
 
<p>Reports that were not approved appear in the Non-Approved Field Reports section. The Non-Approval column lists the reasons they were not approved. Possible reasons include ''Reconciliation Incomplete'', ''Import Error'', and ''Unknown Error''.</p>
 
 
 
<ol>
 
<ol type="a">
 
<li>Click the '''Done''' button.</li>
 
<li>If a field report was not approved, open the Workbench window and double-click the row associated with the unapproved field report.</li>
 
:The Field Report Editor window displays.
 
<li>Resolve the error on the Reconciliation tab if applicable. See the ''Field reports – [[Reconciling Items]]'' section for additional information.</li>
 
<li>Resolve the error on the Import Issues tab if applicable. When complete, check the '''All Import Issues have been resolved''' checkbox.</li>
 
<li>Click the '''Approve''' button.</li>
 
:The Information window displays confirming the field report was approved.
 
</ol>
 
</ol>
 
 
 
<ol start="10">
 
<li>If you chose the '''Import Only''' option, the Field Report Import Results window displays.</li>
 
</ol>
 
 
 
[[Image:fig184.png|center|500px|''Figure 184. Field Report Import Results Window'']]
 
<div align="center">
 
''Figure 184. Field Report Import Results Window''
 
</div>
 
 
 
<p>The Imported Items section of the window lists the items that were imported. Any errors that occurred during the import are noted in the Error Log section of the window. You can save the error log to a file by clicking the Save Log button.  You can also view import errors on the Import Issues tab of the Field Report Editor window.</p>
 
 
 
<ol>
 
<ol type="a">
 
<li>Click the '''Done''' button.</li>
 
:The imported field reports will be listed in the Workbench. You will need to reconcile the item records in the field reports.
 
</ol>
 
</ol>
 
 
 
[[Category:Maintaining IMSMA]]
 
[[Category:How To]]
 

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.