[Sigia-l] Notification schema?

[Beau Lebens]

In my experience, managers/execs would rather receive the actual changes
and/or documents in their email directly, rather than having to click and go
to a URL to view/interact. Obviously this will depend on the exact content
you are dealing with, the size of the documents, frequency of updates etc.

RSS would be an option, but it would require the users end to interact with
your system somehow, whereas it is often a lot easier and more robust to
just build into your backend (depending on how you are building everything)
a system which just periodically checks the database for any 'events' which
need to occur, then acts them out and emails the required people.

Beau

// -----Original Message-----
// From: sigia-l-admin at asis.org [mailto:sigia-l-admin at asis.org]On Behalf Of
// joe
// Sent: Tuesday, 8 July 2003 10:58 PM
// To: sigia-l at asis.org
// Subject: [Sigia-l] Notification schema?
//
//
// Hi,
// anyone done any work or know of any work done on setting up
// notifications? It might be related to setting preferences, but
// here's what I'm working on:
// * The intranet is largely an information repository.
// * Users can comment on documents (discussion group).
// * Most documents go through an approval/review workflow, with
// different statuses throughout the docs' lifecycles.
// * Users can also select a specific document to watch, overriding
// other settings they might've mad.
// * The system can send email notification when new documents are
// created, new discussions are posted, and new statuses are applied.
//
// I'm looking for info about the usability of preference-setting
// areas. Also, I'm looking for work on the act of notification
// itself: how much do executive-level users want this kind of
// information? Has anyone done observed research into this sort of thing?
//
// Anything that might be helpful would be most
// appreciated...workflow-related stuff that has notification and
// preference-setting components, that sort of thing.
//
// TIA,
//
// joe
// ------------
// When replying, please *trim your post* as much as possible.
// *Plain text, please; NO Attachments
//
// Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
// ________________________________________
// Sigia-l mailing list -- post to: Sigia-l at asis.org
// Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
//