initiation MCI duplication to record student data

We now write new and updated data to MCI as the golden copy, e.g. from online registration, but we didn't migrate historic data. This was de-scoped from SAC096 and flagged as phase 2 to be done under Technical legacy project (SAC102 not opened yet) -  

This MCI work will be planned as an enhancement later, to be added to SSP programme plan for 2024 (dependent on when Tribal removes the data from STU table) . MCI holds the reportable characteristics of a student. This data tends to be quite sensitive in some cases and should therefore be kept separately from other student data. It is also used as a data source for HESA Statutory Returns. The benefit of moving to MCI: does not have to manage dual maintenance of storing/updating data on both Student and MCI tables. Another benefit will be to use Tribal out of the box recommended process. Not doing it will leave us open to potential reporting errors.

Benefits

- data security, data protection

-early solution: synch 1st Stu/MCI

-long term: move golden copy to MCI

Resources

-SDev: Ryan-SITS evision Vue (David as support, Ewan for UCAS data import) 

-Dev : Peter-Eugex changes

-SBA: process review AC

-BI Jamie

-Craig 

Estimates- Medium- 100d