IQSS / IQSS/dataverse

Feature Idea: Automatically delete guestbook data after certain period

Open
#10,002 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: GDPR Feature: Guestbook Type: Feature User Role: Superuser
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
In order to comply with GDPR we delete guestbook responses after one year. This is currently done outside of Dataverse but might be interesting to make Dataverse more GDPR compliant out of the box.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Guests that fill in guestbooks.
Installation admins for the definition of the duration.

What inspired the request?
GDPR declaration for the entrepot.recherche.data.gouv.fr Dataverse installation

Any brand new behavior do you want to add to Dataverse?
As an admin,
I can set a duration, after which the responses to a guestbook are deleted and the entry assigned to the guesbook "1" to keep only the number of downloads/exploration

Any open or closed issues related to this feature request?

  • #9396
  • #9375 (for other informations with retention period)
  • #9630 other issue on GDPR and guestbooks

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading related issues #9396, #9375, and #9630 to understand existing GDPR and guestbook retention work. The requested outcome is an admin-configurable duration after which guestbook responses are deleted while the guestbook entry retains download and exploration counts.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.