<!-- /* Font Definitions */ @font-face
@font-face
@font-face
@font-face
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
span.PlainTextChar
span.EmailStyle17
.MsoChpDefault
.MsoPapDefault
@page Section1
div.Section1
/* List Definitions */ @list l0
@list l0:level1
@list l0:level2
ol
ul
-->o Forums doesn't use Sakai's Authz. The permissions for who can send email section.role.ta and site.upd are curious. Is there a reason this doesn't have a real permission?
Features
Google Spreadsheet of Features under review
Potentially controversial items:
Brief Description |
Implications or Concerns |
Solution? |
|---|---|---|
Send email feature |
<!-- /* Font Definitions */ @font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
@font-face Unknown macro: {font-family}
/* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal Unknown macro: {mso-style-unhide}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText Unknown macro: {mso-style-priority}
span.PlainTextChar Unknown macro: {mso-style-name}
span.EmailStyle17 Unknown macro: {mso-style-type}
.MsoChpDefault Unknown macro: {mso-style-type}
.MsoPapDefault Unknown macro: {mso-style-type}
@page Section1 Unknown macro: {size}
div.Section1 Unknown macro: {page}
/* List Definitions */ @list l0 Unknown macro: {mso-list-id}
@list l0:level1 Unknown macro: {mso-level-start-at}
@list l0:level2 Unknown macro: {mso-level-number-format}
ol Unknown macro: {margin-bottom}
ul Unknown macro: {margin-bottom}
--> 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? |
Implement forums.email permission |
|
|
|
Synoptic tool |
Assumes both Messages and Forums are being used, so that Messages values are displayed even if the tool isn't deployed. |
|
UI changes |
Presumably reduces training burden, but will force changes in user documentation |
UI changes will be well documented in the independent Forums 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 |