IQSS / IQSS/dataverse

Cannot delete more than 1 dataset in succession on https://demo.dataverse.org/

Open
#11,544 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What steps does it take to reproduce the issue?

Log in to https://demo.dataverse.org/ with an account that includes more than unpublished one data set

example:

Image

On the main account page select a dataset > edit > Delete Dataset

Image

Now immediately do the same thing for one or more additional datasets

  • When does this issue occur?

This occurs any time I try to delete 2 or more datasets.

  • Which page(s) does it occurs on?

https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/6VV5XP&version=DRAFT

  • What happens?

The first dataset appears to delete without issue, however, if I try to delete multiple datasets, the deletion process does not complete, and furthermore it appears the server may become inoperable.

  • To whom does it occur (all users, curators, superusers)?

Unknown, I only have one account on that server

  • What did you expect to happen?

I expected multiple datasets to be deleted so that I can demo dataverse in a "clean" state to potential users.

Which version of Dataverse are you using?

https://demo.dataverse.org/

Any related open or closed issues to this bug report?
I have submitted support tickets to the Harvard team on two occasions reporting this bug:

Tickets:
https://help.hmdc.harvard.edu/Ticket/Display.html?id=382238
https://help.hmdc.harvard.edu/Ticket/Display.html?id=366838

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

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

Reproduce the issue on demo.dataverse.org from the account page using the dataset URL in the report, first deleting one dataset and then attempting successive deletions. Compare the behavior and server availability after each attempt. Done means multiple unpublished datasets can be deleted in succession and the server remains usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
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.