Improving Sandman Notifications (no deletion until user warned) about hgi-vault

[sb10]

I'm not clear on its behaviour when there's already something in the db for the file. From your description it sounds like it always just replaces the entry with a new not-notified entry? But then you'd get multiple emails about the same thing?

[sb10]

Read and understand notification code, write it up

[sb10]

On testing, 2 unexpected things happened:

1. It sent an email about a file location that sandman wasn't just run on.
2. The email contained the same fofn for all 3 warning time points.

[michael-grace]

Corrections to the Above

• The status is not "one status per file", it can be "many statuses to one file". Each warnings status will have its own tminus time.
• This also means that a deletion status is added as another status to the file.
• Deletion statuses are deleted by the schema.sql script at the start of each sandman run (so, a file will be marked as deleted status in the DB, then that status will be cleared on the next run)
• The warning statuses (and therefore the files) aren't deleted, though files for archival are
• It will send notification for all non-notified warning thresholds. Note: this will include even if the warning threshold configuration is actually changed during the warning period.

This means that the diagram should be:

                               W1       W1          W1
    W1       W1             W1 W2       W2          W2 DEL          DEL
    V        V              V  V        V            V  V            V
    |__________________________|________________________|________________>
 warning                     warning                  deletion
threshold                   threshold                threshold
    1                           2

As described above, sandman sends all notifications in the DB marked unnotified, even if the sandman run doesn't run on a directory referred to by one of those notifications.

[michael-grace]

don't move file to limbo if no warning sent - send warning instead

[michael-grace]

As an admin, if sandman can't run on a given day, I don't want it to skip warnings, so that users don't get surprised by unwarned deletions