Skills data is stored as SOR in MDMSv2 and needs mapping. After mapping, update the skills info in individuals' details and muster rolls with SOR. Use the provided migration script to help with this data update.
This migration is Mukta-specific, it will not be part of our master code.
To migrate data follow the steps given below:
Create Labour-Sor Mapping:
Add the following mapping to the expense.sor.migration.mapping field in the application properties: `{"UNSKILLED.CARPENTER":"SOR_000016", "SKILLED.CARPENTER":"SOR
You can also override it in the Helm (click here).
Use the Specific Build:
egovio/expense-calculator-db:sor-migration-8007f0108-142
Click here to access the branch and change details.
Build and Deploy:
Deploy the build provided above or build and deploy from the code linked above if custom changes are required.
Use the curl below to migrate the data.
Create table eg_sor_migration( id character varying(128), is_migration_successful boolean) ;
Query the eg_wms_attendance_summary table and check if “skillCode” in additionalDetails has been migrated from UNSKILLED.CARPENTER -> SOR_000016
Example:
Old data: additionalDetails : { …… skillCode : UNSKILLED.CARPENTER …… }
New data: additionalDetails : { …… skillCode : SOR_000016 …… }
Verification in DB for an individual: Query the individual_skill table and check if “type” and “level” are migrated to “SOR” and “SOR_code” respectively.
Example.:
Old data:
Type: CARPENTER
Level: UNSKILLED
New data:
Type: SOR
Level: SOR_000016
Once the migration is complete remove the environment variables added for migration.