...
Allow for global re-usablity of LTI tools throughout the course, across course runs, and across different courses, which involves creating options for course teams to save and reuse both 1) License and course-level settings and 2) Assignment-level configuration settings.
Create an author-friendly UI that makes it easy to configure LTI once and save and reuse settings. This involves removing all LTI-related fields out of Advanced Settings and creating WYSIWYG modals at the course level (new modals on the Pages & Resources pages) and at the unit level (improvements to the LTI component block).
Problem Statement:
Currently, the process for course teams/course authors to add LTI tools to their courses and reuse LTIs is cumbersome, intimidating and unnecessarily repetitive. Specific pain points include:
...
When I want to reuse that LTI tool in my course again, in a different unit, I have to fill out all of the settings in the LTI block again, because they aren’t saved (launch id, launch url, and assignment specific settings like frame width, launch in or out of line, etc)
When I want to reuse that LTI tool in a different course, I have to start from scratch the entire process from scratch, starting with creating a new passport, because the settings aren’t saved.
When I create a new course run, I have to start from scratch the entire process from scratch, starting with creating a new passport, because the settings aren’t saved.
...
Feature | Requirements |
Feature 1: Modals for course teams/authors to add an LTI to their course and save the course-level settings/license information Feature 2: An LTI-specific component block available in the components section of the unit pages Feature 3: A “list of LTIs” modal that lets course teams easily select from all the tools that have been added to the course. . | Requirements for Feature 1: A new “LTI” tile on the Pages & Resources page. The tile will house a series of modals that will walk the author through UI-friendly fields to add a new LTI id, passport, and save the settings so they don’t have to be re-entered every time the LTI is used in the course. Authors can also enter the launch ID and launch URL once. See Design Concept 1.
Requirements for Feature 3: A friendly UI that authors can access from within the course outline via the LTI Component Block to choose which LTI they want to add to a unit. See Design Concept 2.
|
Feature 4: Modals in the LTI Component Block for authors/course teams to configure a learning tool within a course unit for specific assignments. Feature 5: An option to save assignment-level settings that can be chosen on reuse of the LTI tool in the same course. Feature 6: A modal for learners to enter permissions once. | Requirements for Feature 4: A UI for a list of configuration fields that focus on configuring the tool specifically for the assignment. Requirements for Feature 5: A setting that lets authors save custom settings so it doesn’t have to be rebuilt every time it’s used in the course or in new course runs. Requirements for Feature 6: Many possible approaches: 1) we could have one modal appear at the start of a course that requests permission from learners for all LTI included in the course; 2) we could have one modal appear per ‘new LTI tool’ launch with the system thereafter remembering the given permissions; 3) we could have option 1 combined with option 2 for any LTI tool added by the course team after term start. |
...