Open action items including LTI v1.3 test suite still an open task.
ADR is still in draft and being reviewed.
Marco Morales (Deactivated) to put into UX backlog the review of configuring LTI blocks higher than the content block level. (won’t be ready for 4-6 weeks I’d guess)
discussed whether unique identifiers exist for course tabs or other levels of the course hierarchy.
resource link ID necessary for LTI Launch
LTI configuration in Studio for Course level still TBD, team is building this into Django admin for now.
Open question about how to handle configuration for LTI to be used throughout the platform. For now focused on course level configuration.
plan is to use string based loose configuration for now as plans /models evolve here for configuration at different levels. (as opposed to django foreign keys)
ADR for Studio / LMS boundary discussed → What are the implications for LTI here?
ADR exists for whether or not to include LTI keys. can easily include in export for 1.1 but not for 1.3.
LTI launches focused on learning content primarily, also course tabs. Potential future use in course content sidebar but this is TBD.
for now centralized configuration is the important part, can explore multiple UIs for configuration or additional slots in the future.
example - Piazza or Yellowdig might have configuration for main app + sidebar (if they eventually support in-context discussion)
Marco Morales (Deactivated) to look at requirements for Studio course run level configuration view / wireframes
Marco Morales (Deactivated) to explore / configure future (out of scope for now) org / program level UI configuration.
TNL-7318 - line items implementation. POC implementation, decided to split the work into smaller pull requests. Move configuration to model, second one to improve auth around LTI, and third to implement line items. First is up for review. This blocks the other steps.