-
Improvement
-
Resolution: Fixed
-
Major
-
4.4, 4.5
-
MOODLE_404_STABLE, MOODLE_405_STABLE
-
MOODLE_405_STABLE
-
When receiving the BigBlueButton Callback with analytics, the plugin process the payload and creates some entries in the `bigbluebuttonbn_logs` table.
- One EVENT_CALLBACK type record with the basic information related to the callback itself
- Multiple EVENT_SUMMARY type records with the stats of the user in the live session. (One per user in the session, this is preprocessed)
The issue is that the information related to the meeting itself is discarded, and that is needed for reporting.
Of course, that same information can be fetched from a getRecordings request when the meeting was recorded, but since BigBlueButton does not implement a getEvents action, for those meetings that were not recorded, that information is lost.
What is needed is a minor change so the raw data is stored as part of the Callback record, so other plugins or subplugins can still be able to identify the meeting general information, such as start time, end time, duration, and some of the metadata inherent to the meeting itself.