View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
17943 | Feature requests | _ Unknown | public | 2022-03-09 09:33 | 2022-03-11 14:54 |
Reporter | gwdgls | Assigned To | |||
Priority | none | Severity | feature | ||
Status | new | Resolution | open | ||
Summary | 17943: Request to enhance the check data integrity function | ||||
Description | The function to delete tables of removed surveys from the database is crucial for data protection, at least in GDPR countries, regarding tables with personal data, e.g. participants' tables. Feature requests.
| ||||
Additional Information | When a survey is deleted via the user interface, the questionnaire and resources (uploads) are deleted. Data tables, however, remain in the database until the data integrity check is done. If hosting an installation with many survey administrators, the server admin won't know when a survey is deleted, so they would usually perform the function on a regular basis. However, they won't know whether the deleted survey's admin might want to reactivate it at a later date and wants to keep these tables for re-importing. | ||||
Tags | data integrity, data protection | ||||
Bug heat | 4 | ||||
Story point estimate | |||||
Users affected % | |||||
By Survey needed ;) |
|
It's not done when delete survey ? |
|
This is an spearated bug in my opinion.
|
|
OK, I'm writing a feature request for each of these. Question: Is there a reason why 2. (filter by survey) is a separate request from 1.? |
|
Another Question: 4. would make 3. redundant, right? |
|
17947: 1. and possibly 2.17948: 3.Is 4. really a bug?
|
|
https://bugs.limesurvey.org/view.php?id=17947 |
|
Remind : it's just my personal opinion :). About «sometimes a user wants to keep tables in order to re-use them in another survey.» but then : we don't keep current token table and survey table … We delete current survey table but not old survey table : my opinoon : it's an issue :) |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2022-03-09 09:33 | gwdgls | New Issue | |
2022-03-10 18:26 | DenisChenu | Relationship added | related to 17094 |
2022-03-10 18:27 | DenisChenu | Note Added: 68616 | |
2022-03-10 18:27 | DenisChenu | Bug heat | 0 => 2 |
2022-03-10 18:28 | DenisChenu | Note Added: 68617 | |
2022-03-10 18:30 | DenisChenu | Note Added: 68618 | |
2022-03-11 12:56 | gwdgls | Note Added: 68629 | |
2022-03-11 12:56 | gwdgls | Bug heat | 2 => 4 |
2022-03-11 13:03 | gwdgls | Tag Attached: data integrity | |
2022-03-11 13:03 | gwdgls | Tag Attached: data protection | |
2022-03-11 13:09 | gwdgls | Note Added: 68631 | |
2022-03-11 13:14 | gwdgls | Note Added: 68632 | |
2022-03-11 13:15 | gwdgls | Note Added: 68633 | |
2022-03-11 14:54 | DenisChenu | Note Added: 68637 | |
2022-03-11 14:54 | DenisChenu | Relationship added | related to 17947 |
2022-03-11 14:54 | DenisChenu | Relationship added | related to 17948 |