IQSS / IQSS/dataverse

Allow forced move of dataverse datasets and collections from the Dataverse dashboard

Open
#11,245 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Feature
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Overview of the Feature Request
From the Dataverse dashboard, with super-admin rights, when moving a dataset or dataverse collection, add an option to be able to force the move like the API:
curl -H "X-Dataverse-key: $API_TOKEN" -X POST http://$SERVER/api/datasets/$id/move/$alias?forceMove=true
curl -H "X-Dataverse-key: $API_TOKEN" -X POST http://$SERVER/api/dataverses/$id/move/$destination-id?forceMove=true

What kind of user is the feature intended for?
Superuser

What inspired the request?
This follows the development of issue #10304 and a discussion on the possibility of allowing the forced move of a dataverse collection

Any brand new behavior do you want to add to Dataverse?
Add the possibility for a superuser to be able to force the movement of a dataset or a dataverse collection.
This can be a checkbox before submitting the form.

Any open or closed issues related to this feature request?
JSF issue :

  • #10304

SPA issues :

  • IQSS/dataverse-frontend#309
  • IQSS/dataverse-frontend#603

Are you thinking about creating a pull request for this feature?
This is not currently prioritized in the team

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the related JSF issue #10304 and the linked SPA issues, then review the dashboard move flows and the API's forceMove behavior described here. Done means a superuser can choose forced movement for both datasets and dataverse collections, with behavior matching the documented API operations.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.