list of disallowed special characters for filenames is not accurate
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Working on CORE2 which uploads to dataverse, I'm writing code to prevent certain characters in filenames.
Testing Dataverse's restrictions, it reports File Name cannot contain any of the following characters: / : * ? " < > | ; # .
This info is incorrect for at least two reasons:
- This filename still errors even though none of those characters are present:
!$%&’()+,-=@[\]^_{}~. It seems this is because the\character is prevented as well. - the
.character is not actually prevented by Dataverse as far as I can tell, even if its used multiple times.
It would be useful for the user to have a more accurate error message. Also would be useful if this was in the documentation (I may have missed it). This happens on 5.3 and 5.10.1
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
No file or test is named; start by locating Dataverse's filename validation and user-facing error-message entry point, then compare the character list with the reported cases. Done means the reported restrictions are accurately reflected in the error message and, if applicable, the documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100