LTI Improvements 3.2 Project
From MoodleDocs
| Improvements to LTI for 3.2 | |
|---|---|
| Project state | Developing |
| Tracker issue | MDL-54679 |
| Discussion | https://moodle.org/mod/forum/discuss.php?d=335775 |
| Assignee | John Okely |
Summary
The Learning Tools Interoperability (LTI) provider was added to Moodle 3.1 - but unfortunately our LTI provider and consumer do not support the same standards, and as such are missing important functionality, therefore they need usability improvements.
Below are a range of issues that have been identified and are being worked on for Moodle 3.2.
Improvements
The targeted improvements for 3.2 are:
Offer cartridges in LTI providerSupport standard icon element when importing LTI cartridges- Upgrade enrol_lti to support LTI v2.0
- Ensure enrol_lti member syncronisation task works as expected
- Content Item support
- Add support for LTI Outcomes Management 2 services
- Caliper Analytics
- Run the LTI Test suite against Moodle (consumer + provider)
- Fix auto-closing LTI config window
- Improve interface for managing course tools
- Add support for services via LTI1 (LTI1.2 spec)
- Improve accessibility of new LTI admin screen
To see the most recent set of issues and status of the project see https://tracker.moodle.org/browse/MDL-54679
Progress
- MDL-54680 Cartridges is released
- MDL-49609 Content-Item patch is completed. Peer reviewed and addressing concerns.
- MDL-53832 A patch has been created using the new LTI library provided by IMS to bring the provider up to LTI 2. Need to unit test and
- Proxies & Tool Profiles, launch requests (including LTI1 style) are working. Data persistence logic finished.
- We are currently finishing implementing the library to achieve all LTI2 requirements and matching functionality from old library
- MDL-51480 Outcomes 2 patch for the provider has been created. The patch is being finished, with refactoring and testing added if needed.
Prototype
The work in progress prototype is available to view on the prototype site. You can add tools via tool proxy, and via cartridge. You can configure a tool type when you add it using Content-item
