request access: when a user requests access to a file and is rejected, that action should be saved

[sbarbosadataverse]

At this time, rejected users are not saved in any way on the file level permissions page:

1. This removes and doesn't allow the dataset owner to track their actual numbers of data requests on their restricted file/dataset
2. This doesn't provide the user with a list of previous requests they can track and keep a record of rejected users
3. This has been requested in support tickets into Harvard Dataverse repeatedly.

[sbarbosadataverse]

@TaniaSchlatter I created this ticket for the request access-rejected user scenario

[cmbz]

2024/11/18: Upon review, we are keeping this feature request.

[qqmyers]

FWIW: The database is tracking granted and rejected requests these days, but there's no UI/API way to retrieve them yet. It would be relatively easy to add a parameter to the https://guides.dataverse.org/en/latest/api/dataaccess.html#list-file-access-requests call, e.g. ?includeHistory=true (mirroring the flag name from #11268 for curationStatus) to at least make the info accessible. It should also be possible to add the info to the current UI or SPA, but some guidance would be needed as to where to display it (showing the history for all files in the dataset page (permissions tab) could be a long list, could show it only on the file page? or?).

[pdurbin]

Right, as discussed in Slack as of the following PR there are three possible RequestState values that can be saved in the database: CREATED, GRANTED, REJECTED.

• ADA/Guestbook-at-request #9599

Yes, it would be great to expose this via API.

[cmbz]

2025/03/03

• Would require a backend db change
• Would require UI development

[qqmyers]

I don't think this requires a db change. It would require API/UI level work.

[cmbz]

2025/03/03

• Moved to dv backlog column @scolapasta

[scolapasta]

Ah, I hadn't realized we were now storing rejected. So yes, if that's the case, no DB change; still needs UI design (especially to handle when large number of rejects exist).

[cmbz]

2025-04-09
Next steps for whomever picks up issue

• Confirm APIs don't exist
• Implement support in the API
• Open an SPA issue for the UI part (design and implementation)
  Sizing at 30 initially