Versions Compared

Old Version 3

changes.mady.by.user Anna Aldric

Saved on

compared with

New Version 4

changes.mady.by.user Anna Aldric

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Configuration: Instance/Platform, Org, Course

    • Instructors or course leads adding enabling a pre-configured tool at the course org level, making it available for all courses in that org when it is enabled

    • At the org/instance level, admins add/configure a tool at the org or instance level, and it that configuration is available for use in any course in that org/instance. If a license is also added at the org level, then an instructor or course lead only needs to enable before use.

    • At the course level, authors toggle on/toggle off or adjust some configuration settings (iframe sizing) for tools that have be added and pre-configured by admins.

    • Within a course, authors can also configure tools within the course outline. This is what is currently possible, and we do not want to remove this capability. Any changes will only apply to the course for which the author has permissions.

    • Students not needing to give permission every time a tool launches - remembering student privacy permissions for an entire course.

...

Feature

Requirements

Feature 1: Add LTIs at the instance or org level once, and have it available to enable in every course in that org or instance.

An Administrative Dashboard experience in Studio, where admins can:

  • Configure an app, for use in courses, within an instance or org

  • Manage configuration settings so it doesn’t need to be reconfigured multiple times

  • Manage all chosen apps made available to users in an org or instance, depending on administrative permissions

  • Manage licenses at the org level

  • A setting that enables tools to be turned off or on for specific courses in an org or instance.

Feature 2a: Have a function that would enable course teams to select from a drop down list of LTIs enabled at the org level.

Feature 2b: Have the platform remember users' permission settings so they are not prompted with every launch. This would allow for a more seamless user experience.

From the Studio Dashboard/Studio Settings, users [course teams, faculty, etc.] will be able to:

  • Select from a list of pre-approved tools licensed at the org level (as maintained by the org admin)

  • Enable the appropriate tools within a course needed for learner success

    • Option 1: Adjust configuration settings for an approved tool for improved utility

    • Option 2: Request a tool that has not previously been configured at the org or instance level. This request should be forwarded to and handled by the instance level or org level admin. The workflow for this request transfer is not within scope for this project, but should be determined by instance or org admins.  

 

Feature 3: Within a course, have an easy way for authors/course teams to configure a learning tool at the course level.

A space in the Course Outline (probably a component tile) where LTIs that have been toggled on for the course can be configured within a course.

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 the clone of a course.

Feature 4: At the platform level, have a set of LTIs that are ‘pre-configured’, and only need a key and secret to enable at the org level. This way an institution only needs to acquire a license in order to set up an LTI from the ‘pre-configured’ list. Like the Canvas apps list.

 

...