...
2. MVP - Proposed Business Process to Import Trainees from Oriel into TIS:
3. Excel workbook with fields identified for Step 2 and Step 5from Oriel that will be extracted and stored and those that will not.
| View file | ||||
|---|---|---|---|---|
|
...
| # | Question | Comment | Owner |
|---|---|---|---|
| 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. | ||
| 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. | ||
| 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? | ||
| 4 | Workbook on sub heading 4 was put together with input provided by Claire Lehoux. There still need to have data tidied up in the DR. | ||
| 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. | ||
| 6 | Reference data changes on Oriel will need to be coordinated with TIS going forward. | ||
| 7 | Custom report can be built on Oriel to extract a list of trainnes for specific programme/s where they have accepted an offer or withdrawn after accepting. | ||
| 8 | Documents will be generated as part of Step 2 of the Process Diagram.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. | ||
| 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? | ||