Skip to content
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

Cascading deletion #176

Open
lwaldron opened this issue Apr 18, 2023 · 3 comments
Open

Cascading deletion #176

lwaldron opened this issue Apr 18, 2023 · 3 comments
Assignees
Labels
blocked can't be worked on now enhancement New feature or request low priority

Comments

@lwaldron
Copy link
Member

Deleting a study should also delete all experiments and signatures under that study. Deleting an experiment should similarly delete all signatures under that experiment. This is not high priority but I think it's what curators intuitively expect, there's no use case for keeping these sub-pages, it can take a while to delete them one by one, and this change would greatly cut down on the number of orphaned pages. However, after a cascading deletion it should also be not too difficult to restore everything.

@tosfos
Copy link
Collaborator

tosfos commented Apr 30, 2023

We researched this. We can implement something, but it will take a good amount of effort. Since this is marked as "enhancement" & "low priority", please confirm we should go ahead.

@lwaldron
Copy link
Member Author

lwaldron commented May 4, 2023

Let's leave it for now, it will have a low impact as it only saves a little bit of time for administrators who have permission to delete studies, and deleting is an infrequent occurrence.

@lgeistlinger lgeistlinger added the blocked can't be worked on now label May 20, 2023
@lgeistlinger
Copy link
Collaborator

Yes so I think that would totally be needed.

@sdgamboa sdgamboa removed this from BugPhyzz Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked can't be worked on now enhancement New feature or request low priority
Projects
Status: No status
Development

No branches or pull requests

3 participants