IQSS / IQSS/dataverse

Feature Request/Idea: Overwrite the contributor name in the dataset version table

Open
#9,827 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Overview of the Feature Request
Overwrite the contributor name in the dataset version table

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

What inspired the request?
In the Dataverse plugin for OJS/OPS 3.3, we use the API token linked to a single account to perform Dataverse operations through the API. These operations are carried out within a specific Dataverse collection (for example: a specific journal or preprints server). Typically, the account is associated with a collection administrator.

As a result, this user is included in the list of contributors for all datasets, which can be viewed in the versions table.

We would like to overwrite this value in order to, for example, indicate the names of the dataset authors.

Any open or closed issues related to this feature request?

Discussion in community group: https://groups.google.com/g/dataverse-community/c/Oo4AUZJf4hE

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 reviewing related issue #6274 and the linked Dataverse community discussion, then trace the API operations that populate the contributor name in the dataset version table. Define how an API user can supply an alternate contributor value and verify that the dataset authors appear as intended without losing existing attribution.

Written by the indexing model from the issue text.

Assessment

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