Bug report: Guestbook doesn't log all access requests
Nobody has claimed this yet.
- 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?
Create a collection with no specific Guestbook. Create a dataset within the collection with a restricted file and submit an access request. You will see this access request when you download the guestbook csv.
However, if you create a collection with a specific guestbook, the behavior of logging access requests is different.
To replicate: Create a new collection with a specific guestbook. Within this collection, create two datasets with restricted files. Connect the specific guestbook to one of the datasets. Submit an access request for both datasets. You will see that only the access request for the dataset with the Guestbook applied is logged in the csv file.
-
When does this issue occur?
When submitting access requests for a dataset without a specific Guestbook connected, within a collection where a custom guestbook is available. -
Which page(s) does it occurs on?
Guestbook page -
To whom does it occur (all users, curators, superusers)?
This information is available usually for superusers, admins and curators.
Which version of Dataverse are you using?
Version 6.3
Any related open or closed issues to this bug report?
Not that I know of.
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 on the Guestbook page by reproducing the two scenarios described: a collection-level guestbook and a dataset-specific guestbook, each with restricted files and access requests. Trace how access requests are collected for the guestbook CSV. Done means requests for both datasets appear in the CSV, including those from the dataset without a specific guestbook.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100