Currently, with local_archiving | job_preset_archive_autodelete and local_archiving | job_preset_archive_retention_time, you can configure a retention time which helps you to get rid of archives as soon as you do not need them anymore. The default of 1095 days = 3 years is generally fine.
However, we have been told that there are higher education institutions who are legally oblidged to delete their exam archives on january 1st of the year following a n year retention period.
Which means if n is 2, but your job_preset_archive_retention_time setting is 3 years, an exam which is written the day before christmas will be deleted nearly 1 year too late. There is the (theoretical) risk that someone might complain about that.
Against this background, I would like to propose (with really low priority, more for the sake of completeness) to refine the retention time setting to support such reference data cases as well.
Currently, with
local_archiving | job_preset_archive_autodeleteandlocal_archiving | job_preset_archive_retention_time, you can configure a retention time which helps you to get rid of archives as soon as you do not need them anymore. The default of 1095 days = 3 years is generally fine.However, we have been told that there are higher education institutions who are legally oblidged to delete their exam archives on january 1st of the year following a n year retention period.
Which means if n is 2, but your job_preset_archive_retention_time setting is 3 years, an exam which is written the day before christmas will be deleted nearly 1 year too late. There is the (theoretical) risk that someone might complain about that.
Against this background, I would like to propose (with really low priority, more for the sake of completeness) to refine the retention time setting to support such reference data cases as well.