Reference:
update tables
DBC&LocalOfficeTrust,Sitetable contains `localOffice`localOfficename.`LocalOfficeContact` only contains the localOfficeId, so there's no need to update it.
...
No need to update anything as it uses the designated body code instead of its name.
LocalOfficeToDbcMapperclass. It's not used anywhere. – should we move it or update it?
TCS:
DesignatedBodyMapperclass - this is also used for Reval syncPersonOwner- is populated by Sync service with Programme/Post owner and after that a person elasticsearch sync job needs to be triggered.Post- owner is from LocalOfficeProgramme- owner is from LocalOffice
NDW:
the name changes would impact the fields in NDW tables as below:
...
Query name
...
NDW table
...
Field name
...
post
...
vwPost
...
ManagingDeaneryLETB
...
assessment
...
vwAssessment
...
...
curriculum_membership
...
vwCurriculumMembership
...
ProgrammeManagingDeanery
...
person_owner
...
vwPersonOwner
...
Owner
...
programme_rotation_membership
...
vwProgrammeRotationMembership
...
ProgrammeManagingDeanery
...
programme
...
vwProgramme
...
ManagingDeanery
...
programme_curriculum
...
vwProgrammeCurriculum
...
ProgrammeManagingDeanery
...
programme_membership
...
vwProgrammeMembership
...
ProgrammeManagingDeanery
...
programme_post
...
vwProgrammePost
...
ProgrammeManagingDeanery
...
programme_rotation_post
...
vwProgrammeRotationPost
...
ProgrammeManagingDeanery
...
trust
...
vwTrust
...
DeaneryLETB
Revalidation:
A full sync from TCS -> Reval is needed to update the programmeOwner in Elasticsearch indices
UI repo doesn't use "Health Education England" prefix outside the specs
...
In ESRExporter db, there’s a Deanery table which look similar to local office table, do we need to care about it?
Traine Self Service (TSS)
...
The biggest risk for us is the pilot filter, we could potentially miss sending notifications during any period the values don't match.
We may need to update the code to match on both sets of values to cover the migration period.
NDW:
the name changes would impact the fields in NDW tables as below:
Query name | NDW table | Field name |
post | vwPost | ManagingDeaneryLETB |
assessment | vwAssessment | ProgrammeManagingDeanery |
curriculum_membership | vwCurriculumMembership | ProgrammeManagingDeanery |
person_owner | vwPersonOwner | Owner |
programme_rotation_membership | vwProgrammeRotationMembership | ProgrammeManagingDeanery |
programme | vwProgramme | ManagingDeanery |
programme_curriculum | vwProgrammeCurriculum | ProgrammeManagingDeanery |
programme_membership | vwProgrammeMembership | ProgrammeManagingDeanery |
programme_post | vwProgrammePost | ProgrammeManagingDeanery |
programme_rotation_post | vwProgrammeRotationPost | ProgrammeManagingDeanery |
trust | vwTrust | DeaneryLETB |
Downstream reporting & dashboards:
...
Leave Manager (Hicom) have not been contacted as far as I know so far so will need to check with them whether they can just accept the name change in their system or whether they need to do some work.
The Leave Manager ETL will need to be amended as it uses the Local Office Name as a filter.
Old repos:
- do we want to ignore them?
TIS-GMC-SYNC: DbcToLocalOfficeMap class
TIS-CONNECTION-DISCREPANCIES: DbcToLocalOfficeMap class
...