Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dataset Page: Create use case for comparing dataset versions #511

Closed
ekraffmiller opened this issue Sep 27, 2024 · 2 comments · May be fixed by #551
Closed

Dataset Page: Create use case for comparing dataset versions #511

ekraffmiller opened this issue Sep 27, 2024 · 2 comments · May be fixed by #551
Labels

Comments

@ekraffmiller
Copy link
Contributor

ekraffmiller commented Sep 27, 2024

Overview of the Feature Request
For the Dataset Page, there are two places where we need to compare dataset versions

  • Versions Tab of the Dataset page: to display the differences between user selected versions
Screenshot 2024-09-27 at 8 36 48 AM Popup from View Details link: Screenshot 2024-09-27 at 8 36 57 AM
  • Publish Dataset action: we need to compare two versions to determine if a Major Release is required
Screenshot 2024-09-27 at 8 34 53 AM

Any open or closed issues related to this feature request?
Depends on IQSS/dataverse#10888 and IQSS/dataverse-client-javascript#197

@ekraffmiller
Copy link
Contributor Author

ekraffmiller commented Nov 20, 2024

PR #551 also includes the use case for comparing dataset versions. Note that the new Dataverse API contains all the differences, but it is not in summary form. We need to decide where to generate the summary data - in the API, js-dataverse, or within the SPA

@ekraffmiller
Copy link
Contributor Author

Closing this because in #551 we included the use case for comparing dataset versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done 🧹
Development

Successfully merging a pull request may close this issue.

1 participant