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
SWORD: decide if minor version bumps for datasets will be allowed #795
Comments
#608 (comment) says "We now advance the versions at the publish call." That's for the native API, which is currently documented like this at https://github.com/IQSS/dataverse/tree/master/scripts/api "Publishes the dataset whose id is passed. The new dataset version number is determined by the most recent version number and the type parameter. Passing type=minor increases the minor version number (2.3 → 2.4). Passing type=major increases the major version number (2.3 → 3.0)." So no matter what we pick for the SWORD API, people can get more granularity from the native API. |
v1 of the Data Deposit API was shipped with DVN 3.x, which only supported major versions for datasets. For backward-compatibility, at least for now, we will have v1.1 of the Data Deposit API continue to increment dataset by major version. This has already been implemented, so I'm moving this ticket to QA. As described above, if API users want more granularity in dataset version bumping, they can use the native API. |
@pdurbin I discussed this with @mcrosas and we think this is needed but can wait till after 4.0 is completed. |
@eaquigley can you please clarify what you'd like me to do? It's an easy change if you'd prefer minor versions to be favored over major versions in SWORD. |
SWORD API will check for the lowest level of bump it can do, i.e.-if only a metadata change then it would be a minor version bump happens, if a file is changed, a major version bump happens. |
All set. Moving to QA. |
Verified major version change after adding file and publishing and minor version editing metadata and publishing. |
When SWORD was introduced into DVN 3.x datasets only have major versions (1, 2, 3) but now in Dataverse 4.0 datasets can have versions such as 1.1, 2.1, etc.
In the GUI, we allow users to choose between major and minor version bumps but we can't communicate this choice via SWORD.
This ticket is about how SWORD should behave with regard to version bumps. Should it always bump to the next major version? Should it always bump to the next minor version if it can?
The text was updated successfully, but these errors were encountered: