Feature Request: Get an overview of a collection's access requests and their statuses via API or UI
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Feature Request
There should be a way to get an overview of all access requests of datasets in a collection and their status to keep track of all requests. This is especially relevant for curated collections, as there the access requests are centrally processed and not by the researchers' themselves at a dataset level.
The only way to keep track of access requests is to currently log them internally by hand based on the emails that come in, which leaves a lot of room for errors and requests being missed.
You can currently only get such an overview on the dataset level, but this is not very useful for curated collections, because there the curators/admins manage all requests across a lot of datasets.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator, admin
What inspired the request?
We get a lot of access requests and we log them in an excel with each email coming in. However, we have no easy way to check if our list is actually complete and no checks to see if the status of each request is up-to-date.
What existing behavior do you want changed?
Either the addition of an API call to get all access requests per dataset in a collection and the status of the access request (pending, granted, rejected) similar to how it looks on a dataset level. And/or have it retrievable via the UI.
Any brand new behavior do you want to add to Dataverse?
Get access request information on collection level.
Any open or closed issues related to this feature request?
- #8013
Are you thinking about creating a pull request for this feature?
Possibly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing related issue #8013 and the existing dataset-level access-request API and UI described in the issue. Define whether the collection overview belongs in the API, UI, or both, which datasets and request statuses it must cover, and consider the feature complete when curators can reliably view all collection-level requests and their current statuses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100