IQSS / IQSS/dataverse

Feature Request/Idea: Review UI/UX for attempting to download inaccessible files

Open
#10,537 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Feature UX & UI: Design UX/UI Input Needed
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
Once upon a time the only thing that would keep a user from downloading a file were file restrictions. Since then we have limited access via embargoes, file retention periods and storage limitations. In the UI a user may select several files for download and some of the files may be inaccessible for any of these reasons. Kind of an edge case, but it's possible that the user could attempt to download a group of files and have one or more files be inaccessible for any any or all of these reasons.

We should take a look at improving the user experience when they attempt to download an inaccessible file(s), giving them useful information on why and if possible what they need to do to gain access.

What kind of user is the feature intended for?
File Downloader

What inspired the request?
QA on the file retention feature

What existing behavior do you want changed?
Here's an example of what we show the user now
Screen Shot 2024-05-01 at 11 56 50 AM

Any brand new behavior do you want to add to Dataverse?

Any open or closed issues related to this feature request?

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 reviewing the current multi-file download flow and the behavior shown in the linked screenshot, then compare it with the stated causes of inaccessibility: restrictions, embargoes, retention periods, and storage limits. Done should provide users with useful information about inaccessible files and, where possible, explain how access can be gained.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.