Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Time

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: LTI Update Work 2023-2024 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

Platform Use Cases? https://docs.google.com/document/d/1uw06pTjtQfREm0rYJvkeQkgPnaHjS3cXriSXAx2RfsY/edit?usp=sharing

  1. Operator with a single organization – the platform can be registered once with a single client_id and the tool integrated multiple times. 

  2. 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. 

  3. 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. 

  4. Operator with single or multiple organizations, course teams under an org are responsible for managing their own catalog of LTI tool integrations. 

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
    • Write user stories for search/discovery and facet/filtering in the marketplace
    • Better specs for the Open edx Marketplace experience vs being authenticated with a particular instance
  •  
  • No labels