E-mailFeatures
Google Spreadsheet of Features under review
Potentially controversial items:
| Brief Description | Implications or Concerns | Proposed Solution | Completed? |
|---|---|---|---|
| Send email feature | The permissions for who can send email are tied to section.role.ta and site.upd. while forums doesn't use Sakai's Authz, is there a reason not to define a forums specific permission within Sakai's authz? | If team is in agreement this is necessary - Implement forums.email permission If team is in agreement this is not necessary, press ahead |
still under discussion |
| Display last activity time and sort by recent activity | Tried to view feature on qa1-nl and am not seeing it or understanding it |
N/A - David has clarified |
|
| Synoptic tool | Assumes both Messages and Forums are being used, so that Messages values are displayed even if the tool isn't deployed. | Provide some mechanism whereby if Messages is hidden or stealthed, then this column will not be calculated or appear in the display |  Documentation is up on http://confluence.sakaiproject.org/pages/viewpage.action?pageId=26804254 and code is ready to be merged from https://source.sakaiproject.org/svn/msgcntr/branches/SAK-15655 |
| UI changes | Presumably reduces training burden, but will force changes in user documentation | UI changes will be well documented in the independent Forums release. |
(Documentation on this particular changeset has been supplied, and some additional work to incorporate other UI changes will be done for the release) |
| Mark messages read after "display all" is viewed | When you "display all" messages they aren't marked as read. This behavior has been confusing at a number of schools, it is non-standard discussion board behavior, but there is not a consensus that it is a problem. | "Display all" marks messages as read by default, so that the default behavior matches user expectations, but there is a property to optionally turn this off |  |
| View Messages of one user |
Location and appearance of print and close buttons are somewhat unconventional. Reasons described here. |
2 suggested adjustments, described here. |
Will contact designer and developer; don't know if they will agree or if there is time. Relatively minor UI issue compared to benefit, but if they agree with suggestions and have time, great. If they agree, but have no time, suggestions can wait till next release (and maybe Stanford can help). |
