__NOEDITSECTION__
{{HowTo's
|[[HowTo:Import Field Reports|Import Field Reportsa Data Entry Form from a xml File]]|[[HowTo:Search for Exporting Data Entry Form | Export Approved Field ReportsData Entry Form from Advanced Search]]|[[Export Approved Field ReportsData Entry Form from Workbench]]|[[HowTo:Import the Translations|Import Translations]]|[[HowTo:Export the Translations|Export Translations]]|[[HowTo:Export Auxiliary Data|Export Auxiliary Data]]|[[Import XLS data | Import of data from other sources]]
}}
{{IMSMANG }} provides extensive data export/import and export capabilities and formats designed to support a variety of purposes and needs. Using IMSMANG’s {{IMSMANG}}’s import and export functions, information managers Information Managers can exchange data directly with other {{IMSMANG systems, }} installations and export data for use in external tools and share data with other XML-compliant system.
==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==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 Data Entry Forms may be exported 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 imported in separate countries'''xml''' format.
Field report information may 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 exported [[Approve Data Entry Forms from the Workbench | approved]] from the [[Access and imported 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 maXML formatthe importing database.Table 16These issues can be resolved easily by creating the necessary auxiliary data and complete the Data Entry Forms. Comparison This functionality is designed to permit imports to continue even if some of MDML and maXMLthe linked data is missing.
Item MDML maXML==Translations==__NOEDITSECTION__Name Mobile In addition to Data Markup Language Mine Action Extensible Markup LanguageEntry 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.
Uses Exchange ==Auxiliary Data==__NOEDITSECTION__{{IMSMANG}} supports the export of field reports with Auxiliary data in two different formats:* xml, for external tools such as [[Portal:Remote Entry |IMSMA Mobile and IMSMANG Remote Entry]]* csv, for use in e.g. in Excel.
Exchange of unapproved field reports for quality assurance {{Warning | Note that neither xml or data entry Exchange csv/xls '''cannot''' be imported back into an {{IMSMANG}} system without the help of complete field report data including reconciliation and linksa [[Information Management Team | GICHD IM advisor]]. }}
Exchange of approved ==Map Exports==__NOEDITSECTION__The map is possible to export in two formats; pdf or unapproved field reports between IMSMANG systemsapm (ESRI Arc Pad Map).
==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.
Source Export ==Import of data from individual field reports, the Workbench, Search or the File menu other sources==__NOEDITSECTION__ Export It is possible to import data from individual field reports, the Workbench, Search other sources or the File menuReconciliation and Links No links or reconciliation information included Includes reconciliation and link information Auxiliary data as mentioned above by using importing scripts. Contact your [[Information Management Team | GICHD IM advisor]] if available Import To the Workbench To the Workbench or automatic approvalTemplates Uses MTML templates (IMSMA Mobile) or FFML templates (IMSMA RE); can select any field report template on you have questions about import FFML templates only. Requires publishing of correct field report template prior to import; can import CDFs using templatesscripts.
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. {{NavBox IMSMA NG Administration}}
==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.[[Category:NAA]]