Feature Request/Idea: API / dashboard page to export and/or truncate actionlogrecord table
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
Currently, the Admin Guide recommends that the actionlogrecord be regularly purged: https://guides.dataverse.org/en/latest/admin/troubleshooting.html#what-s-with-this-table-actionlogrecord-in-our-database-it-seems-to-be-growing-uncontrollably
It would be great to allow superusers to view the table and optimally to truncate it by date via the admin dashboard, or helpful to allow a superuser to export the table and truncate it via API.
What kind of user is the feature intended for?
API user, Archivist, Admin
What inspired the request?
What existing behavior do you want changed?
Any brand new behavior do you want to add to Dataverse?
These two(?) API endpoints and potentially a page in the admin dashboard.
Any related open or closed issues to this feature request?
#9356 mentioned the condition, and prompted this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked admin troubleshooting guidance and issue #9356, then locate the existing actionlogrecord handling and admin/API entry points. Clarify whether the scope is export, date-based truncation, dashboard access, or all three. Done requires an agreed design for superuser access, export behavior, and retention or truncation rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100