Document MVP options for AB portal replacement

DFE-Digital / ecf2

This application will replace the Manage training for early career teachers service in 2025.

5 stars 0 forks source link

Document MVP options for AB portal replacement #76

Closed bbelward closed 1 week ago

bbelward commented 1 month ago

Why?

The database of qualified teachers and existing TRA owned AB portal must be switched off by April 2025. The business case and funding runs out so we won't have money or a mandate to delay this work any further.

The TRA will find migrating induction data to TRS significantly less risky if a replacement AB portal is created.

As owners of induction data, and because of doing an induction discovery in 2024, CPD are best placed to decide what an AB MVP could look like and

What?

Drafting in this doc

Based on what we know from Induction Discovery, kick off what the AB portal replacement must do, for example:
It must have a way of sharing data with TRS
It must fit the TRS data model
We must separate what is statutory data and not
Are there absolute musts?

Out of scope

Deciding governance - how we make sure we deliver what we need to and have the right responsibilities and comms and visibility set up with TRA

Helpful links or other information

claire-hughez commented 1 month ago

We must separate what is statutory data and not Is this definitely true? Have the TRA asked for this? TRA have not decided what data is 'statutory' and I think from talking to Rob C this is a bit of a weird word that's used strangely. The default for now is to send them everything that is currently collected in DQT. Which is given here in the DQT API docs:

}, "induction": { "startDate": "2024-08-08", "endDate": "2024-08-08", "status": "Exempt", "statusDescription": "string", "certificateUrl": "string", "periods": [ { "startDate": "2024-08-08", "endDate": "2024-08-08", "terms": 0, "appropriateBody": { "name": "string" } }

peteryates commented 1 month ago

Perhaps it's more useful to categorise the AB data into two lists:

data we need to record
data we need to pass through to the TRS API

We need to save all of it together in our database.

claire-hughez commented 1 month ago

Perhaps it's more useful to categorise the AB data into two lists:

The TRA have stated they're not sure yet of what they want passed on, but Mili also suggested chasing them on this. I think we know at the least they want the final induction status and the induction end date. Is there anything this would be particularly useful for at this stage?

gracecbrennan commented 1 month ago

@emily-prudence-dfe is prioritising the questions drafted in the doc.

gracecbrennan commented 1 month ago

@emily-prudence-dfe has been focusing on unknowns ahead of session tomorrow.

gracecbrennan commented 3 weeks ago

@emily-prudence-dfe has been working on the MVP doc and has something to share today.

Will be sharing with Nathan today.

gracecbrennan commented 3 weeks ago

@emily-prudence-dfe looking for answer today on what we need to do in terms of displaying induction period data.

gracecbrennan commented 3 weeks ago

Emily.P and Nathan had a catch up on extensions and pauses - these will be written up and shared with Phil today for approval/comment

claire-hughez commented 2 weeks ago

Set up conversations to agree things for the AB portal replacement. Trying to find time with Phil G.

claire-hughez commented 2 weeks ago

Induction period with AYTQ mainly sorted. Will get workshop in for sizing and feasibility.

Talking to TRA today.

mason-emily commented 1 week ago

Emily.P has been prepping for digital delivery board today.

Yday convo with TRA transformation on timelines - end of Jan delivery date? This was agreed.

peteryates commented 1 week ago

This is now being tracked by #193.