Feature Wiki
Tabs
Active user session management
Page Overview
[Hide]1 Initial Problem
Unfortunately, there is no option in ILIAS to manage active user sessions - for example, to see what users in specific roles/courses are actively using on ILIAS.
Scenario
Our organisation restricts the use of mobile phones and in an in-class scenario where students are completing a short test on their mobile phones, staff are unable to actively monitor the use of devices in real-time. Staff currently have access to the UserTakeOver plugin, however, this does not achieve the goal of being able to see/manage what students are doing on their devices live.
2 Conceptual Summary
We are ideally looking for a dashboard whereby:
- a teacher can select a course/role/staff (via org. units) which they would like to monitor
- they can see which page someone is on, or which test they are completing
- if a test - see which question currently being completed
- see time spent on page/question (eg. to monitor if someone has closed ILIAS in the foreground but kept it open in the background)
- the colour of the block changes as time progresses - set by admin
- a teacher can 'jump to' view/page in question if needs be
- auto-refresh where possible or an option to refresh
- logging/exporting
- From an administration perspective, being able to disable some roles from being monitored, or at least limiting which roles have access to this dashboard.
3 User Interface Modifications
3.1 List of Affected Views
- Potentially implemented in the Administration area, or added through the Repository/Course in question.
- Alternatively, this could be linked in with Organisational Unit areas in ILIAS and implemented in the 'Staff' section.
3.2 User Interface Details
From my perspective, this would be a brand new dashboard, with a context bar at the top (under the Breadcrumb bar) with options to:
- Export
- Choose org unit/course/role to monitor
- Set refresh intervals
The user activity would be in 'blocks' presenting:
- time elapsed
- main resource in use and subsection/use of that resource
- link to resource; hyperlink
3.3 New User Interface Concepts
This will require completely new UI concepts. I have attached a screenshot of an 'idea' of this feature concept.
![](./data/docu/mobs/mm_92632/Screenshot_2022-05-06_at_01.45.50.png?il_wac_token=bcf0a7c8a37982d1debf9a94773b238db51c0807&il_wac_ttl=5&il_wac_ts=1725755145)
3.4 Accessibility Implications
{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }
4 Technical Information
{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
5 Privacy
The use of personal data would mainly be for logging/export/use of the dashboard.
- Username/First-Last Name
- Time elapsed in session
- Activity currently being performed in ILIAS at that time
6 Security
{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }
7 Contact
- Author of the Request: [jroj]Jakub Roj
- Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
- 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
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}
Approval
Approved at {date} by {user}.
Last edited: 6. May 2022, 02:53, [jroj]