Sakai 11 new properties and permissions
Release | Tool/Service | Property | Ticket | Change |
|---|---|---|---|---|
11.0 | Dropbox | dropbox.maintain.own.groups | Courses with multiple TAs (teaching assistants) managing multiple discussion sections have a need for the TAs to be able to access student dropboxes by their sections. | |
11.0 | Samigo Test and Quizzes | samigo.pdf.convertformattedtext |
| |
11.0 | Samigo Test and Quizzes | samigo.SelectAssessmentBean.warnUserOfModification | # SAM-1331: Warn user of modification to edited quiz | |
11.0 | Samigo Test and Quizzes | samigo.fromAddress | +# SAM-1947 Email notifications on Samigo Submission | |
10.0 | Samigo Test and Quizzes | varies by question type | Allow question types to be selectively disabled via Sakai properties. Added in Sakai 10 | |
11.0 | Samigo Test and Quizzes | samigo.allowMinScore | ## TEST & QUIZZES (SAMIGO) | |
11.0 | CK Editor (Rich Text Editor) | auto save | not a Sakai property! ckeditor.launch.properties in the source code, so there are properties but not Sakai properties like we think of them. We're really just including a CKEditor community plugin so the configuration and code maintenance of the plugin is up to them (http://ckeditor.com/addon/autosave). | |
11.0 | MathJax | on by default. several properties. | +# SAK-22384 - MathJax support is enabled by default | |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
11.0 | Site Info | site.setup.import.addmissingtools |
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
11.0 | Gateway page | site.types.publicChangeable | It enables an institution to define what site types are by default publicly available via the "Site Browser" tool on the Gateway. It also enables an institution to define what site types are or are not changeable by the maintainer, with regards to the "public" vs. "private" setting (site browser). | |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
11.0 | Portal | moresites.externalConfig.siteTypes | Currently, More Sites tab classifies the sites by their site type and course term if there is one, but this has several issues. -New site types can't be classified apart without hardcoding them. Our proposal is two optional properties in sakai.properties. One (moresites.externalConfig.siteTypes) with the list of site types and other (moresites.externalConfig.prefix) with the prefix to use in the properties files, so every site type in the list can be classified in More Sites tab by its internationalized property key. For example, for setting two new site types (courseAsig is a new course type and course 2 is a new site type), sakai.properties would have this: moresites.externalConfig.siteTypes=course_asig,course_2 And the properties "moresites_course_asig" and "moresites_course_2" would be used for the i18n texts in sitenav.properties. If moresites.externalConfig.siteTypes is not set or is empty, the usual logic is applied. | |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
11.0 | CK Editor | wysiwyg.editor.ckeditor.browser | # The file browser to use for picking files in ckeditor | |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
| basiclti.provider contentitem.provider |
| |
|
|
|
| |
11.0 | Assignments | assignment.grading.decimals | +# ###################################### | |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|
|
|
| |
|