Migration of DrawMGT Systems into V2

Introduction

Currently a simple SQL script (script/migrate_drawmgt.sql ) is created as a prototype.

How to migrate passwords?
Revision code is currently a simple numeric value in V2 and can not be set by the user.
No place to migrate Comments.abstract.
How to migrate users with the same email address?
- Currently duplicate email addresses perpended by 'dup_#{users.id}_' if
  - the user is obsolete or test user,
    or the user id belonging to the same email address is not the highest one.
How to migrate roles?
Classification display parameters are specified on the record level in DrawMGT but not in V2.
How to migrate classification without code (in case of not selectable parent items in DrawMGT), e.g. LocationRef.
- Currently code is set to sortOrder.
It is possible in DrawMGT, that alignment is filled but chainage not. Should we allow it also in V2?

List fields currently ignored, but probably will be used later:

Table(s)	Fields
ContractRef	restrictedFlag
Groups	restrictedFlag
DocumentTypeRef	displayWorkFlowTypeId, layoutTypeId, restrictedFlag, parentId
RevisionTypeRef	restrictedFlag, parentId
CommentTypeRef	workFlowTypeId, layoutTypeId, restrictedFlag, parentId
Users	lockedFlag, testUserFlag, restrictedFlag, externalKey, languageId, companyId, address1-3, officePhone, mobilePhone, fax, skypeId, url, passwordDate, description
Tasks	only commentCode, groupId, firstResponsibleId, commentTypeId, firstCompleteDate, summary are migrated
TaskNotes	commentNoteTypeId, lockedFlag, restrictedFlag, obsoleteFlag, attachment, thumbnail

For classification tables:

Table(s)	Fields
ProjectPhaseRef, CategoryRef, LocationRef, WorkTypeRef, SiteClassification[1-4]Ref	searchOnlyFlag, displayClass, displayTextInput, displayTextDetail, displayTextList, displayHover
AlignmentRef	minChainage, maxChainage