vu-rdm-tech / adminyoda

A simple implementation of a "shadow database" to store administrative information and generate usage reports.
0 stars 1 forks source link

Possible Vaults under datamanager- folder #1

Closed peer35 closed 2 years ago

peer35 commented 2 years ago

While trying to remove a group with an existing Vault it looks like the vault folder and datasets are moved to the datamanager folder??? Or this happens when updating metadata??? /tempZone/home/datamanager-peter-test/vault-accept172/mapje[1627374525]

peer35 commented 2 years ago

Nevermind this seems to contain just the metadata file?

ils /tempZone/home/datamanager-surf/vault-onesix/pub1[1612521056]
/tempZone/home/datamanager-surf/vault-onesix/pub1[1612521056]:
  yoda-metadata.json
peer35 commented 2 years ago

Retried by submitting a new dataset to the vault.

Then I updated the metadata

peer35 commented 2 years ago

Also emptied and deleted a research group. The corresponding vault stayed in its default location under /tempZone/home

peer35 commented 2 years ago

Looks like I don't have to collect stats from the datamanager folder.

Stats of orphaned vaults should still be counted.

The cleanup job only sets vaults and datasets to deleted if the data is no longer updated. Will recheck what happens to /tempZone/home/datamanager-surf/vault-onesix/ now research-onesix has been deleted.

peer35 commented 2 years ago

Made changes to the views and tasks.py to make sure orphaned vaults are counted and shown.

9d10d725c7bac50ca9f1470cdcd90614d84e8b12 85690dcf6a37b335e7a413d141d81ea946752561 7b1f02569f7b6e831b67fbe1687d017c548f58a1 46674b38919b87262f697c75adfeafea00cf26c8