Dataset without files are incorrectly labeled as `info:eu-repo/semantics/openAccess` within exports
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
-
What steps does it take to reproduce the issue?
Create a dataset in Dataverse without uploading any files due to the sensitivity of the data (e.g., patient-level data).
(Apply a custom license that restricts access to the dataset.)[This has no effect on this property.]
Export the dataset metadata using the XmlMetadataTemplate or OpenAireExportUtil. (Datacite or openAIRE)
Check the exported metadata and observe that the access type is incorrectly labeled as info:eu-repo/semantics/openAccess. -
When does this issue occur?
This issue occurs during the metadata export process for datasets without uploaded files. The relevant code to place another value within the export depends on the presence of a file cf. method .
-
Which page(s) does it occur on?
This issue affects the metadata export functionality and is not directly tied to a specific UI page but impacts the exported files and integrations. -
What happens?
The export incorrectly includes
info:eu-repo/semantics/openAccessin the metadata. A dataset without a file is not automaticallyopenAccess, as means to access them are defined within custom terms. -
To whom does it occur (all users, curators, superusers)?
This issue affects all users who rely on metadata exports, including administrators, curators, and external systems consuming the exported metadata.
-
What did you expect to happen?
The export should reflect the correct access status of the dataset or if not known omit this property.
-
Which version of Dataverse are you using?
6.5
-
Any related open or closed issues to this bug report?
-
Are you thinking about creating a pull request for this issue?
We welcome contributions to this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in OpenAireExportUtil.java around the linked method at line 1067, then trace how XmlMetadataTemplate and OpenAIRE or Datacite exports determine access status. Reproduce the export for a dataset with no files and a restrictive custom license. Done means the export no longer labels such a dataset as openAccess when that status is not justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100