Moving Datasets: Provide way in the UI for a user to do this

[eaquigley]

Have discussed this in the past but did not do if for 4.0. If a user uploads their dataset into the wrong dataverse, could we have a way in the UI for them to change this.

Additionally, I'd like to track how many RT tickets we have about this now that 4.0 is out and see if it is happening as frequently as it was in 3.6 to determine how necessary this is now.

[eaquigley]

This needs to be designed during 4.0.2 to be developed during 4.0.3.

[eaquigley]

Things to think about:

• When a user moves a dataset into a dataverse, if that dataverse doesn't have the metadata domains the dataset uses, the user needs to be told to go to the dataverse and enable the metadata domains needed for the dataset.
• Can we do this for them somehow? Tell them the dataverse doesn't have the needed metadata domains, needs (insert metadata domains), would you like to add them? If not, dataset cannot be moved.

[pdurbin]

We used to have a "move dataverse" command but it was problematic and #283 is still open. The challenges listed in the Google doc mentioned in that issue still apply: Implications of moving dataverses and datasets.

It sounds like in production we've moved a few things manually. I'd be interested in knowing what the steps have been.

[pdurbin]

See also the "How to move dv's, ds" doc at https://docs.google.com/document/d/1A2v_ylLIRLIV6UpkDAJNNiFQt7q3SrAtAvQmg4nHBoY/edit?usp=sharing mentioned at https://groups.google.com/d/msg/dataverse-community/polE7z9_-NE/3xwAxgIHGgAJ

Here are the related issued:

• Moving Dataverses + Datasets: Provide way in the UI for a user to do this - Moving Datasets: Provide way in the UI for a user to do this #2073
• Move Dataset: Allow super user to move a dataset to another dataverse, one at a time. - API endpoint to move dataset: Allow super user to move a dataset to another dataverse, one at a time. #2226
• Move Dataverse: Allow super user to move a dataverse and reindex it and all child objects. - Move Dataverse: Allow super user to move a dataverse and reindex it and all child objects. #2278

[PaulBoon]

We at DANS felt the urge to have a GUI to do the moving of datasets and therefore we have developed a separate web application that must be deployed on the same Glassfish as Dataverse.
Our Github repo: https://github.com/DANS-KNAW/dataverse-datasetmover
It uses the 'move' API introduced in version 4.8.6.

It would however be much better if this functionality was available in the Dataverse GUI.
For the initial implementation I would restrict it to superuser only.

My proposal is to add a 'Move Dataset' option in the 'Edit' dropdown list at the bottom just above 'Deaccession Dataset'. The associated 'move' dialog would allow for the selection of the target verse. At the bottom, similar to the deaccession, action buttons for 'Move' and 'Cancel'.

This is useful fo single move actions, for 'batch' movements we might want a 'Reorganize' block on the Dashboard. But that would be another issue.

If there is no objection we at DANS could plan to spend some time and work towards a PR.

[pdurbin]

@PaulBoon no objection from me but I dragged this issue to code review at https://waffle.io/IQSS/dataverse to bring it up at standup in about an hour to get more opinions. I like your idea to focus on "single move" operations first rather than trying to support batch operations as well.

[pdurbin]

As of b39709f I'm linking to the guides from the error like this:

[scolapasta]

@pdurbin one small suggested, add the word "currently" to "is [currently] only available"

[pdurbin]

Ok, I'm moving this to code review because I think I'm done.

In 10f85cd fixed a spelling error @dlmurphy caught.

In 1b2c205 I added "currently" for @scolapasta

In 9ca7383 I added a link to the guides from the blue info box as requested from @mheppler and @dlmurphy which looks like this: