Versions Compared

Version Old Version 13 New Version 14
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


TypeFunctional descriptionWhere usedWarning/error messagesComments
1Delete (status)

Users can apply a status of "delete" to a particular record, which would mean that the record would be deleted from the front end

  • applied at both record and field level
  • this acts as a soft delete
    • removed the field from the front end
    • does not de-link where applied
    • removes link ability for new scenarios

Example: People (Sensitive Data / Manage Record / Status)

  • People
  • Programmes
  • Posts
No error message displayedTBC: In intrepid, this flagged the applicable field or record for archiving in the back end but kept it in view on the UI?
2Inactive (status)

Users can apply a status of "Inactive" to a particular record or reference data field, which would mean that the record or field is made temporarily unavailable

  • can be applied at both record and field level
  • impact of applying this to a field being used in a current record, is
    • filtering may need to be applied to view the record in a list page i.e. To show both current and inactive records
    • 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 may present errors to the user
    • assessment records may become legacy, and no changes editing will no longer be possible once this kicks in

Example: People records (People / Sensitive Data / Manage Record / Status)

  • People
  • Programmes
  • Posts
No error message displayedTBC In Intrepid, this meant the applicable field/record would need to be activated before it could be used in TIS
3Trash can

Users can click on the trash can next to a field and permanently remove data from TIS

  • this functions as a hard delete
  • removes existing linkages with records and other fields
  • No audit trail is kept of record/field

Example: Placement record (People / Placements / Placement list)

  • People: Placement
  • People: Programme Membership
"Are you sure you want to delete?" displayed
4Minus

Users can click on the minus sign next to a field and permanently remove it from TIS

  • this functions as a hard delete
  • removes existing linkages with records and other fields
  • No audit trail is kept of record/field

Example: Curricula (Programme / Curricula)

  • People: Qualifications
  • People: Programme Membership
  • Posts: Other specialties
  • Posts: Sub-specialties
  • Posts: Other grades
  • Posts: Other sites
  • Posts: Programme names
  • Programme: Curricula
No error message displayed
5X button

Users can click on the X sign next to a field and permanently remove it from TIS

  • this functions as a hard delete
  • removes existing linkages with records and other fields

Example: Roles field (People / Sensitive Data / Manage Records / Roles)

  • People: Roles
No error message displayed
6Dates from/to

Users can specify an end date, which would make the related record or fields Inactive after that date has elapsed

  • this functions as a hard delete
  • removes existing linkages with records and other fields

Example: Post funding (Posts / Post record / Funding)

  • People: Registration dates
  • People: Inactive date
  • People: Programme membership
No error message displayed
7ArchiveNot currently implemented in TIS
N/A


Data

...

implications
 In terms of data being passed down to NDW, it is assumed that hard delete data is not passed on, but soft delete data is.


To Be << to be discussed and agreed with data leads

In order to consolidate the way that the concept of deletion is used across TIS, the following rules should be applied:

...

  • 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 (see below)
  • displayed display the deleted status in the audit log

Applicable scenarios

N/A - see Trash Can, 



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 that have a status of “current”
  • display which records are linked or using the data, line by line

Applicable scenarios

  • records and fields that need to be temporarily retired

...

  • this interaction type should be applied to all record types and certain fields
  • this should act as a soft delete, and render the record/field as follows
    • remove it the record or field completely from view in the FE
    • apply status “delete” “deleted” in the BE for audit purposes
  • display the deletion in audit log against the relevant user/record
  • do not share deleted records with NDW

...

  • this interaction should enable the removal of sub-sections to a record
  • this should act as a soft delete
    • remove the data from the UI
    • apply status of Delete in BE
  • keep a record of the change in the back end (accessible via audit logs)
  • do not share deleted records with NDW

...

  • accidental addition of a placement or assessment to a Person record
  • accidental addition of a curriculum to a Programme



X (button)

  • this interaction allows the removal of fields against a record
  • it should act as a soft delete
    • remove the data from the UI
    • apply status of Delete in BE
  • keep a record of the change in the back end (accessible via audit logs)
  • do not share deleted records with NDW

...

Dates From/To

  • this interaction should enable trigger automatic status change to inactive or current
  • it should act as a status change only
    • make applicable record "inactive" when elapsed time passes
    • keep the record in view within UI
    • apply status of Delete in BE
  • keep a record of the change in the back end (accessible via audit logs)
  • do not share deleted records with NDW

...