Bills Change Notification Suggestions
These where entered by Bill on 2/7/06 to the Suggestions page.
Re Change Notification Email events --
Suggest you log, on a per-user basis, summary info on events associated with email notifications being sent out. E.g., log the date & time of sent email notoifications, T0-address of notification, the frequency that the user has currently set for change notifications, the customer's Wiki site name, and the number (count) of specific changed pages noted in the email notification that have changed.
Then provide an enhanced feature that allows a user that has any change notification level optioned "on" to display some number of formtatted log records (say the N-number of the last-in records) for the user -- say similar to the manner in which a user can veiw pages they have changed on the site, or on a per-user basis for admin user accts.
Then retain these summary records for 30-40 days, or based on some max file size, and purge the oldest log records when you exceed the per-user specified limit.
Another enahancement perhaps in this area may include tracking the NDR (Non-Delivery Response) msgs you must receive on bounced email notifications that your server sends out. Perhaps you can keep a log on a per-user basis, or at least keep a daily count of NDRs on a per-user basis, and dispay by user in a similar manner noted above.
Re Change Notification Emails --
Semi-Customizable Fixed Subject in Emails
Actually Sent Out to Users
Suggest you consider an enhancement which provides Site Adminstrators an option to insert Adminstrator-specified text
string(s) into the Subject-header of Emails generated and sent out by the system for Change Notifications. This would essentially be giving Adminstrators some limited capability to have generated a fixed customizable Subject for these Chg. Notif. Emails; which may be changed from time-to-time by the Site Adminstrator.
E.g., one possible implimentation might be to provide a rudimentary capabiltiy for 2 optional text strings -- say <String1> and <String2>. Then the Subject in the Email-header on Change Notifications would appear as:
Subject: <String1>Recent Changes <String2> at
mysite_name
As an illustrative example, where
String1 = "XYZ Service Co. "
String2 = "on the Customer Svc Wiki"
then the resultant Chg. Notif. Email header's Subject in this example would read:
Subject: XYZ Service Co. Recent Changes on
the Customer Svc Wiki at mysite_name
Compare this resultant Subject with how the current system would generate the Subject:
The illustrative example's Subject has a more professional impact and is more informative even though it's semi-fixed. I think it would be preferred by both Site Adminstrators and users who take advantage of Change Notifications.