IQSS / IQSS/dataverse

Investigate supporting RAiD identifiers for project tracking (RAiD = Research Activity Identifier)

Open
#12,045 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Metadata GREI 2 GREI Year 5 Original size: 30 Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
Project identifiers and research activity records like RAiD (raid.org) facilitate reporting and discovery of research outputs via their project identifier. This feature request is about providing a dedicated place in the Dataverse metadata and/or a recommendation for where and how to place project identifiers in the current Dataverse metadata.

What kind of user is the feature intended for?
Developers, depositors and researchers/institutions looking for outputs of a specific project

What inspired the request?
We're currently developing support for RAiD identifiers in RSpace and would like to propagate that metadata automatically when researchers export data to repositories.
See also Discussion in Zulip: #community > RAiD Identifiers

What existing behavior do you want changed?

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

Any open or closed issues related to this feature request?

Are you thinking about creating a pull request for this feature?
potentially, pending available resources

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 linked Zulip discussion and Dataverse's metadata model; the issue names no files, tests, or entry points. Determine whether RAiD needs a dedicated metadata location or a documented recommendation, and define how the identifier should propagate with exported metadata.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.