Administrating Settings Templates

1 Requirements

It would be very helpful to be able to administrate the Settings Template like this: The Administration Panel should feature a checkbox to allow suppressing the type "ILIAS Standard" in the creation dialogue.
Currently the Settings Temlate (for test or survey) are created and then offered as additional types in the create-dialogue. But the ILIAS Standrad will always be the top and default option. It would be helpful to be able to switch off the standard option.

2 Status

• Scheduled for: Not scheduled yet (will be set by Jour Fixe)
• Funding: Required / Interest in funding: (please indicate if you are interested to fund this feature)
• Maintainer: (will be set by Jour Fixe)
• Implementation of the feature is done by (company, developer)
• Contract settled: No | Fill in "Yes" if a contract is already settled and add Institution / Organisation in "Funding" row
• Tested by / status: (name, e-mail), (status information set after implementation)

3 Additional Information

Contact the following persons if you want to know more about this feature, its implementation or funding:

• Information about concept: (Alexandra Tödt, toedt (at) leifos.com)
• Information about funding: (name, e-mail)
• Information about implementation: (name, e-mail)

4 Discussion

Marko Glaubitz, 23.02.2015: Dear Alexandra, thanks creating this page. We would appreciate a feature like this a lot, too.
 
However, I would like to make one detail more concrete: admins should be able to diable the standard template for each type separately. At oour university, for instance, we use the standard folder template alongside with the "upload area" template and would liek to keep it that way. On the other hand, we would love to suppress the standard survey type.
 
Ideally, in a fairytale world, it would be great to be able to configure, which types with which templates are available for a certain tree branch. But on the other hand, this might be a bit too much.

Zenzen, Enrico [ezenzen], 16 SEP 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