| | | | |
|---|
| 1 | 5M | Action Item Followup | @Edward Zarecor | |
| 2 | 10M | Action item Question | @Vladimir Susloparov | xAPI Anonimus User ID & event-routing-backends feature modification. Connection between EDX and xAPI data. Let’s postpone this until a time @Vladimir Susloparov can attend.
|
| 3 | 10M | xAPI Updates | @Edward Zarecor | Meeting with ADL to discuss event mapping and profiles. cmi5 specification, xapi.com/cmi5 Conversation with @Aamir Ayub and @Zia Fazal regarding event-routing-backends Difference between server side and client side problem check – native event semantics required mapping a single native event to two xAPI events There was an attempt to include question data – choices presented to learners for example – in the statements, but that data wasn’t reliably available.
|
| 4 | 5M | Contribution data portal | @Edward Zarecor | We have deployed a hosted Grimoire Labs environment to report on contribution data across GitHub, Discourse, Slack, etc. It’s publicly accessible and will be used to track community health and growth. |
| 5 | | Open ended Conversation | | Jill without usecases it’s hard to know whether we are building the right analytics for the customer and we don’t yet have that. We risk building something that is more complex than we actually need. @John Baldwin should we consider log levels so there’s flexibility in terms of what a user can choose? @John Baldwin top design concern for any system is probably adaptability. @Jill Vogel notes that the Blender presentation at the Open edX conference is worth a watch. @Edward Zarecor An open question is what level of tooling we should provide out of the box. Clearly the foundation needs to be strong, but how much should the platform provide? Should we expect folks to take their data to their existing warehouse, LRS, etc. Getting started docs:
|