IQSS / IQSS/dataverse

In OpenAIRE/oai_datacite export's description property, when user doesn't enter Software Version, include Software Name

Open Beginner friendly
#12,310 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GREI 2 GREI 3 GREI 4 Size: 3
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request

When the user has entered something in the Software Name field but doesn't include a Software Version, the OpenAIRE/oai_datacite export should include Software Name in the description property, as the DataCite/Datacite export already does. Currently, the OpenAIRE/oai_datacite export omits Software Name entirely when the user does not enter a Software Version.

This issue is part of a larger effort to align both metadata exports, described in https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.

What kind of user is the feature intended for?

API User, Superuser, and Sysadmin

What inspired the request?

This is part of a larger effort to align the OpenAIRE/oai_datacite and DataCite/Datacite metadata exports. There is more context at https://github.com/IQSS/dataverse/issues/11916 and https://github.com/IQSS/dataverse/issues/12281.

What existing behavior do you want changed?

Currently, the DataCite/Datacite export includes Software Name in the description property even when the user has not added a Software Version. For example:

<description
    descriptionType="TechnicalInfo">Software Name
</description>

The OpenAIRE/oai_datacite export does not include Software Name when the user does not enter a Software Version.

The OpenAIRE/oai_datacite export should be changed to include Software Name in the description property even when no Software Version is entered, matching the behavior of the DataCite/Datacite export.

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 locating the OpenAIRE/oai_datacite and DataCite/Datacite export implementations and comparing how they build the description property. Reproduce the case with a Software Name and no Software Version, then verify that the OpenAIRE export includes the name in the TechnicalInfo description while preserving existing behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.