Difference between revisions of "Importing and Exporting"
| Line 7: | Line 7: | ||
|[[Export Auxiliary Data|Export Auxiliary Data]] | |[[Export Auxiliary Data|Export Auxiliary Data]] | ||
}} | }} | ||
| − | {{IMSMANG}} provides extensive data import | + | {{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 | + | 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 | + | Data Entry Forms may be exported and imported in '''maXML''' format. |
| − | When importing XML | + | 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, | + | 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__ | ||
Revision as of 10:09, 17 August 2016
| How To |
|---|
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
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 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 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 and Map Exports
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 IMSMA Remote Entry. 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.
