gaia-x-dases / xapi-lms Goto Github PK

A first draft of a virtual classroom xAPI profile is designed based on BigBlueButton and Jitsi Meet. The following table lists all existing user actions and proposes an action mapping with a common xAPI statements.

Essential information (level 1)

• The meeting has started
• The meeting has ended
• A user has joined the meeting
• A user has left the meeting

Pedagogical information (level 2)

• A user is muted/unmuted
• A user is sharing/unsharing the camera
• A user is sharing/unsharing a screen
• A user has raised/lowered the hand
• A user has viewed the chat
• A user has written a message in the chat
• A poll has been created
• A user has voted in a poll
• A user has updated a vote in a poll
• A user has viewed polls tab

Advanced information (level 3)

• A user has activated/deactivated full screen

List of possible user actions

A profile modelisation for forum activties can be a starting point for all types of online discussion tools.
A first proposal of xAPI profle defines the main activities on a forum.

Essential information

• viewed a forum
• viewed a topic
• create a topic
• create a message

Pedagogical information

• updated a topic
• updated a message

Assessment EdX statements

EdX has developed its assessment solution with open response assessment. It allows to answer a question with the peer reviewing activity.
In this perspective EdX tracks the following activities:

• openassessmentblock.get_peer_submission
• openassessmentblock.get_submission_for_staff_grading
• openassessmentblock.peer_assess
• openassessmentblock.self_assess
• openassessmentblock.staff_assess
• openassessmentblock.submit_feedback_on_assessments
• openassessmentblock.create_submission
• openassessmentblock.save_submission
• openassessment.student_training_assess_example
• openassessment.upload_file

From this EdX activity tracking and the Moodle tracking, a first proposal would be to map, in coordination with Moodle assessment activity structure, to general statement templates. For example the answer to a question in an open response assessment is the same action than an quiz response. The specificity of the assessment is an information contained in the context information.

The mapping proposal for EdX event would be the following:

• openassessmentblock.get_peer_submission --> submitted answer
• openassessmentblock.get_submission_for_staff_grading --> submitted answer
• openassessmentblock.peer_assess --> evaluated an assessment
• openassessmentblock.self_assess --> evaluated an assessment
• openassessmentblock.staff_assess --> evaluated an assessment
• openassessmentblock.submit_feedback_on_assessments -->
• openassessmentblock.create_submission --> initialized an assessment
• openassessmentblock.save_submission --> saved an assessment/problem
• openassessment.student_training_assess_example
• openassessment.upload_file --> uploaded a file (context: assessment)

Problem interaction EdX statements

Problem workflow (level # 1)

• problem_check --> answered question
• problem_graded --> submitted answer
• problem_save --> saved an assessment/problem

Problem workflow (level # 2)

• problem_rescore
• problem_reset

To classify

• edx.problem.hint.demandhint_displayed
• edx.problem.hint.feedback_displayed
• problem_check_fail
• problem_rescore
• problem_rescore_fail
• problem_reset
• problem_show
• reset_problem
• reset_problem_fail
• save_problem_fail
• save_problem_success
• showanswer

• Structure documentation on profile releases bases
• Highlight the concept created in DASES profile
• Associate the Wiki Github tool for working group meeting minutes