| Item | Demo - from Prod URL where feasible |
|---|
Ensure that the funding body data is passed over to the NDW each day. | NDW ETL is the piece of code which runs everynight 12:20 am to export TIS data to NDW data warehouse so that report can be generated. The user requirements were to export the data of FundingbodyId field of PostFunding table and newly introduced TrainingPathway field field of ProgrammeMembership to the NDW. Those were exposed to NDW through the NDW ETL. NDW Team have confirmed those fields are in Prod. |
Work remaining from last Sprint:
Ensure that the training pathway field is included in the data passed over to the NDW each day. | As above |
| Give HEE Admins the ability to bulk update Posts Funding details as an efficient way of managing existing Post Fundings in bulk. |
|
We need to move our databases to be managed by our hosting provider (to ensure greater resiliency).
To do this we need to modify them (all) slightly first. |
|
| To indicate which placements are whole time equivalents on the summary screen, rather than force users to drill down to find out this information. | Loom video for demo: https://www.loom.com/share/6eac79d353b943b88cb2f5cb9e7c0eae |
| Team to assess outputs from the Trainee workshops, to determine what work should be carried out to get us to an MVP. |
|
| Introduce validation to prevent users from accidentally deleting a curriculum on a trainee record. |
|
Work remaining from last Sprint:
For those services that don't auto-restart, create an interface for any member of the team to restart any service that fails at any time of day in order to get that service back up and running as quickly as possible for users. |
|