implement notification system
open, high, Add +difficulty , Add +assigned to
Issue
Table of Contents
Watchlist card
Users create a <username>+*watchlist card that is a Pointer, where you add cards that you want to watch. Search cards' results and Pointer cards' items are treated as if they were in the +*watchlist card directly (and the Search or Pointer cards themselves are treated as if they were not). If you want to be notified of changes to a Search card (i.e., the WQL) or a Pointer card, you can add to +*watchlist a Pointer card that points to such cards.
Sample +*watchlist:
Once a day (at like 3am), a cron job runs which sends email to each user with links to all of those cards (if any) which have changed in the last 24 hours. Noting the editor of each would also be handy.
That's as much as we'll implement in a first go. When we update includer cards and in multi-edit only update inclusions that changed that will clean up what appears nicely.
Easier interface
- Cards have a new Watch tab. Clicking on it adds the card to the user's +*watchlist card (see below). While Wagn is updating it, the tab reads "..." and "updating watchlist..." appears in lower-right.
- When the update is complete, the "done" message flashes, and the Watch tab becomes Unwatch.
- Clicking on the Unwatch tab reverses the process.
(We also eliminate Options tab.)
Personal Recent Changes
People may want to see what's up in the middle of the day. So,*watchlist+*rform is hard, and sets type to Watchlist. When being edited it's just like a Pointer.
the View of +*watchlist cards looks like *recent changes, but with only the cards in +*watchlist (is this where we ended up?).
Other possibilities
Add +*frequency where users specify how often they want notification.
Tags:
Once we generate feeds, power users can get all the fancy notification they want through various web services.
When we were pondering some more complex ideas that involved many cards we ran into the issue of namespaces - would the system pre-defining cards like daily, weekly, etc. be a problem? Flipping it around, what a resource to users if those cards meant and did intuitive things? One could implement the e-mail in a Ruby card. The system runs one cron job every night which creates the cron jobs necessary to to run Ruby cards plussed to the daily every day, weekly every week, etc. Far beyond notification, this opens up Ruby cards as a plug-in-like system that could, just for example, pull from various web services - e.g., a card that shows all my Flickr photos tagged with everything i've put in my "favorite Flickr tags" Pointer card.
--John Abbe.....Mon Jul 07 00:18:29 -0700 2008
(actually written when this ticket was first created)
Once we implement notification system, if you add "InvitationRequest+*type cards" to your +*watchlist, Wagn will notify you when someone requests an account. Does this replace existing system notifying Admin, and/or extension of that to email multiple users?
Would be nice to be able to get the notification immediately.
--John Abbe.....Fri Jul 11 02:45:58 -0700 2008
