Description of your use case: Data Entries are often long-lived and can contain sensitive data, for example the username in the protocol entries or user-specific authorizations. To comply with data protection guidelines we have to delete user-specific data from the data entries after a certain time period.
Current Behaviour
No anonymization feature is implemented
Wanted Behaviour
A new command that specifies a data entry id and possible some other parameters that then anonymizes the data entry, specifically, the protocol entries and optionally the user specific authorizations (there is a chance that the data entry will become inaccessible if we just delete the authorization without further checks).
Scenario
Current Behaviour
No anonymization feature is implemented
Wanted Behaviour
A new command that specifies a data entry id and possible some other parameters that then anonymizes the data entry, specifically, the protocol entries and optionally the user specific authorizations (there is a chance that the data entry will become inaccessible if we just delete the authorization without further checks).
Possible Workarounds
None, at least no clean ones