Feature Wiki
Tabs
Further improvement of code-based registration incl. unification of registration and reactivation codes
1 Requirements
The problem: Two different codes (created in two different places in the administration) for reactivation of exisiting accounts and registration of new accounts have proven to be counter-intuitive and actually hinder code deployment in important scenarios.
The solution: We see no reason not to unify the two kinds of codes into one, that can either be used for a reactivation or registration. (Already implemented as patch for 4.4 for Universtiy of Stuttgart.)
In both scenarios the code "features" described in Improved flexibility for Key-based Registration (and already implemented in 4.4) should apply.
Furthermore whe suggest the following improvements for codes:
- Local course and group roles assigned by code should lead to these objects being places on the personal desktop (implemented in patch).
- The administrative handling for these local roles during code generation might be more intuitive. In 4.4 all that works are "bare" role titles like il_crs_member_123456, but the interface doesn't make this clear and the corresponding text field offers an auto-completion which seems to be more or less bogus at this point. Maybe 4.5 could offer a tree-based course/group selection similiar to the one used in the Overview Object/Test Overview plugin. Just an idea.
- The code generation screen should get cancel buttons.
- Codes themselves should have an optional expiration date (in addition to the time-limit options for the accounts created/reactivated with the codes).
2 Status
- Scheduled for: Release 5.0 (will be set by Jour Fixe)
- Funding: Universität Stuttgart
- Maintainer: (will be set by Jour Fixe)
- Implementation of the feature is done by Leifos
- Contract settled: Yes
- Tested by / status: Christian Bogen, christian.bogen@tik.uni-stuttgart.de / The part patched into our 4.4 already works on our test ILIAS and will be deployed to our production ILIAS on March 24th
3 Additional Information
Contact the following persons if you want to know more about this feature, its implementation or funding:
- Information about concept: Christian Bogen, christian.bogen@tik.uni-stuttgart.de
- Information about funding: Christian Bogen, christian.bogen@tik.uni-stuttgart.de
- Information about implementation: Stefan Meyer, meyer@leifos.com
4 Discussion
Matthias Kunkel, Alexander Killing, Stefan Meyer, 13 June 2014: We appreciate this request and schedule it for 4.5. We also support a tree-based course/group selection using the current explorer ui component.
5 Implementation
...
Last edited: 10. Oct 2014, 17:20, Kunkel, Matthias [mkunkel]