IQSS / IQSS/dataverse

Grant Access to Users/Groups of replaced files

Open
#9,697 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Request Access Workflow Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

If restricted files of a dataset are replaced, only the files of the draft version can be unlocked with “Grant Access to Users/Groups”.
This can alternatively also be seen as a feature request.

  • What steps does it take to reproduce the issue?
  1. Replace a restricted file of a dataset
  2. Don’t publish the draft of the dataset
  3. A user request access to a file of the last published version
  4. Permissions -> File:
    grafik
    a. Button “1 Files” shows the latest published file as “deleted”, the file can be unlocked. This work correct, maybe the description as “deleted” isn’t appropriate. The file 10053_da_de_v2_0.tab is still the published version and not deleted.
    grafik
    b. “Grant Access to Users/Groups” shows only the files from the draft version. The files from the latest dataset version are not available. 10053_da_de_v3_0.tab is the new file of the draft version. If a user request access to a file, we normally grant access to all files, this is not possible because only the new files are visible.
    grafik
  • What did you expect to happen?
    A tick box to “Include Deleted Files”. With a lot of files including all deleted files can be very confusing. Maybe better a functionality to show only the files of the latest published dataset version, or a selection of which dataset version should be shown
    grafik

  • To whom does it occur (all users, curators, superusers)?
    Curators or users which unlock restricted files

Which version of Dataverse are you using?
v5.12.1

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

Start at the Permissions -> File view and the “Grant Access to Users/Groups” action described in the reproduction steps. Trace how files are selected after a restricted file is replaced, then verify the completed behavior by reproducing the draft-versus-latest-published-version scenario and confirming that the intended file versions can be selected without changing existing access grants.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization, frontend
Issue type
Feature
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.