Describe the feature you'd like and what it will do
File quota system was implemented circa #1566.
However, the quota has not been enforced -- warning notifications are provided but to date users have been permitted to exceed their quota allotments.

Doc used to date: https://docs.google.com/document/d/1OxrX4qPkeYsU0WPu7BMODakCcvSumidallXZjFpnkgo/edit?usp=sharing

We need to turn quota enforcement on.
This will include:

Policy Decisions

• Decide policy on incentives and thresholds
• Different quota thresholds for .edu and .gov emails?
• Published resources will not count toward quota
• How do we handle existing users who are over quota? Example: user currently has 500GB of storage. When we flip the switch and turn on enforcement, should this user be allowed to retain all of these files? We decided to notify current users who are over quota
• Bag “shadow” – if someone has a large resource that they generate a bag for, we don’t count toward quota, but once in the cloud we cuahsi would pay for double the storage. If no downloads within a year, should we "offboard" the resource (remove the bag).

HS Development Tasks

• Form within HS UI Profile to request more quota (including how much, institution, justification).
• Simplified admin approval process in Mezanine.
• Add admin approval process via email
• Add ability to not count published resources against quota
• Add progress bar in the profile page would be very useful to represent this information. It can indicate the current amount of quota used as a percentage of total quota allocated. Extra credit if it is color coded.
• Break down quota by user/data zone
• Users are required to ask for more quota when a new file is uploaded and the quota has been exceeded by the previous upload -- If the upload was rejected then it would be direct for a user to ask for more
• What happens if someone goes over quota (starts grace period) but then reduces their storage? Does the grace period reset? (Looks like the answer is YES)
• Modify the "daily" script. Emails to admin/help should be monthly. User gets notification when login (every time). Admins we will keep with a once-per-month notification. User also gets notified every time that they go over the "soft" limit
• Ensure that we are enforcing quota at the proper times
• Published resource % should be configurable in the admin dashboard for QuotaMessages
• "Revoke" quota request -> "cancel"
• "File upload disabled due to quota enforcement" -> "Due to your storage being over Quota"
• Check that remaining grace period is reset when UQ below soft limit
• "Current users over quota are contacted and quota is adjusted" -- check email process / management script
• If no downloads within a year, should we "offboard" a resource's zipped bagit archive #5310 created a separate issue for this
• Enforcement for uploads conducted via API and HS UI (ideally before the upload starts to prevent user waiting only to find that they have exceeded quota after the upload completes)
• Add the ability to move instead of copy from UserZone to DataZone #5318 created a separate issue for this
• Just have default messaging for users that don't have an iRods account
• Uploads in process are completed even if the results in going over the quota limit (unless we know the upload size before upload starts)
• FB: more obvious red notification above the FB
• make JS notifications persistent so that it doesn't dismiss before there's a chance to read
• Check enforcement when copying files from UZ to DZ: yes, enforced in file_add_pre_process
• Write additional tests especially for handling of QuotaException
• Currently, we rely on a celery task to decrement the remaining_grace_period. This is a bad idea. What if celery task stalls? What if the task gets run manually instead of triggered periodically? Instead, we could store the date/time that the grace period will end

Devops Tasks

• Ensure protections exist to prevent issues (undesired notifications etc) on non-prod deploys
• Add the rules that exist on the beta dataZone to the beta userZone
• After additional testing, create a dot release checklist for deployment of the new engine, msi, and rule on production

Irods Development Tasks

• Ensure microservice "behaves" (ideally this would include performance enhancement for multiple file deletion) we decided to defer the iRods upgrades until after this issues is released
• Check user quota before uploading files to iRods userZone #5329 (this could be done with rules or with the internal iRods quota system. However, at this time we have decided to instead just notify support if a user that has already exceeded quota continues to upload to the userZone) we have also decided to defer this work.

Messaging and Documentation

• User messaging, update help.hydroshare.org
• Quota messages are stored in the db -- they must be updated
• Notify current users who are over quota