Show Advanced KnowledgeHide Advanced Knowledge

Setting Templates Course

1 Requirements

The course object offers several settings that have to be managed by the course author in the right way to get the course she/he wants. Especially for beginners this is not always easy to understand and to realise.
 
It would be helpful if the course object offers setting templates as already known from test and survey:

• Create and name a course settings template
• Selection for Hiding Tabs
• List of Predefined settings

Such a feature should be combined with the didactical templates because both have the same intention: to make ILIAS easier to use by pre-defining settings for a specified scenario without reducing the variety of features.

2 Status

• Scheduled for: Not scheduled yet
• Funding: Required - probably by optes project (alternative solution was programmed by Qualitus)
• Development: Feature is to be developed by tbd

3 Additional Information

• If you want to know more about this feature, its implementation or funding, please contact: Matthias Kunkel (for the Qualitus version: bromberger (at) qualitus.de)

4 Discussion

Florian Suittenpointner, 27 Mar 2013:
For Volksfürsorge, we developed a solution that covers the same requirement but works differently and has some additional features while some features are missing:

• Different workflow:Our customer decided to offer course creation via a separate menu in the header bar.Course templates feature a setting that determines automatically where a course copied from this setting is supposed to be located in the Repository.Course templates are created in the Repository and look just like normal courses.In the administration (new dialogue "Course"), a target category can be selected the courses in which are treated as course templates.This is no generic solution, so for the trunk it would be preferable to offer templates in the same way like with creating tests and surveys, i.e.:
  • As option in the regular create screen.
  • Managed in a respective administration dialogue.
• Additional features:
  • Assignment of default survey for final evaluation:In the administration dialogue "Course", a category can be stated the surveys in which is used as a default survey for final evaluation.Course templates feature a setting "Final Survey".If this setting is selected, the survey is automatically copied into courses originating from the course template.Alternative solution: Every course template has its own option to select a default survey.
• Missing features:
  • Selection of fixated settings in copied courses:With test and survey templates, you can select what predefined settings are supposed to be fixated in the offspring objects, while our solution only offers the option to predefine settings and automatically fixates many settings in the offspring objects.
  • Selection of hidden elements in copied courses:With test and survey templates, you can select what settings (or even entire tabs) are supposed to be hidden in the offspring objects.

Marko Glaubitz, 23.02.2015: We would appreciate a feature close to Matthias' suggestion as well. What we need is to be able to set the default values for newly created courses in such a way that it fits the standard scenario at our university.

• What we would not want to have, would be fixed templates with settings that cannot be changed by the course creator anymore as it is the case with surveys right now. We would see this rather as a way suggesting "good practice course setup".
• Right now we have adapted the default setting directly in the code, since most values are hardwired there. Having these default values in the database might be good first step, though.

Fabian Schmid, sr.solutions, 10.03.2015: Please consider to implement a general template system for all Objects in ILIAS. The combination of Roles/Permissions and Setting would result in a flexible service for templates. This would also replace the didactiv templates und settings-templates for surveys and tests.

Zenzen, Enrico [ezenzen], 03 AUG 2022: This request no longer fulfills the requirements of the Feature Wiki. In consultation with the maintainer I change the status of the feature request to "Redundant / outdated". If the request is still relevant, please update template and mockups.

5 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.