search

research-software-directory / RSD-as-a-service

This repo contains the new RSD-as-a-service implementation
https://research.software
27 stars 14 forks source link

End user support #680

Open jiskattema opened 1 year ago

jiskattema commented 1 year ago

How is end-user support currently arranged? Very practical: an RSE needs to edit an existing page. Who should arrange access for him/her? I don't see many tickets about that in this issue tracker, so i assume it is not here.

I've asked in a different ticket #647 about an organizational admin account, but that has not been resolved yet.

Can we make a 'contact' button that would send a request to the admin of you organization, just like the current 'feedback' button? Or a 'request access' or something like that? The email would then go to:

  1. the maintainers
  2. or the organizational admin
jmaassen commented 1 year ago

When end users add software and/or projects, they automatically become maintainer of these pages. They can invite others to also become maintainers by generating an invitation link in the maintainers tab.

So in principle, the maintainer of a page is responsible for arranging access for others.

Specifically for the eScience Center, we have the problem that a lot of content has been migrated from the old RSD (without access control) to the new one. For all our software, we've invited the contact persons to become maintainer, or a backup engineer if the contact person no longer works for us. For our projects, all PM are maintainers.

This way, either the contact person of the software, or the PM of a project should always be able to provide access to an RSE that requests it. It's also up to that person to decide if it makes sense that this RSE has access in the first place.

If needed, we would be happy to support you in this process. However, it's sometimes hard for us to decide it it makes sense to give someone access or not.

jiskattema commented 1 year ago

But users move around, change project and/or job; when projects are funded pages created by support staff and/or PMs before RSEs are assigned etc, hence ticket #647 Also, the way you describe 'backup' RSEs for when the original author of the software is no longer involved, will lead to issues when also the backup RSE moves on.

The current feedback button sends an email to rsd@esciencecenter.nl , but could you make a button to mail one of the maintainers of the software/project?

ctwhome commented 1 year ago

Great idea. We could improve the feedback panel with an option to mail the contributors if the context is in a software or project page.

We don't have currently a mail server, but it is something we should consider to actually improve the user experience.