Data WG 2022-06-01 Meeting notes

5M

Action Item Follow Up

Edward Zarecor

Follow Up

Jill Vogel

Event taxonomy: from the A-Z list of tracking event types, event types are inconsistently named, which makes filtering difficult.
Is it possible to add taxonomy fields (category, subcategory) to these legacy events to make grouping/filtering possible? Or if this violates their “frozen” status, can we add this info to the xAPI events?
Follows up on Data WG 2022-02-10 - topic #1: tracking logs are a mess., and a request from Harvard Medical.

• Ethics discussion on data event collection: consistent naming would make it easier for learners to identify which event types they want to opt-out of.

5M

Action Item

Andrés González

I have a proposal for this wg: people who have worked in any analytics project can prepare a short presentation (10-20 min) about a technical topic and present it in the wg meeting. The idea is to talk in detail about a specific problem faced, and show how it was solved and what are the new challenges. Some examples: showing video statistics, converting logs to xAPI, extracting tracking logs, using datawarehouses, etc. It can be recorded and stored to create a data-wg knowledge center. If there is agreement on that, I can volunteer with the first one.

5M

Quitterie Lucas

Check the mapping of problem related events (issue #15 on openedx/data-wg). A first proposal of the mapping of `problem_check` server event is available. Let’s see together what are the main information that remain in the xAPI standard and if it is enough ready to iterate on the other events

• There was a project to add an xAPI/Caliper backend overlaying the existing tracking logs capability – mentions the problem_check event, so maybe they made some progress categorizing this event?

30M

Review of the currently know data use cases

Jenna Makowski

• Review current data use cases from user interviews and those collected and provided by community members