| 7 | Validation on surname casing, such as McCarthy
Currently the code will tidy up any issues with names entered for example like:- ”aNN aPPrentice”
There has been a request to see what could be done where names have a “Son of” derivative (Mac, Mc or O') as the casing on the ROA appears with the single capital letter i.e. Mccarthy.
The issue is if we remove the current code that tidies up casing, this would mean that you would need to tidy up every apprentice entry where the casing is incorrect manually?
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
|---|
| key | SD-7404 |
|---|
|
(POLL Available) |
| 8 | Integrated feedback forms for Assessment Results for Providers (relates to | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
|---|
| key | SD-9502 |
|---|
|
) Is this something customers use in addition to the fields in epaPRO? If yes, can you send us some examples of these please so we can see the level of detail you want? Would you ever move away from these forms that you currently use if we developed something within epaPRO to help us ascertain if the work would be utilised?
| 9 | Are customers using the Confirmed Toggle on the Planning Meetings?
mentioned on SD-10286
Image Removed
It was added to allow you to confirm the attendees at the time of the meeting being scheduled if known. These then appear on the Element Info list of attendees.
We would like to know if anyone is using it as there is no other functionality linked to it and we are wondering if it should be removed?
10 | Apprentice - Data Retention relates to SD-10068 Huge scale issue. Need to present a high level scale of issue and the problemApprentice - Data Anonymising (relates to SD-10068) & Data Retention This is a very large scale undertaking if we progress down the data anonymisation route. We would like to form a “Task Force” group from our customers with the people who deal with your compliance so this can be discussed in more detail. Anonymisation How we anonymise - we will need to create a standardised process that all agree to and also the method of anonymising e.g. use of **** in certain areas such as names and emails etc For dates e.g. DOB we can use a date such as 01/01/1645 Ethnicity is a specified list, we cant null nullify the entry.
Type of data to anonymise. . We are not responsible for updating the data that third parties hold e.g Aptem in linked systems (via API & Integrations)We cant anonymise data in attachments/filesFiles/recordingsRecordings/Tasks/Notes etc. Anonymised records would need to be flagged in some way as locked down, to prevent editing as they would fail validation Cycling if you attempted to update them The data would need to cycle naturally out of backups, so potentially could take 6 months or so to disappear from those areas Once its gone its gone for good and we cannot restore it
Questions for usersPlease note that we are not responsible for updating the data that third parties hold e.g. Aptem in linked systems (via API & Integrations) Question for users /Task Force How long the ESFA will hold data for certificate reprints, we believe it is 6 years? With regards to general apprentice data retention, are you all agreed its 7 years, and what sort of data are you required to retain? With regard to general qualifications (Accolade) we understand that the learner can request a certificate reprint at any time so this data has to be retained “forever” is this your understanding of it too?
(POLL Available) |
