Anonymous
Login

FoCul - IT for Engineers by Engineers

CAM2 Wiki

All users on the internet can see this document

Home > Data Migration Engine

Data Migration Engine

ShowTable of Contents

HideTable of Contents

1 Description
2 Data Migration Scheme

2.1 The old Database
2.2 Data Migration Error Reporting
2.3 Data Migration Notes Field
2.4 Link back to source
2.5 Rough notes from telecon 9th March
2.6 History

3 Specific Forms
4 General Notes on Functional Areas
5 Assumptions
6 Queries

Description

The data migration will be as automated as is practicable. This will allow the process to be re-run at different stages fo the project

Data Migration Scheme

The old Database

The old database will be retained indefinetley for the piping and vessel gasket specs.
We would also recommend that the old database is retained on the server in its full form for at least 6 months
and that DVD copies are made available indefinetley

Data Migration Error Reporting

Each migrated document will have a Data Migration Error Field
Errors will also be reported through the Error Logging module

Data Migration Notes Field

Link back to source

There will be a action menu option ( not button ) to open the source document in CAM1

Rough notes from telecon 9th March

Use a keyword document to define a migration step
Run the process against selected records
keyword document world look as follows

dryrun=yes
oldform=motors
newform=f_motors
template=notetofile++blah
filter=form=lhglsdfh - not necessary a boolean filter although that could be useful
parentrule=Use_Equipment_Header
defaultstatus=kgtlehglj
targetdatabase=this ( or a named database, using "this" means not having to keep changing it )
targetdatabase=d:/Focllhglthlj.nsf
skipmarkeditems=true * field called donotmigrate_tx
computewithform=yes
displayunmappedfields=yes ( see later - will dump unmapped fields into a simple field )

plant#plant_tx#ruleA
area#area_tx#rulea~rulec

migrationfield RT template = mignotes1_rtx#keywordhookforemailtemplate1
migrationfield RT template = mignotes2_rtx#keywordhookforemailtemplate2
migrationfield RT template = mignotes3_rtx#keywordhookforemailtemplate2

use $meta scheme to create links and populate data - SO NO HIERARCHICAL DATA SHOULD BE IMPORTED

migration history field
old and new need each others docunid - note need to overwrite this potentiially
consider doclink to old form would be useful - in migration notes field which is on a "lower priority tab"
consider an option to write unmigrated fields to new doc in a dedicated field

don't assume child and parent are in same database