search

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

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

admin access via organizational account #647

Open jiskattema opened 1 year ago

jiskattema commented 1 year ago

Hi all! I'm sure this was brought up a few times before (and maybe solved..) but is there a way to have 'admin' accounts such that the admin can edit all aspects of an organization? So all its software and projects?

At the moment, there is no way to find a 'contact' person that can modify a given piece of software or project. The contact person is not always an NLeSC employee -- or easily findable. I can ofcourse send an email to the contact person.. but that is quite inefficient when adding a project number (for instance) to all eScience projects.

jmaassen commented 1 year ago

At the moment organization maintainers have the possibility to pin/deny software and projects for their organizations, but don't necessarily have the rights to change software / projects.

The reason for not having this (for software at least) is that it assumes there is a single organization which is an 'owner' of the software and has the right to change it, which is generally not the case. For example, all software coming out of NLeSC projects is created in collaboration with at least one other organization. Having organization maintainers being able to change software entries would imply that those organization can also significantly change "our" software pages (for those piece of software with their name on it).

For projects the situation may be slightly different though, although you these also often involve multiple organizations which may all have access to the RSD.

However, as RSD maintainers, we may be able to quickly help you in some cases, as we can assign extra maintainers to software and project when needed. Would this solve your issue?

jiskattema commented 1 year ago

But now we have the opposite case, where software and project owners (in the literal sense: funded, created, and copyright owned by) like NLeSC cannot modify the software without finding (possibily ex-) employees. Specifically for general data entry and maintenance (i'm thinking of setting the projects grant ID, or some generic software's setting) that is a maintenance nightmare, leading to outdated and incorrect pages.

Would an email notification to the 'owner' when changes are made by an organization admin be an option? For all cases where ownership (and edit rights) is not 100% obvious, there have to be humans in the loop anyways. Assuming organization admins act responsibly, this would remove at least a few back-and-forth email conversations.