PQA Clearquest: Resolving remaining issues with bad data
This is to document all of the issues related with bad data in the source databases that is impeeding the PQA Merge process. Along with the issues I will present what I did to work around the problems and what I suggest we should do to provide a smooth transition of these databases
Resolving Data Conversion Problems in PQA Database Merge
New fields that are mandatory
The following fieilds are new in the destination database (Cont) and are also mandatory thus must be filled in with something:
- Cont:Found_On_Gold: This field is defaulted to No.
Fields with blank or invalid data
The following fields have blank or invalid data in the source database thus fail validation when added to the new database:
- TO:SQATestCase: This field, when blank, is set to the string "N/A". This field is also renamed to Cont:PQATestCase.
- TO:Title_2: This field, when blank, is set to the string "N/A". This field is also renamed to Cont:TItle.
- Prod:Software_Version: This field, when blank, is set to the string "N/A".
- Prod:HUT_Version: This field, when blank, is set to the string "N/A". This field is also renamed to Cont:Board_Revision.
- Prod:Software_Version: This field, when blank, is set to the string "N/A".
- Prod:SQATestCase: This field, when blank, is set to the string "N/A". This field is also renamed to Cont:PQATestCase.
Fields with data that are no longer valid in new database
The following fields have data in the source database but fail validation when added to the new database due to reasons like not being on the list of acceptable values for the field in question:
- Prod:Category This field sometimes has the value of Hardware or System Bios which are not valid choices in the new database. For now I am changing Hardware -> Hardware - Chip and System Bios -> Software. I suggest we add Hardware and System Bios to the constant list as HARDWARE and SYSTEM BIOS (Capitalized) so we can easily find and correct these later.
- Prod:Issue_Classification: This field sometimes has the value of Hardware which is not a valid choice in the new database. For now I'm changing Hardware -> Requirement. I suggest we add Hardware to the constant list as HARDWARE (Capitalized) so we can easily find and correct these later.
- Prod:Resolution: This field sometimes has the value of HW Fix or MAC Core which are not valid choices in the new database. For now I am changing HW Fix -> HW - Fix and MAC Core -> SW Fix. I suggest we add HW - Fix and MAC Core to the constant list as HW - FIX and MAC CORE (Capitalized) so we can easily find and correct these later.
- Prod:HUT_Revision: This field is sometimes set to "n/a". This is translated to "N/A" (note capitalization).
Fields that need truncating
The following fields have data that is too large to fit in the size of the corresponding field in the destination database:
- Prod:ActionNotes: This field is defined with a maximum length of 50 characters in the TO database, 250 characters in the Prod database and 50 characters in the Cont database. Some entries in the Prod database are greater than 50 characters thus require truncation. I suggest that we increase the maximum length of Cont:ActionNotes to 250 characters to avoid this problem.