Feature Request: Enforce Read-Only Mode When Storage Quota Is Reached

[sbarbosadataverse]

Summary:
Automatically move user accounts to read-only mode when they reach their free storage quota in the production environment.

Description:
To ensure fair and sustainable use of storage resources, accounts that exceed their allotted free storage limit should no longer be able to upload or modify data. However, they should still be able to view, download, and manage existing content (with read-only access). This enforcement is critical for maintaining system performance and ensuring equitable access for all users.

Proposed Solution:
Implement logic in the production environment that:

Monitors user storage usage in real time or at regular intervals (see issue #364 )

Detects when a user has reached or exceeded their free quota

Switches the user's account to read-only mode automatically

Notifies the user of the change and provides information on how to free up space or upgrade storage

Benefits:

Prevents overuse of limited storage resources

Encourages responsible data management

Aligns system behavior with storage policy

Reduces the administrative burden of manual enforcement

Optional Enhancements:

Include a warning system before the quota is reached (e.g., at 90%)

Allow admins to override or customize the threshold.

Provide a user-facing dashboard showing current quota usage and remaining space.

[landreev]

@cmbz @scolapasta It is not yet possible to accommodate the request above. At the moment, storage quotas can only be set on specific collections. But not on individual datasets in the root collection, or per user. It was however understood that we would want to add these features eventually, and it sounds like we have a need/use case at IQSS.
I would open a new dev. issue in the main dev. queue, and leave this one here for actually setting the actual quotas in prod. once we have the mechanism for it.
In terms of priority, I personally feel that IQSS/dataverse#11275 is more urgent (if I were to work on both of these, I would start with that one). But both would be great to implement rather sooner than later.

[cmbz]

2025-05-27

• @landreev and @sbarbosadataverse I am placing this issue on hold (with @sbarbosadataverse as the owner) as per Leonid's comment here: Storage: Feature Request: Display Storage Usage per Data Deposit, per account, per collection #364 (comment)
• Please note that there are two new related issues that are meant to implement the desired functionality. Once those are implemented, Feature Request: Enforce Read-Only Mode When Storage Quota Is Reached #365 and Storage: Feature Request: Display Storage Usage per Data Deposit, per account, per collection #364 will be able to be applied to HDV.