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.
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.
Action items
Add action items to close the loop on open questions or discussion topics:
Edward Zarecor Connect with ADL and Quitterie Lucas on a strategy for extending the video profile to support edX events.
The ADL team has already responded to our query about how to support events that don't map cleanly from native events to xAPI video profile events. The key bit is
”It is my opinion that vocabularies, particularly with something as open ended as “the set of things one can interact with” shouldn’t be closed. I don’t believe this was the intention with the Video Profile. I think there were some that were identified, but the intention was that it should always be open.”