16/04/2018

#	Discussion/Action	Responsible	Outcome	Status
1	Programme names/numbers aren’t provided for Dental trainees, they’re created by Admins	JH, AP, IO	Proposed Solution (JH) 3 letter use the prefix of the local office + 3 digit acronym based on specialty 3 digit specialty acronym should be consistent across all Action: AP/IO to impact assess JH: Done mapping and need to do some more work and send to AP. AP has received James ssheet. More generally, we should look to standardise naming conventions around programmes (not just Dental) to be discussed separately Next to put on Microsoft Teams and get SMLs feedback - AP JH/AP - Setup call to briefly explain next week. - Was decided that it should be postponed for the moment on advice from James. IO/AP: Recommendation: show a concatenated display of the programme name in the dropdown list with the Local Office name? To check with DEV on the possible solutions. (P1) TISDEV-3767 - Add indicator to drop downs to highlight "ownership" of values to the user TO DO 19/02: AP/JH: Field limit for programme number? Check field validation (Alistair Pringle (Unlicensed)) Max number of characters is 20 including spaces / special characters favoured approach is to change the programme number <max limit (Alice Thompson / Alistair Pringle (Unlicensed)) see dental spreadsheet prepared by JH 09/04: Sent to Andy, Programme number being changed as this was too long.	ON HOLD till post MVP launch
2	Data Quality dashboard to be shared with other regions from LASE		John to schedule time to review it 05/03 Claire to prod on what the progress is on this 05/03 JT to chase up when he's back in London on 06/03 12/03 Demo to be arranged, check if JH is back. Chris Norman to share SQl script. 26/03 JT to setup doodle poll to arrange date for demo. 09/04: To chase JT for this to be done. 16/04 - Taking place in the next few days.	OPEN
3	Data related support what should the escalation path be? does a new service desk channel need to be created?		individual logins for data leads need to be set up if not already existing. 09/04: CL: There is one being created - data queue on Service Desk	CLOSE
4	Start post funding discussion with local offices	JW/JH	Place holder AP/JH/IO: IO To update with ticket numnber and post on DQ channel.	ON HOLD till post MVP
5	Update on the missing placements (James/Claire) flagged on DQ channel - Data not pulling through rather than missing placements. Progress update on the checks between Intrepid and TIS UI (Claire)	JH/CL/IO	CL: Spreadsheet uploaded with feedback - Qualifications, Assessments and Placements issues identified.
5		CL/IO	IO to review the feedback from Claire 09/04: Claire Shared with other Data leads to test the UI and feedback - JH, AB & DS 15/04: Update? 19/04: Go through BAU tickets
6	Specialty Groups - What is it and is it needed for TIS?	Data leads	09/04: DS to check and confirm. Possibly V9 legacy field? Confirmed by data leads that it's not used	CLOSED
7	Placement import template v.s. Placement manager? Are these separate and are means to what end?	AP	AP: Follow up with Rob - Extract from NDW and feed into ETL?
8	Bulk Assessment template to be reviewed. Assessment - Bulk Uploads Assessment - Bulk Uploads#BulkUpload(DRAFT)-TISBulkAssessmentUploadTemplate(DRAFT)	Data leads CL/JH/AB/DS	AR: Share on DQ Slack channel
10	Bulk People Import - Feedback Check if the Expectations are correct on the Jira tickets	CL/AB	Check progress end of week on bug fixes. Release to users for testing.