Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Request access button on dataset landing page #378

Open
DorienHuijser opened this issue Mar 5, 2024 · 3 comments
Open

[FEATURE] Request access button on dataset landing page #378

DorienHuijser opened this issue Mar 5, 2024 · 3 comments

Comments

@DorienHuijser
Copy link
Member

Is your feature request related to a problem? Please describe.

When a dataset is published under restricted access, there is now no way for external users to find out how to gain access. The only contact information on the landing page is the email address of RDM Support, and we actually don't usually know who is responsible for a dataset, or what the terms for access are.

Describe the solution you'd like

A button "Request access" / "Contact data owner" similar to the implementation in DataverseNL. This would preferably lead to a form (like in DataverseNL), but could also just be a link like mailto::emailaddress@institute.nl. If the latter is implemented, it should be made clear in the metadata form that this email address will be made publicly available.

Describe alternatives you've considered

If issue #376 is implemented, contact information could also be provided in the license.txt and this issue is not so pressing anymore.

Additional context

This question was raised by one of the faculty data stewards at UU in the context of an already published restricted access dataset.

@Danny-dK
Copy link

Danny-dK commented Mar 5, 2024

I could imagine adding a metadata field in the Yoda template that becomes mandatory to fill in once 'restricted access' is chosen. Something like 'contact email for data access'?

@peer35
Copy link

peer35 commented Mar 6, 2024

We do recognize the need for a "Data Request" workflow at the VU, but I feel just adding an email address will not work. Who will maintain this contact information? I imagine the contact will be a researcher, what happens if that person has left the institution? I actually prefer a more general address like RDM support, they can then send the request on.

Alternatively a system where the group managers and the datamanagers receive the request might be helpful.

@Danny-dK
Copy link

Danny-dK commented Mar 6, 2024

Yes, during evaluation of a submission I always mention to the researcher that they need to provide a more sustainable email address. This could for example be the secretariat of the chairgroup or some other science group address. That doesn't mean of course that a chairgroup is completely sustainable as they may merge or end, but it is more sustainable then an personal address. I go back and forth on RDM support being a contact point. Depending on the university that may have many faculties, that might not be the most fun activity for the person(s) of RDM support.

It would be nice if the publication 'request access' button indeed has a link to the category it belonged to and that the Yoda data manager role of that category is than notified. The actual person behind that role may change over time, but it is unlikely that the role in Yoda will change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants