BD-24 Project Meeting Notes

Date

Attendees

Agenda

Notes, decisions and action items

Date

Attendees

Agenda

Notes, decisions and action items

Jan 26, 2021

@Ned Batchelder (Deactivated)@Giovanni Cimolin da Silva @Marco Morales (Deactivated)

  • Review Project Status

  • Action Item Catch-Up

  • LTI Directory & Support Levels Discussion

  • Draft Documentation

  • Deep-Linking (5-6 PRs) in progress / ready for review

    • 126/127 ready by EOD 1/26

  • N+P Service with no PII at platform level feature

  • N+P with PII to include additional toggles / settings

  • Vocareum is working on 1.3 support

  • Documentation task - in progress

Jan 14, 2021

@Ned Batchelder (Deactivated), @Robyn Belair (Deactivated), @Marco Morales (Deactivated)

  • Review Project Status

  • Action Item Catch-Up

@Marco Morales (Deactivated) to share LTI usage data with Giovanni
  • Discussed revisiting notes

  • LTI Directory & Support Levels Discussion

    • Real world data

    • Django marketplace tool - hackathon project

    • Marketplace for all the things? or just LTI? or just Xblocks? what about DjangoApp plugins / extensions? all MFEs?

Jan 12, 2021

@Ned Batchelder (Deactivated) @Giovanni Cimolin da Silva

 

  • Deep linking implementation is underway

    • Pull requests are nearly ready for simple data presentation: HTML, image, link.

    • Deep-linking to a file will require the LMS store the file.

  • Context membership service is an uneasy fit for edX moocs.

    • Requires new batch external-id API in edx-platform

    • Ned to get some reviewing help for those APIs.

  • Giovanni will write an ADR about how we will implement the context membership service

  • TNL overall is interested in LTI independence from XBlock.

 

 

Notes Gap

 

 

 

 

 

Sep 22, 2020

@Ned Batchelder (Deactivated) , @Giovanni Cimolin da Silva , @Marco Morales (Deactivated)

  • Project Status & Next Sprint Goals

  • Open Action Items Review

  • We’ll write fine-grained TNL tickets for problems found running the validation suite

Sep 16, 2020

@Ned Batchelder (Deactivated) , @Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • Project Status & Next Sprint Goals

  • Open Action Items Review

  • Large LineItem Service PR plus tests might be split as much as possible for review (TNL-7318)

    • Pull request concerns includes authorization library and usage for anonymous user

  • ADR in progress

  • Many other services to be pulled into the next sprint

    • Deep-Linking to be pushed into following sprint.

  • Certification testing issues / fixes delayed until another round of this testing (this is in progress still)

  • LTI Standard Question re Deep-Linking naming

Sep 10, 2020

@Ned Batchelder (Deactivated) , @Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • Project Status & Next Sprint Goals

  • Open Action Items Review

  • Ned Onboarding

  • Discussed Project status / history

  • Next steps and sprint goals

  • 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)

Aug 11, 2020

, @Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

Open PRs / Items

Project Timeline / Delay or Pause

Open PRs / Items

  • 2 Line Item PRs

  • Open ADR

  • Running Test suite for LTI v1.3

Project Timeline / Delay or Pause

  • Discussed parallelization options for rest of project

  • Discussed timeline + planning which will pick up once project resumes.

  • Tickets / project items can be flagged as low or high review dependency to provide visibility into edx support / review time.

Aug 4, 2020

@David St. Germain (Deactivated) , @Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • LTI Line Item Service PRs can be reviewed

    • Studio UI to come in future - see open task (Marco)

  • IMS Testing Tools - Paired

  • Question: LTI Optional Metadata / Parameters (is this enabled today??)

  • Continue review of open PR

@Ned Batchelder (Deactivated) Run Certification suite for LTI - edX task

Jul 21, 2020

@Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • Status

  • LTI Testing Tool

  • Timeline Review

  • This sprint → reference implementation for context claim support, won’t include full ADR details this sprint.

    • May want to get arch team review + input on this (share with DaveO or others?) - edX to tag people on PR as necessary.

  • Need to do a version bump for LTI Release latest

  • Discussed score / results service questions / issues, some open issues on handling multiple line items and which to set as the grade in the gradebook.

  • LTI Testing Tool - Access questions, Marco to add action item for this

  • LTI Provider Review scope TBD - uses external python library currently.

  • Timeline check-in

@David Joy (Deactivated) - Version bump for LTI xBlock (new release tag missing)
@Marco Morales (Deactivated) - look into LTI tool usage for testing compliance once we get access and complete orientation.

 

Jul 14, 2020

@David St. Germain (Deactivated) , @Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • Status Update Review to start.

  • LTI Provider injection included

  • LTI Variables - Unique identifiers (block location)

    • this discussion is on the ADR

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

July 28, 2020

@Giovanni Cimolin da Silva , @David Joy (Deactivated) , @Marco Morales (Deactivated)

  • Pausing work for now.

  • Needs review:

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