...
We want to enhance the course author experience to add and use LTI tools in a course. We want to reduce friction caused by the above pain points by:
General Improvement:
Enabling the LTI block by default as part of the Core Product experience
In the Pages & Resources Page:
Moving all LTI json commands for enabling an LTI tool in a course (ie, adding the passport with the key and secret) out of the Advanced Settings page and into newly designed modals with appropriate UI via an LTI tile on the Pages & Resources Page
Allowing course teams to save the course-level licensing settings (launch ID, launch url) for an LTI when that tool is added to a course for the first time. This way, authors will only have to enter it once.
See Technical Requirements section for more information about differences between 1.1 and 1.3.
In the Course Outline/Unit Pages:
Pulling the LTI component block out of the “Advanced” component tile and creating a new LTI component block
Via the new LTI component block, allowing course teams/authors to add an LTI tool to a course by selecting from a UI-friendly list of the tools that have already been added, rather than having to re-enter the id and url as the mechanism for choosing which LTI tool to add.
In the LTI Block:
Simplifying the process of configuring LTI tools within the course by simplifying the fields in the LTI block. This involves 1) removing the repetitive course-level configuration fields (launch ID, launch url, etc), which will be possible because those settings will be saved, and 2) creating a friendly UI for the configuration fields at the assignment level
Allowing course teams/authors the option to save assignment-level configuration settings for reuse within the same course, and allowing teams to choose from those saved settings when reusing the LTI tool
Re-use across courses:
Allowing course-level configurations (launch url, launch ID, etc) to carry over into new course runs. (This excludes the need to carry over assignment-specific settings.)
Allowing course-level configurations (launch url, launch ID, etc) to be reused in other courses within the same instance or organization where multi-course licenses have already been obtained.
For learners:
Learners should be able to give permission for a particular tool for a particular course once and then have those permissions saved by the LMS.
Features & Requirements
In order to realize this MVP, we believe the following features will be required.
...