IQSS / IQSS/dataverse

Feature Request/Idea: Support compliance with the Open Science Horizon Europe Model Grant Agreement (OS HE MGA) Requirements

Open
#10,196 19 comments 5 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
The European Research Council (ECR) is currently running a survey to collect data for updating the Study on the Readiness of Research Data and Literature Repositories to Facilitate compliance with the Open Science Horizon Europe Model Grant Agreement (OS HE MGA) Requirements. A PDF version of the survey, which was commissioned to a group of independent experts by the European Research Council Executive Agency (ERCEA) is attached to this issue.

This is an umbrella issue to cover the following features needed to achieve full Dataverse support for compliance with the Open Science Horizon Europe Model Grant Agreement (OS HE MGA) Requirements:

  1. Dedicated and separated metadata field for Grant project acronym (see survey question 4.1)
  2. Dedicated and separated metadata field for PID(s) for the author(s)’ organisation/affiliation (eg. ROR ID) (see survey question 4.1)
  3. Dedicated and separated metadata field for Grant project PID(s) (eg. Grant DOI) (see survey question 4.1)
  4. Dedicated and separated metadata field to indicate "Horizon Europe" (see survey question 4.2)

What kind of user is the feature intended for?
API User, Depositor, Guest

What inspired the request?
The ECR survey mentioned above.

What existing behavior do you want changed?
Add the metadata fields mentioned above.

Any brand new behavior do you want to add to Dataverse?
No, not brand new, but extending metadata capturing and exposing for harvesting.

Any open or closed issues related to this feature request?

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 the linked issues #6640, #7286, and #4859, then read the referenced ERC survey and attached PDF to confirm the OS HE MGA requirements. Define how the four requested metadata fields should be captured and exposed for API users, depositors, guests, and harvesting. Done means all four fields are supported consistently and their requirements are covered by tests.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.