| | | 1 | | using System.Text.Json.Serialization; |
| | | 2 | | using ArturRios.Heimdall.Shared.Security; |
| | | 3 | | using ArturRios.Mediator.Query; |
| | | 4 | | |
| | | 5 | | namespace ArturRios.Heimdall.Query.Input; |
| | | 6 | | |
| | | 7 | | /// <summary> |
| | | 8 | | /// Request to list the erasure requests that have not yet been carried out (UC-43), so an |
| | | 9 | | /// administrator can see what is outstanding and what is overdue. |
| | | 10 | | /// </summary> |
| | | 11 | | /// <remarks> |
| | | 12 | | /// The listing exists for one reason: GDPR Art. 12(3) and LGPD Art. 19 §2 set a deadline, and a |
| | | 13 | | /// deadline nobody can see is one nobody meets. Most requests need no human at all — the |
| | | 14 | | /// anonymisation pass carries them out — but the ones NFR-12 blocks need an owner transferred, |
| | | 15 | | /// and without this they would sit unnoticed until the deadline had already passed. |
| | | 16 | | /// </remarks> |
| | | 17 | | public class ListErasureRequestsQuery : BaseQuery, IActorScoped |
| | | 18 | | { |
| | | 19 | | /// <summary> |
| | | 20 | | /// When true, only the requests whose deadline has already passed. The default is every |
| | | 21 | | /// outstanding request, because a queue that shows only what is already late is a queue that |
| | | 22 | | /// guarantees lateness. |
| | | 23 | | /// </summary> |
| | 17 | 24 | | public bool OverdueOnly { get; set; } |
| | | 25 | | |
| | | 26 | | [JsonIgnore] |
| | 1 | 27 | | public Guid ActingPersonId { get; set; } |
| | | 28 | | |
| | | 29 | | [JsonIgnore] |
| | 1 | 30 | | public int ActingRole { get; set; } |
| | | 31 | | } |