IQSS / IQSS/dataverse-frontend

Group: add the user-identifier along with the user name to distinguish between users with multiple accounts, or users with the same name

Open
#676 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Overview of the Feature Request

Be able to distinguish between users with multiple accounts, or users with the same name, who have been added to a group.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

Approvers who use groups to manage access to datasets/files

What inspired the request?
Using the Edit group functionality.

What existing behavior do you want changed?

The existing Edit -> Groups -> Edit popup shows only the name of users who are current group members, with no useridentifier or other info to distinguish between users that have multiple accounts or users with the same name.

For users that fall into one of these 2 categories, it's impossible to know which account has been added to the group, to know if they have already been added, or which to delete (depending on the task).

Note that when you assign users to a group, the popup to select the user shows the user's useridentifier:

Image

When you go to edit the group (to add or remove users), the useridentifier is not shown (but could be?):

Image

While ORCID is an identifier, it's not always public and a lot of people don't have one...

Any open or closed issues related to this feature request?
Not sure

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 Edit → Groups → Edit popup described in the issue and compare it with the user-selection popup, which already displays the useridentifier. Trace the frontend components responsible for both member lists and make the current-member view distinguish users with the same name or multiple accounts; verify that adding and removing the intended account remains clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.