Support operations automation

[slint]

As an InvenioRDM instance becomes significantly large, so too does the support load required to meet user demand. There are many requests that users create that they could handle themselves. We choose to focus on record deletion as it is one of the most common requests and establishes a strong base for adding other types of requests in the future, such as file replacement, ownership transfer, spam reporting, etc.

Tip

🎬 See also the recorded presentation for this feature in the August 12th InvenioRDM telecon

Note

See also the Record Deletion Request RFC, which examines the implementation of record deletion requests and how instance administrators can handle them

Eligible operations

Record deletion

Currently, records in InvenioRDM can only be deleted by instance administrators. We propose allowing users to:

1. Be able to immediately delete a record that meets the criteria configured by the instance manager (e.g. within a 30-days grace period after publishing)
2. Request deletion of a record by providing a justification

Storage quota increases

Storage quota increases for drafts are only possible via administrators either on a record-by-record basis or for a specific user. Alongside these mechanisms, we propose to also provide users with the option to open a request for draft storage quota increases directly via the upload form.

File replacement

After publishing a record, it is not possible to update the record's files without an administrator editing the record (to unlock the file storage bucket). Similar to record deletion, we propose that users can:

1. Modify files after publishing under some configured criteria by the instance manager
2. Open a request where they can easily specify what files they wish to modify

Ownership transfer

TBD

Spam reports

TBD