IQSS / IQSS/dataverse

Add ORCID to uploader/contributor of dataset

Open
#10,087 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
In order to identify unique uploaders, we currently have to use strings. This means that Joe Smith, Joe S. Smith, Joe Samuel Smith, and J. S. Smith are all seen as different persons. We would like to add an ORCID so that we can quickly identify unique uploaders even if they use different spellings of their name.

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

What inspired the request?
We would like to have an accurate overview of depositors. This is currently difficult without extra (manual) cleaning.

What existing behavior do you want changed?
We want to change the fact that manual cleaning is necessary to identify unique uploaders. Adding ORCIDs to unique uploaders would make manual cleaning redundant.

Any brand new behavior do you want to add to Dataverse?
A field to add ORCIDs to depositors.

Any open or closed issues related to this feature request?
No.

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 by locating how uploader and contributor identities are represented and exposed for depositors, then trace the relevant data and user-role flows. Define where an ORCID field belongs and how it would identify the same person across name variations; the issue names no files, tests, or entry points to run.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
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.