Sequence of learning steps
Sequential or " no sequence ".
Learning path courses can be configured to be followed sequentially or in any order by learners. The basic setting is set on the top course element, which is automatically created when a course is created. This setting then initially applies to the entire course.
If certain areas of the course are to be given a different setting, this can be done by adding and configuring the course element "Structure". The selected setting will then apply to all course elements subordinate to this course element "Structure". For example, a course can be configured as sequential by default, but a certain area in the course can be permanently accessed in any order.
Tab "Learning path"
Learning paths, unlike conventional courses, do not have the tabs "Visibility" and "Access", but the tab "Learning path". The following things can be configured here:
- Mandatory: The completion of the course element is binding and will be considered in the percentage evaluation.
- Optional: Completion will not be taken into account when displaying percentages.
- Release date: Date as of which the element can be edited by the user.
- Due date: If a course element is mandatory you can also enter a date by which the element must be completed.
- Learning time (minutes): Here you can enter how long the creator estimates the processing time for a given element. It does not depend on how much time the user really needs for that element. This setting is particularly relevant if the progress of learning is determined by the processing time in the course settings. In this case all times are summed up and the total sum is taken as the basis for 100%.
These settings are available for almost all course elements. An exception is the course element "Structure" that is meant for bundling course elements. In the structure element you can only define a sequence of learning steps that applies to all subordinate course elements, either sequentially or in specific order.
Completion criterion
Most course elements offer the possibility that the element is considered "done" when it is opened or when the user explicitly confirms the processing. Depending on your course element there are also other criteria for completion.
Visit course element | Task, Single Page, Test, CP, Folder, Blog, Video live stream, Edubase, External Site, SCORM, Podcast, Video, card2brain, Assessment, Grouptask, Self-test, Check list, Survey, Wiki, File dialog, Particiant list, OpenMeeting, Forum, Participant folder, Vitero, GoToMeeting, Enrollment, E-mail, Notification, Calendar, LTI, Appointment scheduling, Topic assignment, Link list, Form |
Confirmation by participant | Task, Single Page, Test, CP, Folder, Blog, Video live stream, Edubase, External Site, SCORM, Podcast, Video, card2brain, Assessment, Grouptask, Self-test, Check list, Survey, Wiki, File dialog, Particiant list, OpenMeeting, Forum, Participant folder, Vitero, GoToMeeting, Enrollment, E-mail, Notification, Calendar, LTI, Appointment scheduling, Topic assignment, Link list, Form |
Score: Done when the user has reached a certain minimum score. | Task, SCORM, Assessment, Grouptask, Check list, Test, LTI |
Passed: Completed when the pass criteria defined for the course component are met. | Task, SCORM, Assessment, Grouptask, Check list, Test, LTI |
Execution done: Completely done when all steps of the task have been completed. In the intermediate stages, partial completion is taken into account as a percentage of progress. | Task, Grouptask |
Coach has set status to "done": Erledigt wenn der Betreuer dies manuell gekennzeichnet hat. | Assessment, Check list |
Test finished | Test |
Survey finished: Done when the user has submitted the survey. | Survey |
Enrollment done: Done if the user has enrolled in one or more group(s). | Enrollment |
Form filled in | Form |