Currently
There are 3 different ways of making a field or record unavailable within the TIS UI, the uses have not been applied consistently across the front end/back end, however the general summary is as follows:
Delete (status)
- applied at both record and field level
- this acts as a soft delete
- does not de-link where applied
- removes link ability for new scenarios
Inactive (status)
- can be applied at both record and field level
- impact of applying this to field being used in a current record, is
- filtering may need to be applied to view the record in a list page
- drop downs for reference tables will not display anything that has been made with an inactive status
- records containing inactive data will not be flagged, but editing my present errors
- assessment records may become legacy, and no changes will be possible once this kicks in
Trash Can (button)
- this functions as a hard delete
- removes existing linkages with records and other fields
<data flows>
To Be
In order to consolidate the way that the concept of deletion is used across TIS, the following rules should be applied:
Delete Status
- remove “delete” as a status that can be applied from FE across all fields and records
- apply delete status in the BE only, in certain scenarios
- displayed the deleted status in the audit log
Inactive status
- this should only be applied to the following to reference data fields and all record types
- remove ability to link to new records
- flag where there are records using/linked to this data, which have a status of “current”
- display which records are linked or using the data, line by line
Trash Can (button)
- this interaction type should be applied to all record types
- this should act as a soft delete, and render the record/field as follows
- remove it completely from view in the FE
- apply status “deleted” in the BE for audit purposes
- display the deletion in audit log against the relevant user/record
| # | Question | Comments |
|---|
| 1 | Other than reference date and records (forms), is there anywhere else, or data type, that it should be possible to apply inactive as a status? |
|
| 2 | Other than within record, are there other scenarios you might want to delete (trashcan) a data entity? for example, particular fields? |
|
| 3 | Deleting programme membership or curriculum membership current behaviour. Think these are hard deletes too, should they be? If so, do we currently audit the deletion of these? |
|