Page Comparison

...

The first phase involves enabling course authors to reuse LTI tools (including those with LTI 1.3) using the existing “Copy to clipboard” and “Duplicate” features in Studio. Additionally, a new interface will be introduced to make LTI tool implementation more user-friendly.

1.1. Alter studio such that lti_consumer xblock is active by default and such that a new component button is available.

...

Neither of them work because with the current implementation of lti_consumer xblock the client ID changes for every component that is added. Each client_id needs to be added back in the tool provider and this makes LTI1.3 very annoying to use.
At the botom, this means we are using the This comes from the current implementation of Single Tenant mode of the LTI Deployment when we should be using the . The refactor of this xblock should allow the usage of both Single and Multi Tenant Deployment (completely unrelated to multitenancy in the lms). As such, With this change it should be possible to reuse the same ClientID and to pick the deployment ID would not longer be fixed to “1” but instead change for every component while the Client_id remains the sameaccording to the usage of the tool (some institutions use the same deployment ID to separate courses, organization or things like the university department).

1.4. Fix the render for 1.3

...

Creating This phase needs to create the backbones for the reuse directory.

Links and references:

• https://github.com/open-craft/openedx-ltistore

• Make fields overridable at the xblock even when using centralized config

• https://docs.google.com/document/d/1OKkpNIck23gejniIYQHpRZ2ClEO6O7Cds5Wg1HVgRYU/edit

Phase 3

...