Changes

Jump to: navigation, search

Implementation plan

2,368 bytes added, 21:45, 9 April 2015
no edit summary
{{TOC right}}
==Process overview==__NOEDITSECTION__
# Go through the check list below and get an idea on '''what''' else than sending a 6.0 backup needs to be done
# Get a '''full''' backup and configuration details from the country
# Clean-up your dataset and collect all data
# Plan the next activities
===Check with the countries===__NOEDITSECTION__
* Do they use import scripts
: All scripts needs to be reviewed and adapted to PostgreSQL/V6.0, see [[Script changes 6.0]];
: Manual update of the column ''position'' in table cdfvalue need to be added.
 
* Do they import geodata Excel or shp <br /> Do their templates and/or procedure work with V6.0 and ArcGIS 10.1?
 
* Do they have Saved searches that are malfunctioning in 5.0.4 or are using SQL criteria?
: There are many database changes between previous versions and V6.0 and therefore existing saved searches might need to be updated.
: The new saved searches might need to be adapted to the country's terms and process.
 
* Will Data entry templates need a review?
: There are many database changes between previous versions and V6.0 and therefore existing templates might need to be updated. In the Using IMSMA portal, Viewing and Browsing, [[Items Pane]] there are lists with the new fields added in the upgrade.
 
* Summary templates
: The 5.08.04 summary templates that the countries had developed get status ''Archived'' during the upgrade process. The 5.08.04 summary templates may contain fields that do not exist anymore and therefore it is ''"safer"'' to customize the new standard summary templates by e.g. add CDFs to them than to adjust the 5.08.04 summary templates to 6.0.
 
* iReports
: Please note when you upgrade an existing database existing iReports will not automatically be upgraded. The required changes are documented on the [[Upgrade iReports to 6.0]] page.
 
* SQL views
: The SQL views needs to be redone in PostgreSQL and may be redone from scratch or by editing view.sql (output from the extracting step).
 
* Do they have data stored in CDFs that there are standard fields for in V6.0?
: If yes, is there performance or other gains by moving the data to standard fields?
: If yes, the source and target fields need to be mapped. There is a template Excel file for that.
 
* Users and permissions
: Are there any users that should be inactivated?
: Does existing users have appropriate permissions?
 
* Have the country imported all maXML and mdml files to the workbench?
: maXML files created by 5.0.4 are not possible to import in 6.0 and the mdml format is discontinued
==Full backup and configuration details==__NOEDITSECTION__
6,632
edits

Navigation menu