Data WG 2022-07-27 Meeting notes

5M

Action Item Followup

@Edward Zarecor

• Review status of last meeting’s action items.

20M

Present video mapping from Open edX tracking logs to xAPI

@Quitterie Lucas

Proposition of the possible mapping of the video events from edX to xAPI:

• LoadVideo to Initialized

• PlayVideo to Played

• PauseVideo to Paused

• StopVideo to Terminate

• SeekVideo to Seeked

• SpeedChangeVideo to Interacted

Discuss possible mapping for:

• HideTranscript/ShowTranscript

• HideCCMenu/ShowCCMenu

It does not fit to any existing extensions of the interacted events

• Notes:

  • We need some guidance on how to approach the native events that are not covered by the video profile. Ed will reach out ADL

  • There is a delta between the existing mapping of video events in event_routing_backends and the ADL video profile.

  • We haven’t done the gap analysis to fully understand how much work this would be.

  • We also would need to think about how event_routing_backends will respect profiles. It currently doesn’t leverage them.

5-10M

Update on the message bus

@Rebecca Graber (Deactivated)

• Current work: sending signals from studio to course-discovery

• Fundamental concerns:

  • What is an event?

    • A single field changing

    • A model changing

    • A user interaction

    • Example: COURSE_CATALOG_INFO_CHANGED vs COURSE_START_DATE_CHANGED

• Notes:

  • The 2U team is focused on deploying a single event to the bus in the next two weeks.

  • It’s important to understand that the terminology “event” is very overloaded.

    • The initial events that will be “teleported” or propogated across the micro-services are runtime events related to stage changes. A course is published in Studio and the changes to content or metadata need to be propagated to, say, the LMS and the Discovery services.

    • Events is also used to mean tracking log entries or “learning traces” in the xAPI world.

    • In the future we can imagine that learning trace events would be pushed onto the event bus. So, we want to consider the implications of the bus for the data stack.

    • That, however, is not an immediate plan or priority for the 2U Arch team.

10M?

MySQL encoding and collation thoughts

@Dave Ormsbee (Axim)

• Migrating from utf8 to utf8mb4

  • Collation changes

  • Upgrade process

  • Relationship to MySQL 8.0

• Notes:

  • EOL for MySQL 5.7 is October

  • None of the attendees are actively working on the upgrade

  • There was also no intel currently on the requirements for migrating to utf8mb4, so the impact of that is still an unknown.