timestamp of data access request

[npoppelier]

If you open the overview Restricted File Permissions of a dataset with restricted access, you get an overview of open requests, with the following columns: User/Group Name, ID, Authentication, Email, Files, Access (buttons).

We would like to have an extra column there: Date (or Datetime) of the access request. This would imply a change in the GUI but also a change in the database schema, since the timestamp of the access request is not stored yet (see https://guides.dataverse.org/en/5.4/schemaspy/tables/fileaccessrequests.html).

[pdurbin]

@npoppelier thanks for discussing this a while back at https://groups.google.com/g/dataverse-community/c/FHy7IVW3Z3Q/m/am6omciNCAAJ and ultimately opening this issue.

To make this a little more concrete, here's a screenshot of how the list of requests looks as of Dataverse 5.10:

I don't believe it would be too difficult to add an extra column called "Date". Perhaps if you hover over the date it would reveal an actual timestamp.

We'd need to think about all the old files that don't have a timestamp. Do we always include the "Date" column and just show a blank space when there's no date? Do we hide the "Date" column unless at least one file has a timestamp?

Are you a developer or do you know one who could work on this? If so, let's decide some of these details above before you or they begin. If not, I can try to advocate for this issue to the people who prioritize issues.

Is your installation of Dataverse on our map? If so, perhaps you could create a board to indicate which issues are most important to you. This idea of mine is not fully formed, but you can read about it in the "boards for prioritizing issues (for each installation of Dataverse)" thread: https://groups.google.com/g/dataverse-community/c/z8ugn2KzNSc/m/zt7COeRYBQAJ

[npoppelier]

Hi Philip, Thanks for the reassurance that the addition of an extra column "Date", both in the data model and the user interface, is not a lot of work. A solution with hovering sounds nice and does not take up extra space. When there's no date, the hover space can be filled with '-------' instead of '2022-03-31T09:15:33' for example. I have done some Dataverse-related development work in Python, but I'm not a Java developer. At the UMCU we do not have Java developers unfortunately. The UMCU does not have its own installation of Dataverse: we are members of the network organized by DANS around DataverseNL, and DataverseNL is certainly on your map. Should this idea first be discussed at the DANS level? Regards, Nico

[pdurbin]

@npoppelier let me ping @janvanmansum (DANS) and @qqmyers (GDCC) who recently collaborated on an awesome new "multiple licenses" feature. I gave them a well-deserved shout out in the Dataverse 5.10 announcement: https://groups.google.com/g/dataverse-community/c/cgiUjHcUzi8/m/EY5WbfnYAwAJ

They might be able to tell you more about if DANS/GDCC can help with this. I don't think this feature is especially controversial but I'll go ahead and ping @TaniaSchlatter and @jggautier if they'd like to weigh in on UI/UX impact. (It occurs to me that it might be nice to sort by the proposed "Date" column.) And I'm sure @scolapasta would be interested in the database change.

One thing I forgot to mention earlier is that you can see what the core team is working on by looking at our project board at https://github.com/orgs/IQSS/projects/2 . That is to say, if one of the ~1200 open issues isn't on that board, it hasn't been prioritized. I think your idea is good one, but there are lots of good ideas in this issue tracker. 😄

Finally, we have plenty of code in Python. Please let me know if you're itching to work on something! 😄