Page Content
- Background
- Diagram for Proposed Business Process to Import Trainees from Oriel into TIS
- Excel workbook with fields from Oriel that will be extracted and stored and those that will not
- Excel workbook with Reference Data mapping
- Immigration Statuses Reference data from Oriel for 2017 and 2018
- Discussion and Assumptions
1. Background:
The TIS-Oriel integration is a file based export from Oriel of Trainee details and the programmes they've been accepted on to. This will include Trainees that are new to TIS and those who have already been on TIS programmes. New Trainees will cause Trainee record creation and user on-boarding within Trainee User Management.
TIS-618 - Getting issue details... STATUS
2. MVP - Proposed Business Process to Import Trainees from Oriel into TIS:
3. Excel workbook with fields from Oriel that will be extracted and stored and those that will not.
4. Excel workbook with Reference Data mapping
5. Immigration Statuses Reference data from Oriel for 2017 and 2018
6. Discussion and Assumptions:
| # | Question | Comment | Owner | Jira Ticket |
|---|---|---|---|---|
| 1 | In the workbook on sub heading 3, there are fields that are reference data from Oriel and require further data mapping to be done. | Agreed that wherever possible we will adopt Oriel ref tables to avoid having differences and having to map the data. Ashley to check impact on ESR interface to determine which tables we can do this for. Agreed that nationality will have to align with ESR as data passes through interface so this must be mapped. | Data Leads | TISDEV-3356 - Getting issue details... STATUS |
| 2 | In the workbook on sub heading 3, there are fields that are not necessarily mandatory on Oriel and would therefore only pull through if the applicant/trainee has provided the information on their application form, e.g. National Insurance number, Religious belief, Sexual Orientation etc. | Recommendation is that if completed in Oriel that it is pulled through into TIS. | Data Leads | TISDEV-3357 - Getting issue details... STATUS |
| 3 | In the workbook on sub heading 3, there are fields that are on the Recruitment Import template but not Oriel. Which of these fields are required in the template and where would these be sourced from? Which of these should be mandatory? | Feedback received from Claire and Alice as to which one to keep on the template and which one to remove. Ashley to consolidate a draft of the amended template and share. | Data Leads | TISDEV-3358 - Getting issue details... STATUS |
| 4 | Workbook on sub heading 4 was put together with input provided by Claire Lehoux. Although separate from Reference data mapping, there still need to have legacy data tidied up in the DR. Not related to the Oriel integration but for data quality in general. | Data Leads | TISDEV-3359 - Getting issue details... STATUS | |
| 5 | Workbook on sub heading 5 has a list of Immigration statuses discrepancies that requires mapping. Oriel reference data for 2017 and 2018 have different list of values that will be passed on to TIS. | Agreed not to map and just take Oriel values as Intrepid data is not accurate and up to date. Regarding the 2 new questions added for immigration on 2018 application form in Oriel, the recommendation is to record these as 2 new fields on TIS.
| Data Leads | TISDEV-3360 - Getting issue details... STATUS |
| 6 | Reference data changes on Oriel will need to be coordinated with TIS going forward. | Data Leads | TISDEV-3313 - Getting issue details... STATUS | |
| 7 | Custom report can be built on Oriel to extract a list of trainees for specific programme/s where they have accepted an offer or withdrawn after accepting. This task is to:
| Data Leads | TISDEV-3361 - Getting issue details... STATUS | |
| 8 | Documents will be be extracted from Oriel and stored on TIS in a data structure on Azure to be consumed by the Bulk Upload function during trainee records creation. | For info only. | Data Leads | |
| 9 | The Recruitment Import template may need to be changed to have new columns or some columns removed if not needed. For e.g. ApplicantID may need to be added to accomodate for the above Process. Some of the columns in the current Recruitment import template in its current format, will overlap with the fields that are received from Oriel. Do we want to keep them in the template? Which of the overlapped fields would be best to be manually filled? | ApplicantID will be added. Next steps are: SImilar action to #3. | Data Leads | TISDEV-3362 - Getting issue details... STATUS |
| 10 | The Recruitment Import template will be used both for creating and updating records on TIS. In a scenarion where records already eixist on TIS, what should be the best course of action by the Upload function? For e.g. should all or a selection of fields on TIS be updated/overwritten? | Data Leads | TISDEV-3377 - Getting issue details... STATUS |
0 Comments