Feature Wiki
Tabs
Scheduled Activation for all Repository Objects
1 Requirements
Scheduled activation of content objects is currently only possible for items within courses. This feature should be made available on all levels of the repository.
2 Status
- Scheduled for: ILIAS 4.3
- Funding: Funded by Universität Münster
- Development: Feature is to be developed by Leifos
3 Additional Information
- If you want to know more about this feature, its implementation or funding, please contact: alex.killing (at) gmx.de
4 Discussion
JF 2 Apr 2012: We appreciate this feature. We schedule this for 4.3. However there is a strong need to discuss the concept and its dependency to activation times that are stored with the object (which is already an issue in courses, e.g. if activation for tests is used on the test and on the course item level). Also the relation to the presentation type "Timings View" needs to be discussed. Currently these features are very confusing. Even abandoning the presentation type "Timings View" would be an options, since it didn't get any funding in the last years.
5 Implementation
BH & MB, 8 Mar 2013: Can you tell me, where the conceptional discussions took place?
The feature is implemented, but no information about the handling of dependencies to the activation times stored with the objects is documented.
The availability which was set on tests was named ambigously and controlled the timeframe in which it is possible to take the test, but the test was always visible and readable.
Now this availability controls the visibility. This behaviour is unacceptable. It is now not possible to limit the access to the test-participation and sequentially plan a manual scoring and the presentation of test results.
But exactly this is what the test authors want. First students take the tests, then an optional manual scoring takes place and following, test results - which can be defined to show best possible answers - will become public.
When a student can see his results, but did not finished the test with "finish" button, and is not happy with his results,
he can resume the non finished pass, change his answers and go back to results, unless he is happy with his results.
This also became a big problem for one of our customers and I think other users will face the same issues.
We also heard about problems with course or session objects relating to the object activation timings from some of our customers.
For this reason, we would have been glad to join a conceptual discussion.
2013-03-12, KS: I strongly agree with Björn.
As far as tests are concerned the timing setting is not as much about the visibility in the repository but the time frame in which the participants can take a test. In this respect tests differ from other learning objects because other objects don't have this two-step-scenario (first: take the test; second: view results). As long as the access to the test results is tied to the general availability of the test it must be possible to set a time frame for the execution of the test that is independent of the visibility of the test in the repository. As it is now the usability of timing settings for tests is severley limited (and we already have people complaining about this, too).
JF 18 Mar 2013: We apologize that the documentation of the discussion on this page is missing. We definitely discussed this multiple times in the team. For now we discussed two alternatives: The first one would be to keep the settings as they are now and to give access to results with the "visible" permission only - the second alternative would be to re-instantiate the 4.2 session start/end time settings beside the availability time frame settings. We decided to go with the second solution, since it would be unusual to put so much funtionality behind the "visible" permission. Jörg will take care of this.
2013-03-18, KS: Thank you for the quick reaction. I really appreciate this roleback :-)
2013-05-14, KS: Will the feature be re-introduced in ILIAS 4.3 or will this be postponed to 4.4?
2013-05-22, JL: The participation period is now back in 4.3 and 4.4 ("second solution" from above).
Last edited: 17. Apr 2025, 15:07, Kunkel, Matthias [mkunkel]