Implement alert mechanism about gbif-alert HOT 5 CLOSED

As we discussed during the meeting, I add some proposed solutions:

1. some shapefiles could be added to this repository as we did for the three river basins
2. the GDPR problem is not really at GBIF level: we will provide the link to the raw observation webpage (iNaturalist, waarnemingen.be, observations.org). All details the observer want to share are there, the rest is not something solvable, I think
3. email notification frequency should be set up at alert level, not at user level

from gbif-alert.

(we also added notes for that in #9: I'll have to merge/clean those notes).

Good thing is: the general mechanism appears solid to the stakeholder's we've talked with, both internally (OSCIBIO, Bram, ...) and externally (Etienne & co).

from gbif-alert.

Update: I will soon implement the first version of this major feature. We need a lot of other systems in place for it, though.

Requirements:

• basic user management
• stable identifier mechanism for the occurrences (between data imports)
• ability to send e-mails
• per-species filtering
• per-area filtering (#66)
• rock-solid data import (see #40 and #62)
• seen/unseen status for observations (per user) - done, but lacks unit tests
• API: per-status (read/unread) observations filtering: done, but needs: polishing SQL query in maps.py
• maintenance mode

Feature:

• "My alerts" page
• Add alert page
• Edit alert page
• See alert details (observations)
• E-mail notifications
• Show "unseen observations counter" for each alert, on "My alerts" page.

from gbif-alert.

Update: feature implemented, but we need good tests for the email notifications, for example:

• That the send_alert_notifications_email command does the right thing
• That Alert.email_should_be_sent_now follows the correct business logic
• That Alert.send_notification_email log errors and save the timestamp
• That the user-facing page shows the time of last email sent

from gbif-alert.

Since a basic alert/notification mechanism is now in place, I suggest closing this issue and extracting the few remaining points/ideas to smaller, more actionable issues.

from gbif-alert.