Attendees:
edX: Clinton, Nimisha, Gabe, Ed, Piotr, Chris Dodge, Steve Magoun, Miki, Matt, Cale
MIT: Ferdi, Peter, Carson, Brandon
Issues:
- Piotr: Using it for meta-data is fine, but to get children, access videos, etc, the semantics haven't been thought through
- those APIs should exist, we already have OLX that handles the full messiness of the course structure.
- those APIs need to be driven by use-cases, and must be unambiguous.
- Miki: OLX isn't a transport API, and Clinton has use-cases.
- possibility: scale back the API to do just what Analytics needs
- or, develop the use cases so we can fully develop the API
- Clinton: "Within insights, we need course metadata, the course name, and the course structure for answer distribution."
- from assignments, drill down into problems and problem parts.
- Insights is using ...?
- Question: for A/B-tested gradable content, what will the API produce?
- Insights would want both paths of the A/B-test
- Transport vs storage representation:
- transport APIs don't need to mirror the storage representation of an object. The API may need a more compact representation, for example.
Clarification: this API does not provide a student-based view of a course.
MIT has a course import/export API that does take the student's view into account. That API hasn't yet been reviewed by Architecture Council, but it's in a PR.