IQSS / IQSS/dataverse-frontend

Feature Request: Design and implement SPA view to see list of file/dataset history of access requests

Open
#895 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Size: 30 SPA
Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Overview of the Feature Request Create a view for users to see the full list of file/dataset access requests (not just created requests waiting for acceptance or rejection). A new set of parameters are being added to the /datafile/{id}/listRequests API to return all of the requests for file access as well as pagination to limit longer lists

  • includeHistory When true this will force the return of all requests and not just the "created" ones.
  • start For pagination, use this to request a specific page.
  • per_page For pagination, use this to limit the number of items in each paged list.

**What kind of user is the feature intended for?**API User, Curator, Superuser

What inspired the request? The need for a Datset owner to view the requests to access a file

What existing behavior do you want changed?

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

Any open or closed issues related to this feature request? https://github.com/IQSS/dataverse/issues/8013

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 locating the existing SPA view and API integration for file access requests, then inspect how /datafile/{id}/listRequests is called. Add a history view that uses includeHistory, start, and per_page; done means API users, curators, and superusers can browse paginated full request history rather than only created requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.