QT QA Migration » History » Version 3
Kurt Gerber, 16 Nov 2016 11:52
1 | 1 | Kurt Gerber | h1. QT QA Migration |
---|---|---|---|
2 | |||
3 | 3 | Kurt Gerber | h2. 1. Process Overview |
4 | 1 | Kurt Gerber | |
5 | There are different steps take, same for technology as for approaches: |
||
6 | |||
7 | 2 | Kurt Gerber | # *Mapping* between the new questionnaire in qcat.wocat.net and the old questionnaire in qt.wocat.net |
8 | 1 | Kurt Gerber | ** This mapping says which attribute/question in qcat takes the information from which attribute in qt |
9 | ** It explains the transformation, which has to be done from the old attribute to the new one. |
||
10 | 2 | Kurt Gerber | # *Migration script* which |
11 | 1 | Kurt Gerber | ** extracts the data from the old database (qt.wocat.net) |
12 | ** transforms the data based on the rules defined in the mapping table |
||
13 | ** imports the case in the new database (qcat.wocat.net) in draft mode |
||
14 | # *Post-editing* all imported cases |
||
15 | ** Adding missing data by coping from qt what was not automatically imported. |
||
16 | ** Reviewing the cases and publishing them to make them available publically. |
||
17 | 3 | Kurt Gerber | |
18 | |||
19 | h2. 2. Mapping between old and new questionnaire |
||
20 | |||
21 | This mapping is needed for the two following actions: |
||
22 | * For the development of the migration script. |
||
23 | * For the post-editing in qcat to find the missing data in the old qt. |
||
24 | |||
25 | Therefore it needs the mapping in two forms: |
||
26 | Once with the qcat questions as index/keys and once with the qt questions as index/keys... |
||
27 | |||
28 | h2. Migration script / Extract-Transform-Insert |
||
29 | |||
30 | h3. How it works |
||
31 | 1. Migration script migrates all cases and their attributes automatically, as long as¨.. |
||
32 | |||
33 | * transform doesn't produce errors because of inconsistent or wrong data |
||
34 | ** Example: If a value should have been selected only once but was then selected twice. -> the script produces an error |
||
35 | * transformation can be done automatically |
||
36 | ** Example: In the old questionnaire, several values could be selected, in the new one only one. -> Transform can't be made automatically. |
||
37 | |||
38 | 2. In cases of errors or the impossiblity of automatic transform: |
||
39 | * Not migrated or problematic questions (in qcat) are listed per case id in a migration log. |
||
40 | |||
41 | 3. All cases are inserted as 'submitted for review' in qcat. |
||
42 | |||
43 | |||
44 | |||
45 | h2. 3. Post-editing of imported cases in qcat |
||
46 | |||
47 | * The post-editing person needs two things: |
||
48 | ** The migration log |
||
49 | ** The mapping table |
||
50 | |||
51 | * Post-editing tasks: |
||
52 | ** Adding the missing data from qt.wocat.net follwoing the migration log and using the mapping table |
||
53 | ** Publishing the cases |
||
54 | |||
55 | *Question:* When should the compiler be informed about the transfer? |
||
56 | *Suggestion:* When the case is published on qcat. |