-
Notifications
You must be signed in to change notification settings - Fork 495
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
Feature Request: Add API endpoint for comparing Dataset Versions #10888
Comments
There are multiple options for how the response could be formatted: Option 1. json list with two objects. each object contains only the modified fields. Option 2. json response with before and after values: I'm sure there could be more options. @ekraffmiller could you let me know what format would make the most sense for the SPA code? |
FWIW: I think the outputs from the DatasetVersionDifference class are more like option 2. Similarly, I think that's the format closer to how we display the differences in the dataset page version table. |
@ekraffmiller
|
thanks @stevenwinship I will review the SPA requirements today |
Hi @stevenwinship sorry for the late reply, for the Compare Version Details Popup, we will need the changes grouped by metadata block. Also it would be more flexible in the UI to have the changed values in an array (for "multiple" type fields.) Here is an example:
|
I'm sorry I realized there is some missing file information in the JSON example I sent you, here is an updated example. I have added fields to the file elements. I also included a 'filesReplaced" array.
|
Here is an example of the latest json format:
|
Overview of the Feature Request
Need an API endpoint that will compare two dataset versions and return a list of differences between the versions. This is needed to support the SPA Dataset Page
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
API User
What inspired the request?
IQSS/dataverse-client-javascript#197
IQSS/dataverse-frontend#511
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
New Dataverse API endpoint
Any open or closed issues related to this feature request?
Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?
The text was updated successfully, but these errors were encountered: