POC for course tool launch #386
Conversation
zacharis278
force-pushed
the
zhancock/lti-course-tool-poc
branch
from
fdb5aa9
to
32d61ab
Compare
| # Problem. How can we get the user's role for the passed in course/context? | ||
| # We have to use a compat layer to do this which gets messy because this isn't | ||
| # just needed in the LMS but also exams. | ||
| user_role = None |
There was a problem hiding this comment.
this is really problematic when it comes to running this library in anything other than the LMS. We need to ask the running service for user permissions.
|
@MichaelRoytman I'm leaning towards abandoning this and just having exams (or LMS for a different project) build it's own launch. Having an endpoint that works for free in here would be great but the concept of user roles / permissions kinda needs to be done outside this library. Doing this edx/edx-exams#146 is a lot more flexible in the end. There might be an improvement to the public API here to make how this gets built easier and more obvious but not sure there's a lot of value in the two use cases we have so far. |
|
abandoning this approach for now we don't really have need for a generic course level launch. It's more flexible to build the launch using this libraries python api. |
This endpoint would expose a view a frontend app could load given an lti configuration id and a course id. Loading the view would kick off a basic 1.3 launch.
This is definitely pretty limited in what we could support without building out further modeling for what a platform wide or course wide configuration might look like. I think the long term solution very likely depends on OpenCrafts pending work around remodeling configurations / placements. Launch by placement id seems like the more correct end state for this, we just don't have placements yet. In the meantime maybe we can build something really limited to support proctoring or other tools that are course or platform wide.