2023-07-11 LTI/Learning Tool WG Meeting

Time	Item	Presenter	Notes

Item	Presenter	Notes
Product /UX/Spec Approach Document: LTI Update Work 2023-2024	@Anna Aldric	UX/UI Mock up will be added to the working document. Engineers should scope out work, building on these mock ups. If we need further input from UX team, we can have a separate follow up or work asynchronously. Lucid chart from Jenna. (see below) Figma UX Mock Ups from Jon and Cassie - screen shots will be added to primary working document Please add notes to Primary working document: Product Vision: LTI Strategy @Scott Dunn @Anna Aldric @Jenna Makowski to flesh out vision +user stories after meeting with UX team. UX team to continue work in parallel while Product Doc (above) completed Goal: starting engineering scoping work in 2 or 4 weeks, for the MVP (2023)
	Async Update	Screen recordings of current user experience - pending - Anna has tapped a member of her team to record this
PII Sharing	@Zach Hancock	Punt to July 11
Product spec - visual/concept map	@Jenna Makowski	https://lucid.app/lucidchart/f9d3eb7a-e751-45ad-a6df-f725bdbaebef/edit?viewport_loc=-2135%2C-2967%2C11529%2C5751%2C0_0&invitationId=inv_43bb62d1-9b25-4ead-8c95-bedb08c2dc5b
Plan to touch base with Giovanni

Meeting notes

Operator with a single organization – the platform can be registered once with a single client_id and the tool integrated multiple times.
Operator with multiple organizations, provides a catalog of pre-registered LTI tool integrations to multiple customers – in this scenario, the business relationship is established at the platform level and there is only one platform registration per tool (client_id). Ignoring deployment_id, this is the same as use case #1.
Operator with multiple organizations, each organization is responsible for managing its own catalog of LTI tool integrations – each org has a business relationship with the tool provider. There are multiple platform registrations (client_ids) for a given tool provider.
Operator with single or multiple organizations, course teams under an org are responsible for managing their own catalog of LTI tool integrations.

Maybe take a look at how public vs private service directories work.

recording:

Action items

Get Product Spec + UI/UX to “done” in terms of defining full vision/strategy for LTI

Write user stories for all scenarios where licenses can be held/define who owns the business relationships

[out of scope for MVP] Write user stories for search/discovery and facet/filtering in the marketplace

[out of scope for MVP] Better specs for the Open edx Marketplace experience vs being authenticated with a particular instance