sagemathinc
LMS integration via LTI for courses
LTI: http://www.imsglobal.org/toolsinteroperability2.cfm
Requirements:
- Personal data Because of our privacy context, we have particular requirements around how LTI is implemented in the tool provider. The simplest integration usually works the best, whereby the tool consumer is only required to provide the user_id field as an identifier and this is then linked to an account created within the tool consumer. That way, a student is able to manage their own display name, email etc (personal identity information) without the institution providing this information (our provisional legislation restricts us from doing this). Where an LTI integration requires us to pass PII, we are only able to pass tokenized values. This works for some applications but is impractical when a user needs to be identified in the tool provider by a human readable display name.
- API to access identity pairs In light of the above, it would be great if there was an API for an institution to query that would reveal the relation between the pass LTI user_id and the student created account details. In order for us to unmask the user identity (where a student has used alias details) we need a way of mapping back from the display values to the UBC user values. Note that this is not a component piece of LTI, but a practical necessity for UBC at least.
- Context data: In order to link a course in our LMS to the appropriate “shell” in the tool provider, a few options work. In some of our integrations, we pass the course context ID and this is used by the tool provider to create a new “shell” within the tool provider (and becomes the context for enrolment of users). Obviously, if this was supported, it may also be useful to receive the context title for purposes of naming. This is the most convenient option since the base URL can be stored at the system level and the additional elements created on the fly with the LTI launch. An alternative approach preferred by some tool providers, which we also support, is to manage separate LTI launch links from the tool provider so that an instructor would require to know this link when setting up the integration. This usually occurs when the “shell” is created first in the tool provider.
- Roles As long as the LTI implementation relies on the LTI roles, this will be fine for us.
- Outcomes service If the tool supports gradable elements, it would be great if it pushed grades.
Reported by Derek White, internal reference zd ticket #236
This page and its links are VERY good: https://www.edu-apps.org/code.html
We, at the Weizmann institute of science, would LOVE to see a LTI integration that will be very beneficial to many of our online courses in our Moodle LMS.
Still very reasonable to do. Multiple people have tried and failed to do something actually useful at this point though, so I suspect this will not happen without significant financial support or something else changing.
Just adding my support for this as well, something I think UCL would be interested in.
