When a dataset is moved from one dataverse to another, the dataset should take on the new dataverse workflow

[sbarbosadataverse]

a dataset was moved from a journal to harvard root after it had been submitted for review.
in root, the dataset workflow setting did not change from that of the journal-"submit for review" was not removed

see attached screen shot

*i requested permission from journal to move published dataset back to their journal dataverse as should be the case

[djbrooke]

Thanks @sbarbosadataverse for reporting. Before we work on this, we'll need to determine what status is expected when a move occurs under different conditions.

[sbarbosadataverse]

I deleted the dataset because the author needed to recreate it in the journal dataverse for publishing. just an FYI

[cmbz]

2024/05/06

• The logic of what aspects of previous workflow state are preserved or cleared after the move will need to be defined. One idea: clear the previous state whenever a dataset is moved to a new location.

[pdurbin]

We have a SubmitDatasetForReviewCommand. Would a WithdrawDatasetFromReviewCommand be appropriate? That is, put it back in the state it was in before it was submitted for review. I think removing the lock (DatasetLock.Reason.InReview) is the main thing. I'm not sure if we'd want to send notifications or not. "This dataset has been withdrawn from review." 🤔

Anyway, a new command could be useful in cases that don't involve moving datasets.

We should discuss the plan and scope before we size this.

[cmbz]

Sized at 10, needs a bit more investigation. Resize as needed.

[sekmiller]

The logic added here is based on the permissions granted to the default contributor of the target Dataverse. If a dataset that is locked for review is moved to a collection where the default contributor may publish datasets, then the lock is removed.