Dataverse: Support versions before a dataset is published

[mercecrosas]

We want to be able to support multiple versions of a pre-published dataset.

Questions:

• what happens to the pre-published versions when you publish the dataset

[posixeleni]

I just assume that anything prepublished would be version 0, 0.1, 0.2, etc and once you publish it bumps up to version 1?

[sbarbosadataverse]

Thinking we can get rid of the prepublication versioning, or give user the
option to keep them although I don't see the benefit of the latter at this
point. The prepublication versioning was to allow them to make their first
draft "complete" before publishing---I wouldn't even consider it versioning
as it relates to publishing -- prepublication is more
managing/cleaning/organizing the data for the purpose of publishing

On Mon, Oct 27, 2014 at 2:30 PM, Eleni Castro [email protected]
wrote:

I just assume that anything prepublished would be version 0, 0.1, 0.2, etc
and once you publish it bumps up to version 1?

—
Reply to this email directly or view it on GitHub
https://github.com/IQSS/dataverse/issues/1002#issuecomment-60645307.

[mercecrosas]

This is 4.1+. We are discussing this with Jon (ODUM) and Thomas (ICSPR).

On Mon, Oct 27, 2014 at 2:37 PM, sbarbosadataverse <[email protected]

wrote:

Thinking we can get rid of the prepublication versioning, or give user the
option to keep them although I don't see the benefit of the latter at this
point. The prepublication versioning was to allow them to make their first
draft "complete" before publishing---I wouldn't even consider it
versioning
as it relates to publishing -- prepublication is more
managing/cleaning/organizing the data for the purpose of publishing

On Mon, Oct 27, 2014 at 2:30 PM, Eleni Castro [email protected]
wrote:

I just assume that anything prepublished would be version 0, 0.1, 0.2,
etc
and once you publish it bumps up to version 1?

Reply to this email directly or view it on GitHub
https://github.com/IQSS/dataverse/issues/1002#issuecomment-60645307.

Reply to this email directly or view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_IQSS_dataverse_issues_1002-23issuecomment-2D60646461&d=AAMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=MoES6dokjPLLcKaEAd7qaCuTcYZ4jLjEOBQnbbJ9BaA&m=IeiWzZpmJ7v5LBG8mkB61KVnNGOOxlYSoQ0wZw4voIk&s=hjYJYyy-lIxMF6cIqCvbx9PDuCfyup3aeR4JOMd6f8Y&e=
.

[pdurbin]

@mercecrosas is this still something you're interested in?

[RightInTwo]

I would love to see this in regards to #5764. The use case would be a) triggering an update of the CRIS on new versions of unpublished data and b) tracking changes when passing on the data between different people in the curation process.

[pdurbin]

b) tracking changes when passing on the data between different people in the curation process

There is some amount of tracking when a curator returns a dataset to an author. Via API a curator can include reasonForReturn as explained at http://guides.dataverse.org/en/4.15.1/api/native-api.html#return-a-dataset-to-author and note is saved in the workflowcomment database table: http://phoenix.dataverse.org/schemaspy/latest/tables/workflowcomment.html . This was implemented in #3943 and there's a lot of conversation about it at 'Help Wanted: stories related to "Submit for Review" and "Return to Author"' thread at https://groups.google.com/d/msg/dataverse-community/bGlCU2pbQpE/h3d9enX9AAAJ . There is demand for a GUI for the curator to be able to write this note, reflected in the following issue: Return to Author: When returning datasets that were submitted for review, I want to add a feedback note. #3702

[qqmyers]

FWIW: In QDR we've had some discussion on this - still thinking through the overall curation strategy, but if curators work in Dataverse to do things like replace files with archival versions, etc., having pre-publication versions would be a good way to track their efforts.

[RightInTwo]

And also, we will definitely have data that we cannot publish but still want to curate and archive. This would be a nice way to facilitate that.