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

tools/delete_imaging_upload.pl #1067

Open
2 of 6 tasks
cmadjar opened this issue Apr 5, 2024 · 1 comment · May be fixed by #1121
Open
2 of 6 tasks

tools/delete_imaging_upload.pl #1067

cmadjar opened this issue Apr 5, 2024 · 1 comment · May be fixed by #1121
Assignees

Comments

@cmadjar
Copy link
Collaborator

cmadjar commented Apr 5, 2024

  • Test deletion of an entire MRI upload (UploadID) with SQL and file backup (ensure the SQL and file backup repopulate the database correctly after the deletion)
    • default file generated, and sourced back without issue.
  • Test deletion of an UploadID that has the same TarchiveID as an other UploadID - this should fail with an error message explaining there are multiple UploadID for a given TarchiveID
    • update tarchiveID for an UploadID in table mri_upload with another existing. Run the script, failed.
  • Test deletion of an UploadID with QC information attached - this should fail with proper error message
  • Test deletion of an UploadID with a parameter_form filled and the option -form and ensure the entries in the parameter form have been deleted
  • On a defaced dataset, test running the delete script with the -defaced option - this should delete only non-defaced MINC files for that UploadID
    • cannot find a defaced dataset.
  • Run the delete script with option -basename <FileBaseName> specifying a basename for the MINC files to be deleted - only images matching that basename should be deleted for the UploadID

Bugs found:

@CamilleBeau
Copy link
Contributor

The checked steps ran as expected, the rest I believe are impacted by this issue, so I will continue testing when resolved!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants