IQSS / IQSS/dataverse

Dataset Version Differences Details showing metadata keywords as changed when they were not between versions

Open
#11,578 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

First noticed on our installation of dataverse (ASU) where version difference details were showing keywords as being changed between versions when they were not. Was able to recreate the issue on a dataset in Dataverse Beta (screenshot below).

Found an additional example of existing dataset in Beta Dataverse that displays this issue. Noted that this dataset in the SPA version of beta dataverse does not show this issue.

What steps does it take to reproduce the issue?

  • When does this issue occur?
    Create a new dataset with metadata that includes keywords and their associated URIs. Without URIs, the issue does not seem to happen. Once created and published, make changes to files or metadata (not the keyword field) and republish to create a new version.

  • Which page(s) does it occurs on?
    On the View details of most recent version on the Versions tab

  • What happens?
    Viewing the differences between versions of a published dataset that has keywords with URIs in the metadata. When there are no changes in keyword metadata between versions, the difference details still display the same keywords as if they changed.

  • To whom does it occur (all users, curators, superusers)?
    All users

  • What did you expect to happen?
    The version details differences should not show changes with keywords

Which version of Dataverse are you using?
v6.6 and maybe other versions or all versions where Keyword URI fields were added

Any related open or closed issues to this bug report?
None that I could find

Screenshots:

Image

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

Reproduce the issue from the Versions tab using a published dataset with keyword metadata that includes URIs, then compare the version differences after changing files or other metadata without changing keywords. Trace the code responsible for rendering version-difference details and verify that unchanged keywords no longer appear as changes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.