OK. As I said, below are some basics about the upcoming notifications revamp - these apply mainly to the header notifications. I don’t want to go into details because things may (and probably will) change as we work through implementation and testing, so this list is not comprehensive.
-
“Conversations” - comments, ID remarks, and @ mentions - will be prioritized, since those are what we and our test users said were what they wanted to be notified about the most. And yes, you should only get one notification for a mention in a comment. :-)
-
You’ll be notified when your observation or an observation you are following has its community ID or data quality grade altered by the action of another user (ID, Data Quality Assessment vote, etc). You’ll also be notified about annotations or observation fields added by other users, and if an observation of yours is faved.
-
One notification per resource, even with activity from multiple users. So if 4 people comment on your observation, you’ll only get one notification for it.
-
More fine-grained control: don’t want to be notified about annotations, observation fields, or subspecies IDs? You’ll have options to turn off notifications like that.
-
An “All notifications” page that will keep your notifications for a certain period of time, in case you missed that mention or comment. It won’t be lost in the bowels of your dashboard’s back pages.
-
The ability to mark a notification as read.
That’s about it for now, I’ll leave this topic open for another day or two if you have comments or questions, but I won’t be able to say much more at this time. Thanks for all of your ideas and your contributions to iNat.