Feature Request/Idea: Reject files with specific extensions
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
As part of securing the Recherche Data Gouv installation, we are asked to filter out specific type of files (determined by their extensions) that shouldn't be allowed to be deposited in the repository.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Sysadmin for setting the list of rejected files and error message
Depositors are the one affected by the file rejection.
What inspired the request?
Securing Recherche Data Gouv installation.
What existing behavior do you want changed?
Renaming files : a user (UI or API) should not be able to change a file extension to one filtered out by renaming the file.
Any brand new behavior do you want to add to Dataverse?
Filtering out files based on extension : allow installation admin to set a list of extensions.
Files with these extensions would be rejected.
Users should receive an appropriate error message to be informed why their file was rejected (e.g. list of exluded extensions and links to the repository relevant terms of use) : screenshots to be added.
Any open or closed issues related to this feature request?
It might be a duplicate but I didn't find other issues.
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 by tracing the UI and API file-upload and file-renaming entry points described in the issue. Define the administrator configuration, extension matching, rejection message, and terms-of-use link behavior; the work is done when filtered extensions cannot be deposited or introduced by renaming and affected users receive the configured explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100