Storage Quota for a Collection Not Updated when Deleting a Dataset

[wshahn]

What steps does it take to reproduce the issue?
This is my entire process. Please note that quota reallocation seems to work well when deleting files within a dataset, but is not reallocated when deleting a dataset. See specifically steps 10-13 below.

1. Create a collection
2. Then, create a dataset (Image 001)
3. I set the storage quota for the collection to 10MB:

$ curl -X POST -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/dataverses/$ID/storage/quota/$SIZE_IN_BYTES"
{"status":"OK","data":{"message":"Storage quota successfully set for the collection"}}
$ curl -H "X-Dataverse-key:$API_TOKEN" "$SERVER_URL/api/dataverses/$ID/storage/quota"
{"status":"OK","data":{"message":"Total quota allocation for this collection: 10,485,760 bytes"}}

4. Before uploading any files, a 10MB storage quota is reflected in the UI (Image 002)
5. Big text file successfully uploaded at 3.9MB (Image 003)
6. The quota has successfully updated with this upload (Image 004)
7. Let's delete big.txt from the first dataset (Image 005)
8. Quota is reallocated (Image 006)
9. Re-uploaded big.txt to the same dataset
10. Created a second dataset also with big.txt (Image 007)
11. The quota has updated to 2.3MB (Image 008)
12. Finally, let's delete the second dataset (Image 009)
13. We see that the quota remains at 2.3MB (Image 010)

• When does this issue occur?
  When using collection quotas and deleting a dataset.

• Which page(s) does it occurs on?
  dataset.xhtml and editdatafiles.xhtml.

• What happens?
  The quota size is not updated correctly when deleting a dataset taking up space in the quota.

• To whom does it occur (all users, curators, superusers)?
  All users (I performed this test as a superuser).

• What did you expect to happen?
  I expected the quota to be reallocated upon deleting a dataset.

Which version of Dataverse are you using?
v6.5

Any related open or closed issues to this bug report?
None.

Screenshots:
Image 001

Image 002

Image 003

Image 004

Image 005

Image 006

Image 007

Image 008

Image 009

Image 010

Are you thinking about creating a pull request for this issue?
As of now, no.

[landreev]

Looking into fixing this now.