Difference between revisions of "Importing and Exporting"
| (18 intermediate revisions by 4 users not shown) | |||
| Line 2: | Line 2: | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
{{HowTo's | {{HowTo's | ||
| − | |[[Import Data Entry | + | |[[Import a Data Entry Form from a xml File]] |
| − | |[[Export | + | |[[Search for Exporting Data Entry Form | Export Data Entry Form from Advanced Search]] |
| − | |[[Import the | + | |[[Export Data Entry Form from Workbench]] |
| − | |[[Export | + | |[[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 | + | {{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]]. | ||
| − | + | Data Entry Forms may be exported and imported in '''xml''' format. | |
| − | |||
| − | Data | + | 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__ | |
| + | 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==__NOEDITSECTION__ |
| − | + | {{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). | |
| − | {{NavBox | + | ==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. | ||
| + | |||
| + | {{NavBox IMSMA NG Administration}} | ||
| + | |||
| + | [[Category:NAA]] | ||
Latest revision as of 13:43, 16 June 2017
| 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 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:
- xml, for external tools such as IMSMA Remote Entry
- csv, for use in e.g. in Excel.
 |
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.
| |||||||||||||||||||
