-
Notifications
You must be signed in to change notification settings - Fork 487
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
Moving Datasets: Provide way in the UI for a user to do this #2073
Comments
This needs to be designed during 4.0.2 to be developed during 4.0.3. |
Things to think about:
|
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. |
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:
|
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. It would however be much better if this functionality was available in the Dataverse GUI. 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. |
@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. |
Note that running MoveIT sometimes results in this error: Caused by: org.postgresql.util.PSQLException: ERROR: deadlock detected It's not clear why.
As of b39709f I'm linking to the guides from the error like this: |
@pdurbin one small suggested, add the word "currently" to "is [currently] only available" |
Or whatever it looks like. Out of scope for now. Use the API. :)
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.
The text was updated successfully, but these errors were encountered: