...
Ferdi: preference is to have CCX be an add-on to edX, rather than an integral feature.
- Miki: have a very limited trial with an MVP implementation
- If it's successful, shut it down, and do it right.
- But if it succeeds, we could be stuck with the MVP data.
Cale: pluggable keys could be a good way to solve this. (LIST 1b)
- (whiteboarding about opaque keys)
- course_v1: org+course+run
- course_ccx: org+course+run+ccx
- still requires spreading CCX knowledge around the code
- but less than other proposals
- this makes CCX part of the course/run hierarcy
- Chris Ewing likes it.
- CCX should be a view of a course, not a copy of a course.
- Miki: separation of CMS and LMS
- state of course at edit time doesn't have to be the state in LMS
- one course in CMS could be many courses in LMS
- state of course at edit time doesn't have to be the state in LMS
Peter: are there implementations of new keys to look at? Library keys
Field overrides: how would ccx keys interact?
- They would just key off the course_ccx ids instead of the course id plus the ccx id.
Miki: the key id is not a big deviation from the current implementation, low cost, big benefit.