Feature Wiki
Tabs
Segmented Learning Progress
Page Overview
[Hide]1 Requirements
The current learning progress can automatically aggregate from a collection of items (e.g. for courses, folders, scorm modules).
However only the overall status is aggregated. Information like "2 out of 5" items are completed is lost. The current proposal consists of two parts:
1.1 Part 1: Enriched LP-Data for collections
The Learning Progress (LP) for a collection should aggregate more information:
- size of the lp-collection (total number of item-groups)
- number of item-groups with status "completed"
- number of item-groups with status "in-progress"
- number of item-groups with status "not started"
- number of item-groups with status "failed"
This information can be aggregated with little additional cost (new columns in ut_lp_marks), because alle LP-Events of items in the lp collection are propagated to the lp-collection. The information can then be used to construct a more detailed learning progress widgets or reports on top of that data.
The following is meant by item-groups: A lp-collection can be structured in terms of item-groups, where only a fraction of the items must be completed to complete the item-group.
1.2 Part 2: New LP-Widget
The Learning-Progress representation could be replaced by a new widget (example). This segmented progress bar consists of as many segments as there are item groups in the lp collection (default: 1 segment, if there is no lp collection). The learning progress is then visualised by colouring the segments individually (from left to right).
- On the very left: Completed segments (green)
- Next: In progress (yellow / or gray)
- Next: Not started (gray)
- Last: Failed (red)
2 Additional Information
- Idea / concept: Kiegel, kiegel@qualitus.de
- Funding: N.N. / Qualitus
- Maintainer: (will be set by Jour Fixe)
- Implementation of the feature is done by Leifos, Lützenkirchen
- 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 Discussion
Zenzen, Enrico [ezenzen], 24 AUG 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.
4 Implementation
...
Test Cases
Test cases completed at {date} by Suittenpointner, Florian [suittenpointner]
- {Test case numberlinked to Testrail} : {test case title}
Approval
Tested successfully and approved at 30.06.2015 by .
Last edited: 24. Aug 2022, 09:06, Zenzen, Enrico [ezenzen]