IQSS / IQSS/dataverse

directoryLabel leading '.' char for hidden directories is ignored (removed)

Open
#8,807 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: File Upload & Handling Type: Suggestion User Role: Depositor
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?
Crate a new file in a dataset with directoryLabel starting with '.' char. And save the file.

  • When does this issue occur?
    Issue occurs when adding files in hidden directories on top level. Hidden directories inside other directories work.

  • Which page(s) does it occurs on?
    Upload dataverse files (API and webinterface)

  • What happens?
    The leading '.' char is ignored / removed. For example adding .hidden/file will be saved as hidden/file.

  • To whom does it occur (all users, curators, superusers)?
    all users

  • What did you expect to happen?
    Adding .hidden/file should be saved in a hidden directory named .hidden

Which version of Dataverse are you using?
v. 5.9 build 750-fb24c87

Any related open or closed issues to this bug report?
datalad/datalad-dataverse#83

Screenshots:

  • Adding file in hidden dir
    Bildschirmfoto 2022-06-18 um 11 17 04
  • hidden dir is now no longer hidden
    Bildschirmfoto 2022-06-18 um 11 17 13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the upload through both the API and web interface, focusing on top-level directoryLabel handling for .hidden/file; nested hidden directories are reported to work. Trace where the leading dot is removed and verify that uploads preserve .hidden/file in both entry points, with regression coverage for the reported behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.