For some datasets' dataverse_json exports, there is no `citationDate` key showing what the dataset's citation date is
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?
-
When does this issue occur?
When looking at the dataverse_json exports of some datasets -
Which page(s) does it occurs on?
In the dataverse_json exports of some datasets, but not all datasets -
What happens?
In the dataverse_json exports of some datasets, there is nocitationDatekey showing what the dataset's citation date is. For example, see the dataverse_json export of the dataset at https://doi.org/10.7910/DVN/PZBQTD:In the
datasetVersionkey, there should be acitationDatekey, but there isn't. For datasets where there is acitationDatekey, I've seen it right below thepublicationDatekey, like the part in orange in the screenshot below. -
To whom does it occur (all users, curators, superusers)?
All users, curators, superusers -
What did you expect to happen?
In the dataverse_json export of the dataset, thedatasetVersionkey should include acitationDatekey, like there is in the dataverse_json export of the dataset at https://doi.org/10.7910/DVN/5KLDV6:
Which version of Dataverse are you using?
v6.9 (on Harvard Dataverse)
Any related open or closed issues to this bug report?
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 by comparing the two linked dataverse_json export responses for the affected dataset and the dataset that includes citationDate, then review related issues 9656 and 12316. Done means the datasetVersion object in exports includes a citationDate key for datasets currently missing it, without removing it from datasets where it already appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100