IQSS / IQSS/dataverse

Feature request/Idea : show dataverse collections and groups associated to user roles in admin dashboard?

Open
#7,728 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: JSF Feature: Superuser Dashboard Type: Suggestion User Role: Superuser
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Hi,
I hope this is not duplicating an existing ticket.
Currently the Users dashboard displays the following fields :
ID | Username | Name | Email | Affiliation | Authentication | Roles | Superuser (Y/N)

A user's roles and groups can be different from one Dataverse collection to another. In the following example "Dataset Creator" and "Member" do not apply to the same collections :
image

it would be nice to display :
1/ the name of the collection near the roles.
2/ The group(s) to which the user belongs.

In order to not uselessly complexify the dashboard, it could be done for ex. like this : Dataset creator (dataverse_collection_1, group), Member (dataverse_collection2, group)... ?
OR (maybe preferable)
make these informations available through the "List Users" function in the API, which also does not display this information?

Main use case :

  • facilitate user management for the superadmin.
  • facilitate reports on the current usage of the Dataverse instance.

I hope it is clear, not redundant and relevant enough.
Thanks in advance for your time.
Thomas

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Users dashboard and the List Users API function named in the issue. Determine whether the associations should be exposed in the dashboard, the API, or both, and define how roles map to collections and groups. Done means the chosen interface clearly exposes each user's role, associated collection, and group.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.