IQSS / IQSS/dataverse

Feature Request/Idea: Remove inactive user accounts

Open
#9,631 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Account & User Info Feature: GDPR 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
As an instance administrator
I can set a duration after which, inactive user accounts will be removed
In order to avoid preserving old accounts and personal information

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
used by Sysadmin : configuration of the Dataverse instance,
affecting all types user accounts

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

Any brand new behavior do you want to add to Dataverse?
Allow instance administrators to set a duration e.g. InactiveUsersPreservationDuration (if the duration is not set, then inactive user accounts are always preserved, as currently),
user accounts that didn't log in for this duration are sent a notification informing them that if they don't log in within one month (maybe this would also have to be configurable), the user account will be deleted.

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

The issue names no files, tests, or entry points. Start by locating how Dataverse stores instance configuration and user login activity, then trace the existing account notification and deletion flows. Done should include configurable inactivity and warning periods, notifications, and deletion behavior while preserving accounts when no duration is configured.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authentication, backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.