This is a follow up ticket from MDL-80289. I marked it as an improvement as there are not bugs related to this but this would be good to have uniform data in the database field.

In BBB, the bigbluebuttonbn_logs contains a field meetingid that used to have the format "<meetingid><courseid><intanceid>[<groupid>]". This format was used to retrieve information (which instance in fact) that was at the origin of the log. Since we also have these fields in the the courseid, bigbluebuttonid of the same time, this seems to be redundant (I guess this was because the log table used to be an event table that provided information about the imported recording that were not with the same instance).

In any case we have a couple of disrepancies and a potential future issue if we keep it this way:

• Disrepancies: the different logger function do not create the meeting id in the same format (creation, update vs meeting joined...)
• Future issues: if we still try to deduce the instance id from the meeting id, this causes issues with backup restore, changing platforms and so on... (this is maybe what's happening on MDL-80289).

So what we need to do:

• Uniformise the meetingid info in the log table
• Deprecate all methods in instance that try to deduce an instanceid from a meeting id by parsing the meetingid (this will have to be done a bit after we are sure that most platform use 4.0 at least)