IQSS / IQSS/dataverse

Feature Request/Idea: Incorporate CRediT vocabulary for author/contributor roles

Open
#8,213 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Overview of the Feature Request

This is a split from #2235

The vocabulary at https://credit.niso.org/ allows for a more granular, detailed declaration of roles individual contributors and/or authors played for a dataset, software etc.

DataCite is also considering adding this to its metadata schema

What kind of user is the feature intended for?
Curator, Depositor

What inspired the request?

What existing behavior do you want changed?
Currently there is a field contributorType only, which is more on the organizational role.
The CRediT terms allow to define more granular roles in terms of activities related to a dataset or software deposited. This may apply to the existing contributor fields, but also to author.

Any brand new behavior do you want to add to Dataverse?

  • Extend the metadata schema
  • Evaluate usage in metadata exports and DataCite registrations

Any related open or closed issues to this feature request?
#2235

Notes
This might be in scope for project @hermes-hmc

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 reading the related issue #2235 and the CRediT vocabulary, then trace Dataverse's metadata schema, metadata exports, and DataCite registration paths. Done should include an agreed design for applying CRediT roles to contributors and authors, with the schema and affected integrations updated consistently.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.