Feature Wiki
Tabs
Centralizing online/offline status - step 4
Page Overview
[Hide]This feature request is part of a couple of request to centralise the online/offline status in ILIAS objects:
1 Initial Problem
Currently there is no centralized implementation for handling the offline status in different modules.
Centralized online/offline status actual is supported by the following object types:
- Course
- Content Page
- Forum
- ILIAS Learning Module
- HTML Learning Module
- Poll
- SCORM Learning Module
- Survey
- Test
- Bibliographic list item *1
- Chat (Repository) *1
- Data Collection (still not implemented with ILIAS 9)
- File *1
- Individual Assessment *1
- Learning Sequence *1
- LTI Consumer *1
- Test Pool *1
- xAPI/cmi5 *1
*1 … with ILIAS 9
Other objects have their own implementation or no offline/online status or intentionally not supposed to have a offline/online status.
2 Conceptual Summary
In this hopefully last step, the following components are to be migrated to the centralized online/offline status and, if necessary, the settings form is to be modified in it's order. (See Chap. 3.2)
- Blog
- Booking Pool
- Exercise
- Glossary
- Group *2
- Mediacast
- Media Pool
- Portfolio Template
- Survey Pool
- Weblink
- Wiki
*2 … For closed groups, there could be the disruption of the habit that members simply have to sign in to get access. In future, however, the online setting will still be required. It is expected, however, that the new mode of operation will be learned quickly, especially due to streamlining.
The following table shows:
- which objects do not yet have an online/offline status,
- which most probably do not have a centralized online/offline status.
Object | online/offline | centralized online/offline |
---|---|---|
Blog | no | no |
Booking Pool | yes | no |
Exercise | no | no |
Glossary | yes | no |
Group | no | no |
Mediacast | yes | no |
Mediapool | no | no |
Portfolio Template | yes | no |
Weblink | no | no |
Wiki | yes | no |
Survey Pool | yes | no |
Objects that should not have an online/offline status:
Object |
---|
Category |
Folder |
Item Group |
RSS Feed |
Session |
Study Program |
3 User Interface Modifications
3.1 List of Affected Views
- Settings-Screen of Objects
- Listing Panels on Dashboard and List GUI in Repository showing status "offline" if it is set. (Also in Listing Panels if it is used in the meantime.)
3.2 User Interface Details
In the Settings tab of each item, the second form section should be "Availability".
The first entry in the form section is "Status" and offers a checkbox "Online", which is deactivated by default after object creation.
The KitchenSink forms must be used for the settings forms. This will take work away from ILIAS 10 when we have to get rid of the old UI-components.
3.3 New User Interface Concepts
Nothing new.
3.4 Accessibility Implications
No special requirements in respect of accessibility are to be expected.
4 Technical Information
See Documentation for Implementation KS-Forms for Common Properties of an Object
5 Privacy
No personal data is stored or processed to implement this feature.
6 Security
We do not see any changes for special security issues.
7 Contact
- Author of the Request: Samoila, Oliver [oliver.samoila]
- Maintainer: Kergomard, Stephan [skergomard], Meyer, Stefan [smeyer] & Killing, Alexander [alex]
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
8 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
9 Discussion
JourFixe, ILIAS [jourfixe], 24 JUL 2023 : We highly appreciate this suggestion and schedule the feature for ILIAS 10. Please introduce the centralised online status also for the repository object pluginslot. This will allow repository plugins to use this service and its related features, too.
10 Implementation
{ The maintainer has to 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}
Privacy
Information in privacy.md of component: updated on {date} by {user} | no change required
Approval
Approved at {date} by {user}.
Last edited: 8. Jul 2024, 14:42, Samoila, Oliver [oliver.samoila]