2023-07-11 LTI/Learning Tool WG Meeting
Time | Item | Presenter | Notes |
|---|---|---|---|
| Product /UX/Spec Approach Document: LTI Update Work 2023-2024 | @Anna Aldric |
|
|
| 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
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.
Marketplace (parallels with web services?) - WSDL and UDDI.
Maybe take a look at how public vs private service directories work.
recording:
Action items