Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LTI Redesign Project #415

Open
MaferMazu opened this issue Dec 23, 2024 · 2 comments
Open

LTI Redesign Project #415

MaferMazu opened this issue Dec 23, 2024 · 2 comments

Comments

@MaferMazu
Copy link

MaferMazu commented Dec 23, 2024

Abstract

The "LTI Redesign Project" on Open edX aims to enhance usability and user satisfaction through user-centered design. Objectives include simplifying LTI addition and reuse for administrators and course creators and accommodating users of all levels.

Detailed Product Proposal

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4179230740/LTI+Redesign+Project

Context & Background (in brief, if a Product Proposal is linked above)

The course author's experience adding an external tool via LTI could improve. We can't reuse an LTI 1.3 tool; instead, we will perform a specific workaround and use external plugins. That means the default form is to configure a tool each time you want to use it. Also, configuring tools is complex compared with other platforms such as Moodle and Canvas.

https://openedx.atlassian.net/wiki/spaces/COMM/pages/3779362817/Product+Vision+LTI+Strategy
https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4179230740/LTI+Redesign+Project

Scope & Approach (in brief, if a Product Proposal is linked above)

The initial scope was:

  • Alter studio such that lti_consumer xblock is active by default and such that a new component button is available.
  • Graphical editor for the xblock.
  • Fix the re-usability with the current tools.
  • Fix the render for the 1.3 launch.

However, we also encounter the principal problem of LTI 1.3: the LTI config depends on the LTI xblock.
Decoupling the model to have an LTI config part and an xblock part could be the first or second part of this project.
This proposal also aligns with what 2U commented in the Boston conference about the next steps of the work on LTI. However, this requires ADRs and discovery because we will affect how it works and must figure out how to mitigate possible problems.

So, we should discuss the scope for the first part of the project.

More info: https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4428726289/Technical+Approach+for+LTI+redesign

Value & Impact (in brief, if a Product Proposal is linked above)

LTI 1.3 is a standard that improves extensibility by integrating Open edX into a broader educational ecosystem. We want to improve how we configure tools according to this standard and make it easier for administrators and course authors to add tools and content.

A specific metric could be the time we spend configuring and reusing a tool in the platform.

Milestones and/or Epics

It depends on the scope we set, but the milestones of the two parts of the project we proposed are in the wiki proposal.

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4428726289/Technical+Approach+for+LTI+redesign

Named Release

Teak

Timeline (in brief, if a Product Proposal is linked above)

TBD

Proposed By

edunext

Additional Info

Related project proposals:
#368
#287

Copy link

Thanks for your submission, @openedx/openedx-product-managers will review shortly.

@MaferMazu
Copy link
Author

cc @jmakowski1123 @SantiagoSuHe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant