IQSS / IQSS/dataverse-frontend

Add "Move Dataverse collection" to the Move Data part of the Dashboard

Open
#309 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Overview of the Feature Request
An API endpoint exist for the often asked task of moving datasets, however, contrary to "move dataset" it is absent of the UI Dashboard.

What kind of user is the feature intended for?
Superuser

What inspired the request?
Frequent need for non tech admins to move collections

Any brand new behavior do you want to add to Dataverse?
Add a "Move Collection" button to the dashboard :
image
Leading to a similar page than the current Move Data page (see under) but with labels for Dataverse colections :
image
Modified labels for copy-pasting purposes :

  • (info message) Move Dataverse collection – Manage and curate your installation by moving a dataverse collection from one host dataverse collection to another. See also Managing Datasets and Dataverses in the Admin Guide.
  • (left section title) Dataverse to Move
  • (left section object label) Dataverse
  • (left section watermark) Enter Identifier of the Dataverse to move

Open to discussion on whether we should rather or not have move dataset and dataverse in the same move data page and not two buttons in the dashboard, but I think user would be more error prone if they have both in the same page.

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

Other dashboard issue, should this part of the UI be reworked globally

  • #258

Will you be able to contribute a Pull Request for this issue?
We will wait to have the featured contributed in JSF and the SPA in a less MVP state to start contributing for the SPA.

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 Dashboard's existing Move Data page and the linked Dataverse collection move API documentation. Compare the requested collection labels and flow with the current dataset-move UI, then implement the Dashboard entry and collection-move page. Done means a superuser can reach the new action and move a Dataverse collection through the SPA.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
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.