Philip Durbin 🚀 (Aug 06 2025 at 13:56): Philip Durbin 🚀 (Aug 06 2025 at 13:56):@Dieuwertje Bloemen hi, I just noticed your email about access requests in a collection.
@Guillermo Portas and I have been thinking hacking on the Notifications API as part of #11673, mostly because the SPA needs a better API to display in-app notifications.
It sounds like you're interested in filtering notifications down to a particular collection. Is that right?
Dieuwertje Bloemen (Aug 06 2025 at 14:36):I think that might be useful. It doesn't entirely cover the need, because you can't see what the status is at the moment of query. Though I'm gonna look how far I can get with the get notifications API call, wasn't aware that existed actually. It'll at least get me an overview of all requests ever sent. Thanks!
Philip Durbin 🚀 (Aug 06 2025 at 14:36):Yes, please do take a look! There's also a dedicated topic on it: #dev > Notifications API usage and future
Dieuwertje Bloemen (Aug 06 2025 at 14:38):I have at some point used a copy and paste of my notifications to calculate number of datasets that went through more than one review phase. So, there is some potential to grab some statistics more reliably from this API potentially. But of course, I don't actually think that that's the best data to do this kind of stuff with :working_on_it:
Philip Durbin 🚀 (Aug 06 2025 at 14:43):Right, there's also this API, but you pass a file rather than a collection: https://guides.dataverse.org/en/6.7.1/api/dataaccess.html#list-file-access-requests
Dieuwertje Bloemen (Aug 06 2025 at 14:46):Yeah, even if that one existed for a dataset, that would be great. But my ideal use case would be pretty much that call, but it gives the status for all access requests to any dataset/file of a collection. Maybe even with a parameter to say if you want the information on a dataset level or a file level (but just file level, would already be great).
Philip Durbin 🚀 (Aug 06 2025 at 14:50):I'm sure the SPA will need something like that. https://github.com/IQSS/dataverse-frontend/issues/163 is related.
Philip Durbin 🚀 (Aug 06 2025 at 14:53):It's not in the SPA 2025 Q3 proposal, though. Via https://github.com/IQSS/dataverse-pm/issues/421
Philip Durbin 🚀 (Aug 06 2025 at 14:54):Wouldn't hurt to create an issue though, a feature request, so that we consider it when building the APIs the SPA will need to manage access requests.
Dieuwertje Bloemen (Aug 06 2025 at 14:57):I first wanted to see if anyone else has a similar/adjacent need. Or maybe has some workaround for this kinda thing. If not, I'll definitely create an feature request for it.
Philip Durbin 🚀 (Aug 06 2025 at 15:26):Cool. Also, I brought this up at standup just now, to raise awareness.
Laura Huis in 't Veld (Aug 14 2025 at 13:43):Hi @Dieuwertje Bloemen , I recently received a similar request from one of our users. He wanted to have an overview of all users who have requested access to restricted files in the past for a particular collection and all sub-collections.
The Privacy Officer of this organisation recommended to maintain a local record of all individuals who have requested access to restricted files, particularly in the context of anonymised datasets.
I guess in this case you would also like to have info about if access was granted or not.
Philip Durbin 🚀 (Aug 14 2025 at 13:47):We store "REJECTED" in the database but we don't expose it via the UI or API. Please see this issue: #8013
Dieuwertje Bloemen (Aug 14 2025 at 14:30):Hi @Laura Huis in 't Veld , we do keep a spreadsheet of all the access requests we've processed and their relevant DTA's (also at the advice of our privacy officer for GDPR compliance and stuff ;) ). But my main concern is that maybe we're sometimes missing access requests due to a manual oversight. Or someone forgot to log a specific granting or rejecting. It would be nice to easily get an overview of all access requests of the collection (and their status is a bonus) to then match against our internal list of the ones we've processed. It's mainly because I don't want to miss any requests (and keep requesters hanging) and I feel like the manual tracking just leaves room for too many errors. At least my gut currently says we've missed some, but I don't have an easy way to check if we actually did. My colleagues noted they could pull it from the database, but I think many installations would like a more easy way of quickly pulling such a link (e.g. to populate an excel with via an api call).
Philip Durbin 🚀 (Aug 14 2025 at 14:39):Yeah, I feel like #8013 should be retitled. Instead of request access: when a user requests access to a file and is rejected, that action should be saved it should explain that we want the data via API, at least.
Dieuwertje Bloemen (Aug 14 2025 at 14:40):I've just created a feature request #11746. I'll also discuss it internally to see if maybe we can work on such an API call to get access requests on collection level.
Philip Durbin 🚀 (Aug 14 2025 at 14:45):@Dieuwertje Bloemen looks great. I edited it to link to the older, related issue. And I gave that old issue a better title, by the way. Longer but I hope better. :smile:
Last updated: Oct 30 2025 at 06:21 UTC