IQSS / IQSS/dataverse

Data access request seems to go to file contributor instead of dataset contact

Open
#9,976 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Request Access Workflow 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?

Requesting access to restricted files where the file uploader does not correspond with dataset contact.

  • When does this issue occur?

Requesting access to restricted files where the file uploader does not correspond with dataset contact.

  • Which page(s) does it occurs on?

Dataset-page, under Files.

  • What happens?

When requesting acces to restricted files, the access request seems to automatically end up with the file uploader instead of the appointed dataset contact.

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

All users.

  • What did you expect to happen?

We expect that all access requests go to the dataset manager(s) (i.e. dataset contact), and not individual file uploaders.

Which version of Dataverse are you using?

5.12

Any related open or closed issues to this bug report?

No.

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

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 by reproducing the request for a restricted file from the dataset page's Files section using Dataverse 5.12. Trace how the access request chooses between the file uploader and the dataset contact, then verify that requests are delivered to the dataset manager(s) rather than an individual uploader.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authorization, 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.