Management and Reporting Portlet

Possible Features

• Audit notifications that were sent
• Author notifications
• Curate list of groups available for mass notification
• Map which authorized notification authors may notify which groups

Purpose

The Management and Reporting Portlet should allow users to view notifications and drill down to view the status of each message per recipient.   The management portlet content should only be available to users that have the appropriate roles.   

Supported operations:

The Management and Reporting portlet should be designed in a way that will allow administrative users to:

• View the list of current notifications.
• View the details for any notification.   The user-interface should intelligently handle displaying the additional metadata properties associated with each message even if the portal itself does not utilize that metadata.
• View the list of recipients for any notification.
• View the status updates of a notification for any recipient.  This operation should allow the admin user to drill down from notification to recipient and then determine actions the user has taken on the notification.   Examples of the type of information that should be available would be records to indicate when the notification was sent to the user, when the notification was acknowledged, if the user favorited the notification, or if the user dismissed the notification.   Available state information is going to be limited by delivery mechanism.  For instance, it may not be reasonable to expect a status update to indicate that a notification sent via SMS was read.
• The management portlet should provide basic support for authoring new notifications.   It should provide enough of a base UI to allow users to set all static fields and it should provide a mechanism for attaching optional metadata as required.